zPredict

Your wallet · testnet

Use your own wallet.

No wallet connects to a website in shielded Zcash, and zPredict doesn't need one: your account is a key kept in this browser. Your wallet sends testnet ZEC in and receives it back out, in three steps.

  1. 1. Deposit

    Pay the request from a shielded testnet wallet: scan the QR code, open it in a wallet on this device, or copy it. No testnet ZEC? Get some from the faucet.

    Deposit
    1. Pick one fixed size. Every deposit is one of these three, so the amount never reveals a bet size.
      Deposit size
    2. Create an account tag. It is made in this browser and never leaves it in clear.
    3. From a shielded testnet wallet, send exactly 0.05 testnet ZEC with this payment request. It pays the escrow's unified address (Ironwood receiver only, FROST 2-of-3) and carries a memo giving each relayer only its own share of your tag. Don't edit the amount or the memo.
    4. After 10 confirmations each relayer credits your balance.
    5. No testnet wallet? The faucet sends 0.01 ZEC straight into this account.
  2. 2. Bet

    Once the deposit is credited, pick a market and send an order. It leaves this browser as three random shares, one per relayer.

    Pick a market
  3. 3. Withdraw

    Paid from the escrow to a fresh testnet unified address with an Ironwood (Orchard) receiver. Transparent addresses are refused.

Account key

Anyone with this key controls your balance. Nobody can recover it for you: keep a copy somewhere safe, never share it.

Which wallets work?

You need a wallet that runs on Zcash testnet, can send to an Ironwood (Orchard) receiver with a memo, and reads ZIP 321 payment requests.

  • zcash-devtool (wallet pay --payment-uri): tested. Our end-to-end scripts pay this exact kind of request with it and receive payouts to it, on a local regtest chain.
  • Other wallets: not verified by us yet. If yours handles testnet, Ironwood and memos, it should work; tell us in the repository's issues either way.