Sender console
Create confidential distribution
SepoliaSix guided steps. Recipient data stays in your browser. At execution, TokenOps receives encrypted funding and recipient-bound encrypted inputs; VantaDropRegistry receives public metadata only.
Claim Vault boundary
Six steps. Recipient data stays in your browser — at execution only encrypted handles and public metadata go on-chain.
This panel can send real Sepolia transactions (test-token mint, operator approval). Connect a disposable burner wallet — never a wallet holding real funds. Checks marked "free" are reads only and never prompt your wallet. Nothing on this panel runs the create flow itself — that stays on the Execute step.
Wallet & network
CTTT test tokens
CTTTbalance is confidential. Balance verification may require the Zama decrypt flow. Mint test tokens if needed. The free check below reads only the opaque encrypted balance handle — it can tell "never credited" from "has confidential state", but never a plaintext amount (decrypting is deliberately out of scope for this panel).
Honesty note: the faucet mint amount (10 CTTT, 6-decimal raw 10000000) is public plaintext calldata by design — only your aggregated confidential balance stays private. After a successful mint, re-run the free readiness check.
Operator approval
The TokenOps factory 0xbE6A3B…cd4c must be an authorized ERC-7984 operator on CTTT before the Execute step can fund a distribution. The check is a free read; approval, if needed, is one real Sepolia transaction. Doing it here saves one wallet prompt during execution.
Wallet
Network
Choose distribution type
Every type runs the same confidential flow — the choice sets the framing, not the mechanics.
Public: the title and the distribution type above are written on-chain to VantaDropRegistry at execution. Do not put recipient names or amounts in the title — recipients and amounts never go on-chain.