This guide helps operators run a local or Sepolia walkthrough of Droptron.
Prepare:
- a wallet with Sepolia ETH
- frontend
.envvalues - Supabase project values
- TokenOps/Zama-compatible network configuration
- demo token configuration if using dCUSD
- at least one recipient wallet for claim portal testing
cd frontend
npm install
cp .env.example .env
npm run devOpen:
http://localhost:3000
cd hardhat
npm install
cp .env.example .env
npm run compile
npm run deploy:sepoliaAdd the deployed address to the frontend configuration if you want the UI demo-token path to use that deployment.
- Open
/app. - Connect the operator wallet.
- Create a workspace if the wallet has not onboarded yet.
- Open
New distribution. - Choose a mode:
- Disperse for direct private payouts
- Airdrop for claim-window rewards
- Vesting for scheduled unlocks
- Select an ERC-7984 token or use the demo token if configured.
- Add recipients and amounts.
- Review the campaign.
- Open the campaign detail page.
- Complete the TokenOps operation steps.
- Open
/claimin an eligible recipient wallet. - Reveal and claim the wallet-specific allocation.
- Droptron is wallet-scoped.
- The operator gets receipts and recovery controls.
- The recipient portal does not show a public table of all recipients.
- Reveal is authorized by the connected wallet.
- Public chain activity remains visible, while allocation values remain confidential.
The operating wallet needs enough of the selected confidential token for the distribution. If the balance is private, the wallet may need to authorize a balance reveal before Droptron can confirm readiness.
Switch to the network where the campaign token and TokenOps contracts are configured.
Airdrop recipients can reveal or claim only when the claim window allows it.
The claim portal only lists records assigned to the connected wallet. If the wallet is not included, it should not see that campaign detail.