deploya tokenTools / Claim Site

Solana Airdrop Claim Site

Publish a list once and let holders claim their own airdrop. You sign one transaction however long the list is.

Solana0.1 SOL per distribution

Wallet not connected

Connect your wallet to create a claim site for an airdrop. You sign every action yourself, and nothing is custodial.

How to set up an airdrop claim site

  1. Connect the wallet holding the tokens. The whole amount is moved into the vault when the distribution is created, so it has to be in this wallet now.
  2. Paste the mint address and read the token. A Holder Snapshot CSV can be pasted straight into the list below it.
  3. Paste the recipient list: one wallet and amount per line. Anything unusable is listed back to you rather than silently dropped.
  4. Choose when it opens, and whether it releases all at once or gradually.
  5. Check the totals, then confirm. This stores the list, then asks your wallet to approve creating and funding the vault in one transaction.
  6. Share the link you get back. Everyone who opens it connects their wallet, sees their own allocation, and claims it themselves.

Common questions

How is this different from the Multisender?

Who pays, and how many transactions you sign. The Multisender sends the tokens out and charges you for every transfer, so a thousand recipients is a thousand costs on you. A claim site publishes the list, funds one vault, and then each recipient claims their own share and pays their own network cost. You sign one transaction whether the list has ten names or two thousand.

So is it free?

No, and it is worth being precise. The cost moved, it did not disappear. Each recipient pays roughly 0.002 SOL of account rent to claim, instead of you paying it for them. You pay our fee once plus the network cost of the one transaction. For a long list that is dramatically cheaper for you; for three recipients it is not worth the extra step.

Where is the recipient list kept?

We host it, and your browser checks it. Only a 32-byte fingerprint of the list, called a Merkle root, goes on chain, because putting a thousand rows there would cost more than the airdrop. The full list has to live somewhere recipients can read, so it lives on our service. Before the claim page shows anyone an amount it rebuilds that fingerprint from the list and compares it against the copy stored on chain, which is the one nobody can alter.

What if your service goes down, or you tamper with the list?

Tampering cannot pay anyone the wrong amount: an altered list produces a different fingerprint, the check against the chain fails, and the page refuses to offer a claim at all. As for downtime, you are given the same list file to download when you create the distribution. It is public data, so anyone holding it can compute a proof, and the vault on chain is unaffected either way. We are storage, not the authority.

Can I add or remove a recipient afterwards?

No. The list is committed permanently when the distribution is created, because the whole point of the fingerprint is that it cannot be changed. Check the list before you confirm. If you need to add people later, create a second distribution.

What happens to tokens nobody claims?

They stay in the vault. There is no expiry and nothing returns to you automatically, so budget for the possibility that some recipients never turn up. An unclaimed allocation is not lost to them either: they can claim whenever they get round to it.

Can a recipient claim more than they were allocated?

No, and this is enforced by arithmetic rather than by our interface. Each row's wallet address and its exact amount are both part of what the fingerprint commits to, so changing either produces a proof that does not match the root on chain and the program refuses it.

Can the same wallet appear twice in my list?

It can in what you paste, and the tool combines the entries into one holding the total and tells you it did. That is necessary rather than tidy: each recipient's claim account is derived from their wallet address, so a second entry for the same wallet could never be claimed. Combining them is what makes sure they receive everything you listed.

Can an airdrop vest instead of unlocking all at once?

Yes. Turn on the gradual release and each claim creates a vesting lock rather than a straight payment: the recipient gets whatever has unlocked and the rest stays locked in their name. Our Token Vesting tool finds it by wallet address, so they have somewhere to come back to for the remainder.

How long can the list be?

Up to 2000 recipients in one distribution. That limit is not arbitrary: the proof a recipient submits grows with the size of the list, and past roughly that point it stops fitting inside a single Solana transaction. For a bigger airdrop, split it into more than one distribution.

Which tokens work?

Standard SPL tokens. Token-2022 tokens are refused up front, and so is any token that charges a transfer fee: the claim program rejects those outright, and a fee would also mean recipients receive less than the list promises them.

Do recipients need to trust you with anything?

They need us to serve them a list, and nothing more. They do not connect a wallet to anything custodial, we never hold their tokens, and the amount they are shown is checked against the chain before they are asked to sign. If our list were wrong in any way, the check fails and they are told so rather than signing something.

What this changes

The expensive part of an airdrop is not the tokens, it is the thousand small costs of delivering them. Every transfer needs an account for the recipient to hold the token in, and someone has to pay the rent for it. With the Multisender that someone is you, a thousand times over.

A claim site inverts it. You publish a commitment to the list, fund one vault, and then anyone on the list can come and take their share. They pay for their own account. You sign twice at most, whatever the length.

The commitment, in plain terms

Putting a thousand rows on chain would cost more than most airdrops are worth, so what goes on chain is a 32-byte fingerprint of the whole list, called a Merkle root. To claim, a recipient hands the program their own row plus a short set of hashes, and the program rehashes its way up to the root. If it matches what you published, their row was in the list. If anybody edits so much as one amount, it does not match, and the claim is refused.

That is why the list itself can be public and can be hosted anywhere: the fingerprint is the part that has to be trustworthy, and it lives on Solana where nobody can quietly change it.

Who you are trusting, and with what

Worth stating exactly, because it is the fair question to ask. We host the list. That is all we do: we do not hold your tokens, we cannot alter what anyone is owed, and we are not in the claim transaction.

The claim page rebuilds the fingerprint from the list it was served and compares it against the copy on chain before it shows anyone an amount. So the worst a broken or dishonest list server can do is fail to show someone a claim. It cannot cause anyone to sign for the wrong amount. You also get the list file to download, which means the distribution keeps working from anyone who has it, whatever happens to us.

Things to get right before you confirm

  • The list is final. No adding, removing or editing a recipient afterwards. Read it once more.
  • The full amount leaves your wallet now. The vault is funded when the distribution is created, not as people claim.
  • Unclaimed tokens stay in the vault. Nothing expires and nothing comes back to you on its own.
  • Recipients need a little SOL. Roughly 0.002 for their own account. Someone with an empty wallet cannot claim, which is worth mentioning when you announce it.

Related tools

Sources