Droptron

Private token operations for teams that cannot afford to make every allocation public.

Droptron is a wallet-first workspace for creating, funding, executing, and claiming confidential token distributions on the Zama Protocol. It brings TokenOps confidential disperse, airdrop, and vesting flows into one polished product surface, so teams can run real token programs while keeping recipient amounts encrypted.

Token distributions are usually operationally sensitive. Team rewards, grant payouts, investor allocations, advisor unlocks, ecosystem incentives, and private community campaigns can reveal strategy when every wallet and amount is public. Droptron keeps the workflow transparent enough to operate, audit, and recover, while keeping allocation values private to the wallets that are allowed to see them.

At A Glance

• Private by default: allocation values are encrypted, not published as plaintext tables.
• Real distribution flows: disperse, airdrop, and vesting are wired through TokenOps and ERC-7984 confidential assets.
• Recipient-safe reveal: recipients only see records assigned to the connected wallet.
• Operator-grade workflow: readiness checks, lifecycle states, receipts, and admin controls are built into the workspace.
• Production-shaped UX: responsive workspace screens, wallet-change guards, claim portal separation, skeleton loading, and copy that explains the privacy boundary without making users read protocol docs.
• Developer-ready repo: Next.js frontend, Hardhat demo token, Supabase migrations, and clear setup paths live together.

What Droptron Is

Droptron is an operations desk for confidential ERC-7984 token distribution.

It is built for:

• token teams distributing private rewards, contributor payouts, or launch allocations
• DAOs and grants programs paying contributors without exposing every amount
• funds and ecosystems coordinating investor, advisor, or partner allocations
• recipients who need a simple way to verify, reveal, and claim only what belongs to their wallet

The product is intentionally split into two sides:

• Workspace: where operators create campaigns, choose tokens, add recipients, execute TokenOps flows, view receipts, and manage recovery controls.
• Claim portal: where recipients connect a wallet, see only eligible airdrops or vesting schedules, reveal their own encrypted allocation, and claim when available.

No recipient needs a workspace account. No operator needs to expose plaintext allocation data in the UI after execution. Wallet ownership, TokenOps roles, ERC-7984 confidential balances, and Zama decrypt permissions define the privacy boundary.

Why It Matters

Public token operations leak more than a transaction hash.

They can expose:

• exact recipient allocations
• team, advisor, investor, or contributor compensation
• treasury movement and distribution timing
• community reward segmentation
• private cohort or allowlist strategy
• concentration of ownership before a launch or unlock

Droptron turns that into a product workflow:

1. build a campaign in a guided workspace
2. select a confidential ERC-7984 token
3. import or enter recipients
4. validate amounts and readiness
5. execute real TokenOps transactions
6. publish or expose recipient-specific claim access
7. let each recipient decrypt only their own allocation
8. preserve receipts and admin controls without making private values public

Core Capabilities

Confidential Disperse

Use Droptron for direct encrypted payouts to a fixed recipient list.

Best for:

• contributor payouts
• grants and community rewards
• vendor or partner payments
• team rewards
• private investor or advisor distributions

How it works:

• the operator imports recipients and amounts
• allocation values are encrypted for the TokenOps disperse flow
• the connected wallet executes the confidential transfer
• recipients receive confidential token balances
• authorized wallets can reveal private rows when needed

Confidential Airdrops

Use Droptron for claim-based confidential campaigns with public windows and private amounts.

Best for:

• allowlisted campaigns
• retroactive rewards
• community cohorts
• private launches
• campaign-style reward claims

How it works:

• the operator deploys a per-campaign TokenOps airdrop clone
• the operator funds it with an encrypted balance
• Droptron publishes recipient claim payloads
• recipients open the claim portal and only see eligible campaigns
• a recipient can reveal their own allocation and claim during the window
• remaining funds can be recovered through admin controls

For larger airdrops, Droptron supports delegated claim signing. The operator grants an approved signer the required role once, then Droptron can generate recipient claim signatures in a batch instead of asking the browser wallet to sign each recipient one by one.

Confidential Vesting

