Phase 1 ends when anyone can use it.
Phase 1 is the whole product: private payments that work end to end, plus the compliance layer that makes them provable. Most of it is already live on testnet. It closes when we open the testnet to everyone. Everything after that is about removing the last places where you still have to trust us.
The private rail
Done. Anyone can use it. Everything works, the testnet is open.
The complete product: private payments that work end to end, plus the compliance layer that makes them provable. All of it is live on Robinhood Chain testnet, open to everyone, with nothing gated and nothing invite only.
Zero-knowledge shielded pool
LiveDeposit USDG, receive a private note, withdraw to any fresh address. An observer sees both transactions and cannot link them.
Proofs built in your browser
LiveGroth16 over Poseidon and a LeanIMT Merkle tree, generated locally with snarkjs and verified on-chain by the WithdrawVerifier contract.
Partial withdrawals
LiveSpend part of a note. The remainder returns as a change note, so you are not forced into fixed denominations.
Non-custodial notes and encrypted backup
LiveThe note never leaves your browser. Export an encrypted backup with PBKDF2 and AES-GCM, restore it on another device.
Claim links
LivePay someone who has no wallet set up yet. The secret rides in the URL fragment, so no server ever sees it.
Gasless withdrawals
LiveA relayer submits your proof and takes its fee from the withdrawal, so you never need to hold ETH. The fee recipient and amount are bound into the proof, so it cannot tamper with either.
Compliance layer: the association set
LiveDeposits are screened against a public policy, and an approved-set root that anyone can recompute from public chain data is published, with no signing key. Each note has a verifiable clean status and an exportable receipt. This is what makes it a compliant private rail rather than a mixer. Enforcing the set inside the withdraw circuit is a Phase 3 item.
Open testnet
LiveOpen to everyone. Nothing is gated, nothing is invite only, and the whole product is usable end to end at app.privepay.app.
Open the network · $PRIVE
Take us out of the loop, and put a bond where the trust used to be.
Phase 1 works, but two things still lean on us: the relayer is ours, and the screening provider would be ours. Phase 2 opens both. $PRIVE is live, launched on Pons, and the contracts that give it its job are being written in the open. Until they are on-chain, the token is a claim on this phase, not a live bond. We would rather say that than pretend otherwise.
$PRIVE launch
LiveLive, launched on Pons. It is not a fee coupon. It is the collateral that will let strangers run the infrastructure without you having to trust them. The bond contracts below are what turn that from a design into a guarantee, and they are next.
Decentralised, bonded relayers
Today there is one relayer and it is ours. It cannot steal from you or deanonymise you, and you can always submit a withdrawal yourself, but it can go down or refuse to serve you. Anyone will be able to run one by posting a $PRIVE bond, and a relayer that fails to deliver on a commitment it accepted on-chain loses it.
Bonded screening provider and governance
Whoever decides whose money is clean must be slashable when the published set does not match the published policy. Holders govern the lists, the appeal path and the parameters, so that power is not ours alone.
Published SDK
The TypeScript SDK exists in the repo. Ship it to npm so any wallet or app can shield a payment in a few lines.
Programmable and agent payments
Machines are becoming the counterparty. Give agents a way to pay privately over the same rail, with per-payment authorisation instead of a hot wallet holding the keys to everything.
Audit and in-protocol enforcement
Nothing touches real money before this phase closes.
The compliance layer in phase 1 is an attestation anyone can recompute. Phase 3 moves it inside the circuit, and puts the whole system in front of auditors.
Independent audit
The pool, the verifier and the circuit, audited by a third party and published in full, including what they found.
In-circuit enforcement
Prove membership of the approved set inside the circuit itself, not just alongside it. This needs a new circuit and a new verifier.
Production trusted setup
The current proving key comes from a development ceremony. Mainnet needs a proper multi-party ceremony that anyone can contribute to and verify.
Mainnet
Real money, once it has earned the right.
Robinhood Chain mainnet with real USDG, opened carefully rather than loudly.
Mainnet deployment
The pool, the verifier and the screening provider running on Robinhood Chain mainnet with real USDG.
Progressive limits
Open with deposit caps and raise them as the anonymity set grows. A big pool with three users in it is not private.