What a Snapshot Airdrop Does
A snapshot airdrop picks a specific block height on Solana, records every wallet holding a target token at that block, and sends each wallet a proportional or fixed allocation of a new token.
It is the standard mechanism for rewarding existing holders, bootstrapping a new token's distribution, or migrating from one mint to another. Used right, it produces a real, distributed holder base on day one. Used wrong, it wastes tokens on bots, sybils, and abandoned wallets.
This guide covers the full workflow as of May 2026.
[stats]
Snapshot precision | Block-level | Down to ~400ms
Cost per recipient | ~0.0001 SOL | Network fee
Setup time | 15 min | First snapshot to first send
Sybil resistance | Filter-dependent | Critical decision
[/stats]
The Three Steps
A snapshot airdrop has three phases. Each one has decisions that change the outcome significantly.
Step 1: Pick the Snapshot Source
What are you snapshotting?
- A single token mint. Most common. Snapshot every wallet holding token X at block Y. Used for migrations, holder rewards, fair drops.
- A pool LP. Snapshot every wallet that provided liquidity to pool X. Rewards active liquidity providers, not just passive holders.
- An NFT collection. Snapshot every wallet holding NFT in collection X. Common for project-aligned airdrops.
- Multiple sources. Combine. Holders of token A who also held NFT B at block Y. Filters down to highly engaged users.
The choice determines the recipient list. More restrictive choices produce smaller, more aligned recipient lists. Less restrictive choices produce larger, more diluted lists.
Step 2: Decide the Distribution
Two main models:
Pro-rata. Each wallet receives an amount proportional to its holding at the snapshot. A wallet holding 1% of supply receives 1% of the airdrop pool.
Fixed-per-wallet. Each qualifying wallet receives the same amount, regardless of holding size. Caps whale dominance.
Pro-rata is the default and the most common. Fixed-per-wallet is increasingly popular for token-distribution-fairness narratives, particularly for projects that want to encourage broad community ownership.
A common hybrid: pro-rata up to a cap. Wallets receive a share proportional to holdings, but no wallet receives more than 1% of the airdrop pool. Limits whale capture without abandoning proportionality entirely.
Step 3: Filter Sybils
This is where most airdrops fail.
A sybil is someone who controls many wallets and qualifies multiple times for what should be a single allocation. In 2026 Solana, sybil attacks on airdrops are professionalized: services exist that will spread a single user's funds across thousands of wallets to maximize airdrop yield.
Three filters that meaningfully reduce sybil impact:
Minimum holding duration. Require that the wallet held the source token for at least N days before the snapshot. A wallet that bought one block before snapshot doesn't qualify.
Activity threshold. Require N on-chain transactions in the 30 days before snapshot. Filters out wallets created just for the snapshot.
Cross-reference with known bot wallets. Many wallet databases tag known sybil farms. Exclude these. Imperfect (false negatives are common) but catches the easy cases.
A token without sybil filtering can lose 70%+ of its airdrop pool to sybil wallets. With even basic filtering, that drops to under 20%.
Tools for Running the Airdrop
Three paths, increasing in capability.
Path 1: Manual via spl-token CLI
Possible but tedious. You write a script that iterates the recipient list and calls spl-token transfer for each. Works for small airdrops (under 100 recipients). Falls over at scale because each transfer is a separate transaction.
Path 2: Batched via custom script
Combine multiple transfers into one transaction. Solana supports up to ~25 SPL transfers per transaction depending on instruction size. Reduces gas cost and time significantly. Requires custom code.
Path 3: ManagerNest Snapshot Airdrop tool
The simplest path. The ManagerNest Snapshot Airdrop tool handles the snapshot, sybil filtering, batched sends, and post-send verification in one flow.
Steps:
- Connect wallet.
- Paste the source token mint and choose a snapshot block (default: latest finalized).
- Set the filter rules (minimum holding, activity threshold).
- Choose the distribution model (pro-rata or fixed-per-wallet).
- Paste the airdrop token mint and the total amount.
- Review the recipient list.
- Sign one transaction per batch of ~20 recipients.
Platform fee is 0.1 SOL flat plus network fees per batch. For an airdrop to 5,000 wallets, total cost is approximately 1.5 SOL all-in.
Gas Math
Network fees scale with recipient count. Here is the rough math:
The platform-fee component (if you use a tool) is a flat addition on top.
For very large airdrops (50,000+ recipients), some teams choose a claim-based model instead: the airdrop is announced and each recipient claims their tokens on-demand. Saves the team's upfront cost; pushes the network fee onto the recipient. Whether this is fair or extractive depends on the airdrop size per recipient.
Common Mistakes
Three mistakes that ruin airdrops:
Snapshot too late. If you announce the airdrop before taking the snapshot, sybils have time to set up wallets that qualify. Always take the snapshot first, then announce. The block is on-chain; nobody can game it retroactively.
Forgetting test runs. Before the real send, do a 100-recipient dry run with a small amount of your token. Verify the transactions land correctly, the recipients see the tokens in their wallets, the metadata is correct.
Ignoring associated token accounts. If a recipient's wallet doesn't already have a token account for your mint, the send creates one and pays ~0.002 SOL in rent. Across 10,000 wallets, that's 20 SOL extra. The ManagerNest tool handles this, but a custom script must.
How to Verify the Airdrop Landed
After sending:
- Pick 20 random recipient wallets from your list.
- Check each one in Solscan or DexScreener.
- Verify the airdrop token shows up with the correct amount.
If all 20 are clean, the send is good. If even one is wrong, dig in: usually it's a missing token account or a wrong decimal multiplier.
Communication Around the Airdrop
The mechanics are half the work. The communication is the other half:
Announce the snapshot block before sending. Even though the snapshot already happened, telling recipients which block was used builds trust.
Provide a checker tool. A simple page where any wallet can paste their address and see how much they qualify for. ManagerNest's tool generates this automatically; for custom scripts, build one.
Publish the recipient list (or its merkle root). Full transparency. Skeptics can verify their own qualification and that no special wallets were added.
Frequently Asked Questions
Can I airdrop to wallets that don't have my token account yet?
Yes. The send instruction can create the associated token account in the same transaction. Costs ~0.002 SOL per new account.
Can I take a snapshot of a historical block?
Yes. Solana RPC supports historical block queries up to several months back. Helius and other paid RPC providers go further. The free public RPCs go back about a week.
Can I cancel an airdrop after sending?
No. Once tokens land in a recipient's wallet, only that recipient can move them.
Is there a way to airdrop without paying for new token accounts?
Yes: use the claim-based model. Tokens are deposited in a claim contract, recipients pay to mint into their own wallet when they claim. Shifts cost to the recipient.
How long does an airdrop to 5,000 wallets take?
About 20 minutes if batched properly, including transaction confirmations. The ManagerNest tool runs in parallel where possible to compress this.