Use Droptron for encrypted vesting schedules where the schedule shape is public but grant values stay private.

Best for:

• team and advisor unlocks
• contributor grants
• investor schedules
• milestone-style allocations
• long-running reward programs

How it works:

• the operator creates or uses a TokenOps vesting manager
• each recipient receives an encrypted vesting grant
• schedule fields such as start, cliff, end, interval, initial unlock, and cliff unlock are public
• grant amounts remain encrypted and readable only through ACL-authorized reveal
• recipients can reveal total grant, claimable amount, settled amount, vested amount, and locked amount
• recipients claim unlocked tokens as the schedule progresses

Privacy Model

Droptron is designed to be explicit about what is public and what is private.

Public

• campaign existence
• token address
• network
• operation type
• public schedule data such as claim window or vesting timeline
• transaction hashes and explorer receipts
• contract addresses
• some role and admin state required by the protocol

Private

• recipient allocation amounts
• encrypted airdrop claim amounts
• encrypted vesting grant amounts
• confidential transfer values
• decrypted values after a recipient or authorized wallet hides them again

Wallet-Scoped Reveal

Recipients do not browse a global allocation table. The claim portal checks the connected wallet and only lists records assigned to that wallet. Reveal actions use Zama user decryption so the private value is shown only after wallet authorization.

Product Experience

Droptron is not a raw SDK form. It is a product layer around confidential token operations.

The interface focuses on:

• guided campaign creation
• token registry and manual ERC-7984 token selection
• demo dCUSD flow for Sepolia testing
• recipient validation and allocation review
• operational status cards
• explorer receipts
• claim portal separation
• language support for global teams and recipients
• mobile and tablet layouts for the homepage, workspace, campaign builder, dashboards, settings, and claim flows
• wallet-change access guards
• premium skeleton loading states for network waits
• admin controls for pause, role, recovery, withdrawal, and disclosure paths where supported
• clear copy around what is private, what is public, and what action comes next

The goal is simple: make confidential token distribution feel like a normal product workflow, while preserving the privacy guarantees that make ERC-7984 and TokenOps useful.

How The Main Flows Fit Together

Operator workspace
  |
  |-- Create campaign
  |-- Select ERC-7984 token
  |-- Add recipients and private amounts
  |-- Validate wallet balance, network, and approvals
  |-- Execute TokenOps operation
  |-- Store campaign status, receipts, and private handles
  |
Recipient claim portal
  |
  |-- Connect wallet
  |-- List only eligible airdrops and vesting grants
  |-- Reveal wallet-specific allocation
  |-- Claim when the operation allows it

Architecture

droptron/
  frontend/              Next.js app, wallet UI, campaign workspace, claim portal
  hardhat/               Demo ERC-7984 token contract and deployment scripts
  supabase/              Workspace and campaign persistence migrations
  docs/                  Reserved for public product documentation

Frontend

• Next.js App Router
• React and TypeScript
• Tailwind CSS
• RainbowKit, wagmi, and viem
• TanStack Query
• Supabase client
• TokenOps SDK
• Zama FHE React SDK
• built-in i18n messages for English, French, Korean, and Vietnamese

Contracts

• Solidity and Hardhat
• OpenZeppelin Confidential Contracts
• ERC-7984 compatible demo token
• Sepolia deployment scripts

Data

Supabase stores workspace and campaign metadata, including lifecycle state, public receipts, contract addresses, recipient references, and encrypted handle references. Private allocation values are not treated as public product state. On-chain TokenOps contracts and Zama ACL/decryption flows remain the source of truth for confidential values.

Documentation

Public docs live in docs/:

• Architecture
• TokenOps Flows
• Security And Privacy
• Demo Guide

Token And Network Support

Droptron is currently optimized for Sepolia testing and TokenOps/Zama confidential flows.

Token selection supports:

• verified registry tokens for the selected network
• manual ERC-7984 token addresses
• Droptron demo dCUSD for local and Sepolia testing

If a team only has a standard ERC-20 token, the intended path is to wrap it into an ERC-7984 confidential asset first, then use that confidential token inside Droptron.

Demo Token

