How to Airdrop Tokens to Thousands of Wallets on Solana#

Token airdrops are the fastest way to build an initial community, reward early supporters, and distribute supply to real holders. On Solana, sending tokens to hundreds or thousands of wallets requires batching transactions efficiently — which is exactly what Jump2Coin's Multisender handles automatically.

This guide covers how to prepare your recipient list, configure the airdrop, and execute it safely.

Why Airdrop on Solana?#

Solana's low fees make airdrops economically viable at scale. Sending tokens to 1,000 wallets on Ethereum might cost thousands in gas. On Solana:

• Base transaction fee: 0.00005 SOL ($0.009) per transaction
• Each transaction can include up to 10 token transfers
• 1,000 recipients = ~100 transactions = ~0.005 SOL in Solana fees

The Jump2Coin Multisender handles batching automatically. You paste your list; it figures out the rest.

Step 1 — Prepare Your Token#

Your token must already exist (create one at /create) and you must hold enough tokens in your connected wallet to cover the full airdrop amount.

You'll also need enough SOL for:

• Platform fee: 0.001 SOL × number of recipients
• Solana network fees: ~0.00005 SOL per batch transaction
• ATA rent: ~0.002 SOL per recipient that doesn't already have a token account (automatically created)

Step 2 — Prepare Your Recipient List#

The Multisender accepts a simple text format — one recipient per line:

WalletAddress1, 100
WalletAddress2, 250.5
WalletAddress3  500

Supported separators: comma, tab, or space. Amount can be a decimal number.

Tips for building a good list:

• Export holder snapshots from tools like Solana FM or Helius
• Deduplicate addresses before uploading — the tool processes each line as-is
• Verify addresses are real wallet addresses, not program addresses or burn accounts
• Test with a small list (5–10 addresses) on devnet first

CSV format is also supported. The first column should be the wallet address, the second the amount.

Step 3 — Enter the Token Mint Address#

Navigate to /airdrop and paste your token's mint address. Click Verify — the tool fetches the token's decimal precision from on-chain, which is required to convert your human-readable amounts to raw token units correctly.

You'll see confirmation: Token verified — Decimals: 9

Step 4 — Paste or Upload Your List#

Paste your recipient list directly into the text box or click Upload CSV to upload a file.

After entering addresses, click Parse & Review. The tool will:

• Validate every wallet address
• Convert amounts to raw token units using the correct decimals
• Separate valid from invalid lines
• Show a preview of all recipients

Any lines that fail validation appear in a collapsible Invalid Lines section with the reason:

• Invalid wallet address — malformed or non-existent address
• Amount must be a positive number — zero or negative amounts
• Amount rounds to zero at token decimals — amount too small for token precision

Invalid lines are skipped — they do not block the airdrop.

Step 5 — Review the Airdrop#

The Review screen shows a summary:

You can also browse the full recipient table (first 20 shown; all are included).

Double-check recipient count and amounts before proceeding. Airdrop transactions cannot be undone.

Step 6 — Send the Airdrop#

Click Send Airdrop. For each batch of 10 recipients, Phantom will ask you to sign a transaction. Here's what each transaction contains:

• Priority fee instruction
• Compute budget instruction
• Platform fee transfer (first batch only — total fee collected once)
• For each recipient:
  • createAssociatedTokenAccountIdempotentInstruction — creates ATA if missing, no-op if exists
  • transferChecked — transfers the exact token amount

Important: Do not close the browser tab while the airdrop is in progress. If a batch fails, you can retry — the tool shows success/failure per batch and continues to the next batch even if one fails.

Step 7 — Review Results#

After all batches complete, the Done screen shows:

• Per-batch success/failure status
• Transaction signatures with Solana Explorer links
• Total recipients served

Failed batches can be re-run manually by checking the failed addresses against your original list and re-sending only those.

Large-Scale Airdrop Tips#

Use a fresh connection — RPC rate limits can cause intermittent failures during large airdrops. If you experience consistent failures, switch to a dedicated RPC endpoint (Helius, Alchemy, QuickNode).

Run in segments — For 10,000+ recipients, split into multiple sessions of 1,000–2,000 per run. Keeps session time manageable and reduces the impact of any failures.

Pre-create ATAs — If you're doing a massive airdrop, consider pre-creating all ATAs in a separate pass to reduce per-transaction compute costs.

Batch during low-traffic hours — Solana congestion is highest during US evening hours. Airdrops run faster and more reliably in off-peak windows.

Verify before sending — The preview table shows the first 20 addresses. For critical airdrops, export the full list and verify recipient counts independently.

Frequently Asked Questions#

What if a recipient already has a token account? The tool uses createAssociatedTokenAccountIdempotentInstruction — it silently skips ATA creation if the account already exists. No extra cost.

Can I send SOL instead of tokens? No — the Multisender is designed for SPL token transfers. For SOL distributions, use a regular multi-send tool or write a script.

Does the Multisender work with Token-2022 tokens? Currently, the Multisender targets the standard SPL Token program. Token-2022 support is planned.

What is the maximum number of recipients? There is no hard limit imposed by Jump2Coin. Practical limits depend on your SOL balance for rent and fees, and your patience for the session length.

Can I airdrop to Solana Mobile users or hardware wallets? Yes — any valid Solana wallet address is supported regardless of the wallet type.

What happens if the airdrop session disconnects mid-way? Completed batches are already confirmed on-chain. Only unconfirmed batches need to be re-sent. Check the batch results screen and re-run failed addresses.