Airdrops

Airdrops let you distribute your token to a list of recipients or via an open claim link, without handing custody of your supply to anyone. You keep the tokens in your own wallet and approve a spending allowance; recipients claim, and the tokens transfer straight from your wallet to theirs.

Non-custodial by design

Chain Daddy never holds or mints your airdrop supply. You approve an allowance to the distributor wallet, and the system pulls exactly the claimed amount from your wallet per claim. Revoke the allowance any time to stop distribution.

How It Works

1. You create a campaign and choose a mode: Allowlist or First-come-first-serve (FCFS).
2. You set the token, the per-claim amount, and a total budget.
3. You approve a spending allowance from your funding wallet to the distributor address shown in the campaign — an ERC-20 approve on EVM chains, an SPL token delegate on Solana.
4. You activate the campaign and share its claim link.
5. A recipient connects their wallet, proves ownership with a signature, and the token transfers from your wallet to theirs.

No tokens move until someone claims, and each claim pulls only that recipient's amount.

Choosing a Mode

Mode	Best for	How recipients qualify
Allowlist	Rewarding a known set of wallets or social accounts	You upload the list; only those identities can claim (with optional per-recipient amounts)
FCFS	Open campaigns, faucets, community growth	Anyone with the link can claim a fixed amount until the budget runs out, subject to an optional anti-sybil gate

Creating an Airdrop

Airdrops live next to Community in your Token Manager — switch to the Airdrops tab with the toggle at the top, then create a campaign.

