The pool

Reading the chain…

  1. Mainnet
  2. Ceremony
  3. Audit

Program

Read from the chain

Program address

Not deployed yet

There is no program account on Solana, so there is no address to send anything to. The address and its Solscan link appear here the moment it exists — this page reads the chain, it does not guess.

The browser deposit screen is not wired yet. Until it is, a deposit is a plain Solana transfer to one of the pool addresses above, and the receipt is drawn by the client in the repository — the same code the end-to-end test runs.

What the pool will take SOL only · v1

Three amounts

Nothing in between

Fixed amounts only: a free amount is a fingerprint, and it would point back to you.

Three moves, nothing else What a deposit really is

  1. 01

    Send to the program

    From any wallet, send one fixed amount to the program address. Not to a person: the funds land on a PDA, an address with no private key. Nobody can move them — not the owner, not the server, not an administrator. Only the code can, and only for a valid withdrawal.

  2. 02

    Keep your receipt

    Your browser draws two random numbers and publishes only their imprint — the commitment. Those two numbers are the receipt, and they are the only key to that deposit. They never leave your machine, and nobody else ever sees them.

  3. 03

    Withdraw to another address

    Later, prove you know the numbers behind one deposit in the tree, without saying which one. A relayer sends the transaction, so the receiving address needs no SOL and no history of its own; the program pays it. The relayer cannot alter the proof or redirect the payment.

The receipt is the only key

Lose your receipt and the funds are gone for good. There is no account, no password reset and no support line: nobody can hand a deposit back — not KeepHost, not the program, not a court. Whoever holds the receipt can withdraw, so keep it the way you would keep a seed phrase.