Verification Center

Proof, receipts, and privacy guarantees.

Review the verified registry lifecycle, TokenOps Disperse receipts, and privacy guarantees behind CipherOps. No fake data — only confirmed on-chain transactions.

Sepolia verifiedTokenOps receiptsFHE-encrypted amountsNo fake data

1 — Verified Registry Lifecycle

Full confidential token lifecycle

Verified through live Sepolia transactions during manual QA. All steps performed against official Zama deployed contracts — no custom contracts or mocks.

6/6 steps confirmed
1
Faucet— ERC20.mint(user, 100e18) on official Sepolia mock token
2
Approve— ERC20.approve(wrapper, amount) — live allowance verified
3
Wrap— wrapper.wrap(user, amount) — ERC-20 sealed into ERC-7984
4
Private Reveal— confidentialBalanceOf + EIP-712 user-decrypt via Zama relayer
5
Unwrap— wrapper.unwrap(from, to, encHandle, inputProof) — Gateway initiated
6
Finalize— wrapper.finalizeUnwrap(requestId, cleartext, proof) — ERC-20 released

Full tx hashes in docs/QA_CHECKPOINT_PHASE3.md

2 — Verified TokenOps Disperse

T2AConfirmed

Initial Verification (T2A)

Tx
0x650b5e598d3a…8de07752
Network
Ethereum Sepolia
Type
TokenOps Confidential Disperse (direct mode)
Token
cUSDCMock — Zama official Sepolia wrapper

Recipient amounts are FHE-encrypted. Amount not visible on-chain.

View on Sepolia Etherscan →
T3Confirmed

CSV/Campaign UX Verification (T3)

Tx
0x8743a9d98d65…c7264d18
Network
Ethereum Sepolia
Type
TokenOps Confidential Disperse via polished Operations form
Token
0x7c5B…3639
Recipient
0x1afB9439…7a5FD282

CSV import, campaign summary, and post-success receipt all verified. Recipient amount remains encrypted.

View on Sepolia Etherscan →

Full details in docs/QA_CHECKPOINT_TOKENOPS_DISPERSE.md

3 — Privacy Guarantees

What is visible on-chain

  • ·Public observers can see transactions and contract calls on Sepolia Etherscan.
  • ·Public observers cannot see individual recipient payout amounts — they are FHE-encrypted ciphertexts.
  • ·Recipients can reveal their own confidential balances through the Private Reveal flow in the Registry.
  • ·The plaintext balance is decrypted locally in the recipient's browser; it is never stored server-side.
  • ·CipherOps does not invent transaction hashes, mock balances, or simulate operations.
  • ·All registry data is read live from the official Zama on-chain registry — no cached index.

4 — Documentation

Registry →

Live Zama wrapper registry explorer

Operations Studio →

TokenOps Confidential Disperse

Recipient Portal →

Reveal your own confidential balance

QA Checkpoint — Phase 3

docs/QA_CHECKPOINT_PHASE3.md

QA Checkpoint — TokenOps Disperse

docs/QA_CHECKPOINT_TOKENOPS_DISPERSE.md

Submission Pack

docs/SUBMISSION_PACK.md

Final QA Checklist

docs/FINAL_QA_CHECKLIST.md

TokenOps Client Analysis

docs/TOKENOPS_CLIENT_ANALYSIS.md

Explore the lifecycle

Every verified feature is live on Sepolia right now.

Open RegistryOperations StudioRecipient Portal