Shielded transfers and swaps use a UTXO pool on Solana with Groth16 proofs. Balances, amounts, and counterparties are not exposed on-chain the way a regular SPL transfer is. Validators see that the program ran and that commitments updated, but not the plaintext trail of a standard wallet send.

For the full threat model and what is and isn’t leaked, read the privacy model docs.

Proofs are generated entirely client-side in your browser using a WASM prover. Your secret notes, viewing keys, and randomness never leave the device — only the resulting proof and public inputs are submitted to the relay.

The prover is open source; you can inspect or self-host it from GitHub.

The relay receives the validity proof, the public inputs, and a small fee — nothing else. It cannot link a deposit to a withdrawal, recover the recipient, or read any amount. Its only job is to forward the transaction so your wallet doesn’t have to pay gas in cleartext.

Architecture details live in the relay docs.

No registration required. A viewing key is derived deterministically from your wallet signature the first time you connect. You can optionally back it up with the encrypted backup flow so you can sync your shielded balance across devices.

Step-by-step in key management.

Protocol fee is 0.30% of the shielded amount, split between relay and treasury. There’s no minimum, but very small notes can become uneconomical to spend due to network gas. Suggested floor is around 0.05 SOL or 5 USDC equivalent.

Live fee schedule: fees & limits.

That happens when the on-chain tree advanced between proof generation and submission. The client retries automatically with a fresh root for up to 3 attempts. If it still fails, just resubmit — your funds are never at risk because the proof is bound to a specific tree state.

Troubleshooting guide: docs.

No. Unipay is fully non-custodial. Your spending keys never leave your wallet, the relay cannot move funds, and the on-chain program is governed by a transparent upgrade authority with timelocks. We never hold user assets at any step.

Each user controls a viewing key that lets them selectively prove the source, destination, or amount of any of their own transactions to a third party — without leaking the rest of their history. Institutions can issue audit reports on demand without breaking the privacy of unrelated users.

Read the compliance overview for the auditor flow.