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.
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
Allocations, tiers, and vesting are encrypted client-side with Zama before submission. TokenOps vesting receives encrypted amounts via `@tokenops/sdk` — plaintext amounts stay off the public dashboard.
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
- 2
Zama FHE encryption
- 3
Confidential contract submission
- 4
TokenOps campaign synced
- 5
Campaign ready
TokenOps integration
Confidential distribution lifecycle rail
Mode
Real SDK
Connection
Probing…
Provider
—
SDK version
—
Operation log
No TokenOps operations yet.
Zama encryption
Confidential allocation layer
ModeRelayer SDK
Contract0x468d…C885
StatusLoading
Connect a wallet to record the admin address.