Airdrop

Publish a list, let people take their own.

You paste the list and deposit the tokens; the contract stores a fingerprint of the list (a Merkle root) and nothing else. Recipients claim their own row — anyone can submit the claim for them, so a project can pay the gas for people who have none. Whatever is unclaimed when the deadline passes goes back to you.

New campaign

One per line: address then amount. The list itself never goes on chain — only its fingerprint does.
After this moment you can take back whatever nobody claimed. Until then nobody — including you — can touch the rest.
Before you sign
Paste the list — the summary appears here, in one sentence.

Campaign live

The file your recipients need

The root commits to the list, but it cannot reproduce it — a hash is a fingerprint, not a dossier. So creating a campaign writes a small JSON file: publish it (in your Discord, on your site, anywhere your holders are). The claim page rebuilds the root from that file and refuses it if it does not match the chain, so a wrong or edited copy cannot be used to claim.
Campaigns

Everything running right now.

#TokenChainPoolClaimedDeadline
Reading…

If it fails — self-check

  • Publish the claim file. The chain stores only the Merkle root; without the file a claimant cannot build a proof. The download button gives you the exact file.
  • The root must match. The page compares your file's root with the campaign's root and refuses a mismatch before anything is signed.
  • The claim goes to the address in the row, not to whoever submits it. Anyone can pay the gas for someone else's row.
  • After the deadline the creator can sweep only the unclaimed remainder; claims stop once it is swept.