Recipient Portal
Private payouts stay encrypted until the recipient chooses to reveal their own balance. Public observers cannot see what you received.
How it works
Sender encrypts amounts
The Operations Studio uses Zama FHE to encrypt each recipient's amount before the transaction is broadcast. The disperse tx only reveals the token address and recipient count — not individual amounts.
On-chain privacy
The encrypted ciphertexts live on-chain, but only the respective recipient's wallet can decrypt them. Public block explorers show the transaction but not the individual payouts.
Recipient-controlled reveal
You — and only you — can reveal your own balance by signing a one-time EIP-712 authorization. The decryption happens locally in your browser; nothing is sent to a server.
Step-by-step guide
Receive confidential token payout
An admin uses the CipherOps Operations Studio to send ERC-7984 tokens to your wallet. Individual amounts are FHE-encrypted before being broadcast — no one else can read what you received.
Open the Registry
Navigate to the Registry Explorer. It reads Zama's official on-chain wrapper registry and lists every ERC-20 ↔ ERC-7984 pair.
Select the same ERC-7984 token
Find the confidential token pair matching the address in your payout. Click it to open the Token Action Panel.
Use Private Reveal
Click the Private Reveal tab. Connect your wallet on Sepolia. The page will ask you to sign a one-time EIP-712 authorization — this proves you own the wallet without revealing your balance publicly.
See your balance privately
The Zama relayer decrypts your encrypted balance locally using your keypair. The plaintext amount appears only in your browser — it is never sent to a server or stored on-chain.
Ready to reveal your balance?
Open the Registry, find the token you received, and use the Private Reveal tab.
Recent payout receipt
If you were sent a payout via CipherOps Operations, the receipt details will appear here in a future update once wallet connection is wired to this page.
For now: copy the confidential token address from the Operations post-success card, then paste it into the Registry Explorer to locate your pair and start the Private Reveal flow.