Live verification
Verify the whole project quickly.
This page collects the public facts a judge needs: SDK versions, ERC-7984 token, TokenOps infrastructure, VantaDropRegistry, proven browser flows, Etherscan links, Claim Vault discovery status, and the public/private data boundary.
Fast status
TokenOps SDK
@tokenops/sdk@1.1.1
Zama FHE SDK
@zama-fhe/sdk@3.0.0
CTTT token
VantaDropRegistry
Core infrastructure
Demo checklist
- 1Open /create and confirm the sender console, Sepolia guard, prep panel, and execute timeline are present.
- 2Open /drops and confirm wallet discovery explains Claim Vault eligibility checks without JSON import.
- 3Open /recipient/demo and confirm the visible flow is connect, detected package, reveal, claim, verify.
- 4Open /drop/demo and confirm the public room does not expose private claim material.
- 5Use the Etherscan links below to inspect contracts and transactions.
What is public vs private
Public surface
Verifiable metadata only
The registry is intentionally narrow: it records public metadata needed for discovery and judging, not recipient-specific claim material.
Confidential surface
Claim Vault capsules and encrypted allocations
Claim material is stored in encrypted backend capsules for wallet discovery. Recipients decrypt only their own allocation after explicit wallet actions.
Claim Vault discovery
Product direction
Product discovery now uses a Paychain-style encrypted Claim Vault: recipients open /drops, connect a wallet, sign a harmless eligibility message, and receive only their matching claim capsule if one exists.
Honest privacy boundary
Wallet discovery uses encrypted backend storage and wallet-signature access control. It requires trusted encrypted backend storage for discovery. Manual package import exists only in hidden developer diagnostics.
Wallet readiness
Your wallet readiness
No wallet connectedLive detection of your browser wallet — connection and chain only. This section performs no on-chain action: the "Proven live" results on this page were produced by the Node-script spike, not by this browser, and browser execution is not wired yet.
Integration status
Where the browser integration actually stands. "Ready" means typed service functions exist and compile into this bundle. "Proven live" means a human ran that exact action against a funded burner wallet on live Sepolia and it succeeded. The full issuer create flow and the recipient decrypt/claim flow have both now been run live end-to-end on their actual public pages —/createand/recipient/demo— not only via hidden developer diagnostics. The full app flow is proven live on Sepolia. The product path now uses Claim Vault discovery; manual package import remains only in hidden developer diagnostics.
This row is a real read-only call to VantaDropRegistry.totalDistributions() from your browser. The original proven demo airdrop predates the registry frontend and was never registered; the count above reflects only distributions actually registered by the now-proven-live issuer flow.
Etherscan proof panel
Stack
Pre-deployed TokenOps infrastructure plus the pinned Zama browser SDK.
Contracts
Verify each public address independently on Etherscan.
Proven on Sepolia
Proven liveThese links are real Sepolia records: mint, create and fund, recipient decrypt access, claim, and registry deployment.