Admin
Create a confidential campaign
Upload allocations, encrypt them with Zama FHE, and sync the campaign lifecycle to TokenOps. Allocation amounts, tiers, and vesting stay private; budget and rules stay public.
Start from a preset
One click fills the whole form with a realistic, ready-to-launch example
Presets pre-fill everything — you still review, edit, and sign before anything hits the chain.
Campaign details
Public, verifiable metadata
Recipient allocations
Add recipients with the form, or paste a CSV
No recipients yet. Fill the fields above and click Add recipient.
Confidential creation flow
Encrypt → submit → TokenOps sync
Two settlement rails
- Claim rail — recipient calls `claim()` → encrypted balance credited via `FHE.add` on `CloakConfidentialToken`.
- TokenOps rail — this flow deploys + funds per-recipient vesting wallets on the official confidential factory (same allocation, schedule-based release).
- 1
CSV parsed & validated
We read your recipients, check every address, and sum allocations against the public budget — no signature needed.
- 2
Zama FHE encryption
Each amount, tier, and vesting class is encrypted in your browser. Signature 1 authorizes the encrypted batch.
- 3
Confidential contract submission
All recipients are written on-chain in one Multicall3 batch. Signature 2 sends it — that's the last signature, no matter the list size.
- 4
TokenOps campaign synced
Encrypted allocations flow into TokenOps vesting wallets automatically — no extra clicks from you.
- 5
Campaign ready
Recipients can claim privately and anyone can verify the public rules on the audit page.
TokenOps integration
Confidential distribution lifecycle rail
Mode
Connection
Provider
SDK version
Operation log
No TokenOps operations yet.
Zama encryption
Confidential allocation layer
Connect a wallet to record the admin address.