The repository includes a demo ERC-7984 token contract for end-to-end testing.

Operators can request demo dCUSD in the UI when the deployment is configured. The default demo amount is capped for testing so campaign creation remains realistic and predictable.

The demo token is not a production asset. It exists to make local development, Sepolia walkthroughs, and integration testing easier.

Getting Started

Prerequisites

• Node.js 20+
• npm 7+
• a wallet supported by RainbowKit
• Sepolia ETH for gas when testing on Sepolia
• Supabase project values for the frontend
• TokenOps and Zama-compatible network configuration

Install And Run The Frontend

cd frontend
npm install
cp .env.example .env
npm run dev

Open:

http://localhost:3000

Useful commands:

npm run check
npm run type-check
npm run lint
npm run build
npm run start

Compile And Test Contracts

cd hardhat
npm install
cp .env.example .env
npm run compile
npm run test

Deploy the demo token to Sepolia:

npm run deploy:sepolia

Environment Setup

The frontend and Hardhat packages each include their own .env.example.

Frontend configuration typically includes:

• Supabase URL and anon key
• wallet and network configuration
• TokenOps factory and contract addresses
• demo token and demo faucet configuration
• delegated airdrop signer key for batch claim signature generation

Hardhat configuration typically includes:

• Sepolia RPC URL
• deployer private key
• explorer verification key, if verifying contracts

Never commit private keys, delegated signer keys, RPC secrets, or production credentials.

Running A Local Product Walkthrough

1. Start the frontend.
2. Connect a wallet on /app.
3. Create a workspace if the wallet has not onboarded before.
4. Request demo dCUSD or choose another ERC-7984 token.
5. Create a distribution:
   • Disperse for direct private transfers
   • Airdrop for claim-window campaigns
   • Vesting for scheduled unlocks
6. Execute the required TokenOps steps from the campaign detail page.
7. Open /claim in the same or another wallet.
8. Reveal and claim only the allocation assigned to the connected wallet.

Operational Notes

Wallet Changes

Droptron is wallet-scoped. When the connected wallet changes, the app checks workspace access again and clears mismatched cached workspace state. This prevents one wallet from casually viewing another wallet's workspace data after account switching.

Balance Checks

Before execution, the operating wallet needs enough network gas and enough of the selected confidential token for the distribution. For confidential balances, the wallet may need to authorize a private balance reveal before Droptron can confirm readiness.

Airdrop Funding

Airdrop funding moves an encrypted amount from the operator wallet into the per-campaign airdrop clone. Droptron funds based on the campaign recipient total, then recovery controls allow an admin to withdraw remaining funds when appropriate.

Vesting Percentages

Vesting initial unlock and cliff unlock values are entered as percentages of the recipient's total allocation. For example, if a recipient has a 5,000 dCUSD grant, a 10% initial unlock means 500 dCUSD becomes available at the start, subject to the TokenOps schedule rules.

Security And Privacy Notes

Droptron reduces allocation exposure, but it does not make the entire operation invisible.

Users should understand:

• public chain activity still exists
• contract addresses and transaction hashes remain visible
• claim windows and vesting schedules are public by design
• encrypted handles may be visible, but not the plaintext values
• reveal is wallet-authorized and should be treated like a sensitive action
• delegated signing keys must be protected like production infrastructure secrets
• the demo token and local configuration are for testing only

This repository is under active development and has not been independently audited.

Development Standards

Before opening or shipping changes:

cd frontend
npm run check

For contract changes:

cd hardhat
npm run compile
npm run test

The codebase is organized around product features rather than isolated demos. UI components, TokenOps flow helpers, campaign lifecycle logic, workspace onboarding, and claim portal screens are separated so the product can keep growing without turning into one large script.

Roadmap

Droptron's current product foundation supports real confidential distribution operations. The next natural extensions are:

• stronger team and multi-operator workspace management
• safer production delegated signer infrastructure
• more registry token metadata and chain support
• recipient notifications and shareable claim links
• deeper admin recovery and disclosure workflows
• audit-focused receipts and export views
• production hardening for contract, backend, and signer infrastructure

License

See LICENSE.