1. Navigate to your Token Manager page
2. Open the Airdrops tab (toggle at the top of the Community view)
3. Click Create Airdrop
4. Configure the campaign:
   • Name: Display name shown on the claim page (required)
   • Mode: Allowlist or FCFS (required)
   • Chain: The chain your token lives on (required)
   • Token address: The ERC-20 contract address of the token you're distributing (required)
   • Amount per claim: How much each recipient receives (required for FCFS; the default for allowlist entries with no per-recipient amount)
   • Total budget: The maximum total you're committing to distribute (required)
   • Funding wallet: The wallet that holds the tokens and will grant the allowance (required)
   • Description: Optional context shown on the claim page
   • Gas cap (FCFS, optional): auto-pause the campaign once a set amount of network gas (in the chain's native coin) has been spent distributing it — a spend ceiling for open-ended campaigns
   • Eligibility gate (FCFS, optional): require a verified social account and/or a minimum token holding to claim — see Eligibility Gates
5. Click Save

The campaign is created in draft status. It is invisible to the public until you activate it.

Funding the Distributor

In the non-custodial model, you fund a campaign by approving a spending allowance — not by sending tokens to Chain Daddy.

1. Open the campaign. It displays the distributor address to approve.
2. From your funding wallet, grant the distributor address an allowance of at least your total budget (in the token's base units): approve on your token contract on EVM chains, or approve the distributor as your token account's delegate on Solana. The campaign's funding panel has a one-click approval for both.
3. Confirm the allowance landed. The campaign health panel shows whether your funding wallet's balance and allowance cover the budget.

WARNING

Keep enough balance and allowance in the funding wallet to cover outstanding claims. If either falls below a claim amount, that claim fails and the campaign auto-pauses so you're alerted before more claims fail. Top up and re-activate to resume.

Eligibility Gates (FCFS)

FCFS campaigns are open to anyone with the link, so you can attach an eligibility gate to filter out bots and repeat claimers:

• Verified social: the claimant must claim with a wallet that has a verified social account attached. This is the strongest gate — wallets are free to create in bulk, but aged social accounts are not.
• Minimum token hold (EVM chains): the claimant's wallet must hold at least a set amount of a token you choose, on a chain you choose.

Minimum hold is best-effort

The minimum-hold check is a point-in-time balance read. A determined claimer can borrow tokens just long enough to pass it, so treat it as a speed bump, not a hard guarantee. When sybil resistance really matters, use the verified-social gate (optionally combined with min-hold) and keep per-claim amounts modest.

Every campaign also gets built-in protections regardless of gates: one claim per wallet, one claim per social identity, and per-IP rate limiting.

With no gate configured, an active FCFS campaign is an open faucet — anyone with the link can claim until the budget runs out. That can be exactly right for a growth campaign; just size the budget (and gas cap) accordingly.

Uploading a Recipient List (Allowlist mode)

For allowlist campaigns, upload the recipients who are allowed to claim:

1. Open the campaign and go to the Allowlist section
2. Upload a CSV of recipients. Each row is one identity:
   • A wallet address, or a social handle (with its platform)
   • An optional amount for that recipient (base units). Leave blank to use the campaign's default per-claim amount
3. Save the upload

You can upload up to 10,000 entries per upload, and upload more than once to grow the list. Re-uploading the same identity updates its amount.

Activating and Sharing

1. Make sure the campaign is funded (budget set, per-claim amount set, allowance approved)
2. Set the campaign status to active
3. Share the claim link from the campaign. Recipients open it, connect their wallet, and claim.

You can pause an active campaign at any time to stop new claims, then activate it again later. Mark it completed or cancelled when you're done.

Claimant Experience

When a recipient opens your claim link:

1. They see the campaign name, the token, and the amount they can claim
2. They connect their wallet and sign a message to prove they own it (no gas, no transaction to sign for the claim itself)
3. The system checks eligibility:
   • Allowlist: their wallet or social identity must be on your list
   • FCFS: the budget must not be exhausted, and they must pass any anti-sybil gate you set (for example, a minimum token-hold requirement)
4. If eligible, the token transfers from your wallet to theirs, and they see the transaction hash

Each recipient can claim once. A wallet can claim at most once per campaign, and a social identity can claim at most once even if the recipient tries a different wallet.

Reading Campaign Health

The campaign panel and the Analytics tab show a few numbers worth understanding:

Stat	Meaning
Total budget	The most this campaign will ever distribute.
Claimed	Tokens already confirmed on-chain to claimants.
Reserved	Tokens set aside for claims still in flight — accepted but not yet confirmed on-chain. Each reservation either becomes Claimed or is released back to the budget if the claim fails.
Remaining	Budget minus claimed and reserved — what new claimants can still get.
Claims / unique claimants	How many claims have been made, and by how many distinct wallets.
Claim rate	Of claims started, the share that completed. A falling rate usually means an underfunded wallet, or an eligibility gate doing its job.

The health panel also checks your funding live: it compares your funding wallet's balance and allowance against the remaining budget, so you can top up before claims start failing.

Gas and the Gas Cap

Chain Daddy's distributor pays the network gas for every distribution. Claimants sign a free message — no transaction on their side — and your only gas cost is the one-time approve from the funding wallet.

For FCFS campaigns you can set an optional gas cap: once that much of the chain's native coin has been spent distributing your campaign, it auto-pauses (the same way an underfunded campaign does). This keeps an open-ended campaign from running longer than you intended. Leave it empty and distribution continues while the budget lasts.

Claim Statuses and Troubleshooting

A claim moves through these statuses:

Status	Meaning
Pending	The claim was accepted and budget reserved; the transfer is about to be sent.
Submitted	The transfer transaction is on its way to the chain. Most claims confirm within a minute.
Confirmed	The transfer landed on-chain — the claimant has the tokens, and the claim page links the transaction.
Failed	The transfer could not be completed. The reserved amount is released back to the budget, and the claimant can try again.

For claimants:

• "Not eligible" — on allowlist campaigns, your wallet or social identity isn't on the operator's list (ask them to add you). On FCFS, an eligibility gate wasn't met or the budget is exhausted.
• "Already claimed" — each wallet and each social identity can claim once per campaign, even from a different wallet.
• Stuck on submitted — the network is busy; the claim confirms automatically once the transaction lands. If it ultimately fails, the claim is released and you can try again.
• Campaign paused — the operator paused it (often to top up funding). Try again later.

For operators:

• Campaign auto-paused — your funding wallet's balance or allowance dropped below a claim amount, or the gas cap was reached. Top up / re-approve (or raise the cap), then set the campaign active again.
• Claims failing on one campaign only — double-check the token address and decimals on that campaign; a wrong decimals setting moves the wrong magnitude.

Tips and Limits

Aspect	Detail
Custody	Non-custodial — tokens stay in your funding wallet until claimed
Claims per recipient	One per wallet, and one per social identity, per campaign
Allowlist size	Up to 10,000 entries per upload (upload repeatedly for more)
Budget guard	Claims can never exceed your total budget; the distributor reserves each claim atomically
Underfunding	A claim that exceeds your available balance/allowance fails and auto-pauses the campaign
Gas	Chain Daddy pays the distribution gas; you only pay to approve the allowance. FCFS campaigns can set a gas cap that auto-pauses when reached
Supported chains	Arbitrum, Avalanche, Base, Polygon, BNB Chain, Ethereum, Gnosis (ERC-20) and Solana (SPL)

Revoke to stop

Because distribution is allowance-based, you can stop all future claims instantly by revoking the distributor's allowance on your token contract, or by pausing the campaign.

FAQ

Do I send my tokens to Chain Daddy?

No. Your tokens stay in your own wallet until the moment a claim is confirmed. You grant the distributor address a spending allowance capped at your budget, and each claim transfers directly from your wallet to the claimant. Revoking the allowance stops everything instantly.

As a claimant, is anything at risk when I claim?

No. You sign a short message that proves you control your wallet — a signature is free, moves nothing, and grants no permissions over your funds. The token transfer itself is sent and paid for by the distributor; you never submit a transaction or approve anything.

Why do I have to sign a message to claim?

The signature proves the claim request really comes from the owner of the receiving wallet, and it is bound to this specific campaign — it can't be reused anywhere else. Without it, anyone could claim tokens into someone else's address (or pretend to be you).

What happens if my funding wallet runs low mid-campaign?

The next claim that can't be covered fails safely and the campaign auto-pauses so no further claims are attempted. Top up the wallet (or re-approve a larger allowance) and set the campaign active again — nothing is lost, and the failed claimant can claim again.

Can I run an airdrop for a token on Solana?

Yes. Solana airdrops work the same non-custodial way as EVM ones: instead of an ERC-20 allowance, your funding wallet approves the distributor as an SPL token delegate for up to your budget, and each claim transfers straight from your wallet to the claimant. Pick Solana as the campaign's chain and the funding panel walks you through the delegate approval.