Airdrops
Distribute tokens to thousands of addresses in batch transactions. CSV upload, gas-efficient, multi-chain.
Overview
ChainPortal's airdrop feature lets you distribute tokens to multiple recipients in a single batch transaction, saving significant gas compared to individual transfers.
How Airdrops Work
Select your token
Choose the token you want to airdrop from your deployed assets.
Prepare recipient list
Upload a CSV file with addresses and amounts, or enter them manually.
Review distribution
Verify the total amount, number of recipients, and estimated gas cost.
Approve token spending
Approve the airdrop contract to spend your tokens (ERC20 approval).
Execute airdrop
Send the batch transaction. All recipients receive tokens in one transaction.
CSV Format
Prepare your airdrop CSV with two columns:
Tip: Amounts should be in human-readable format (e.g., 1000 for 1000 tokens). ChainPortal handles decimal conversion automatically.
Supported Ecosystems
The maximum number of recipients per transaction is set by each chain's airdrop contract. The app sends a longer list in several batches.
| Ecosystem | Max Recipients per TX | Gas per Recipient |
|---|---|---|
| 500 | ~$0.01-0.50 | |
| 20 | ~$0.001 | |
| 500 | ~$0.005 | |
| 500 | ~$0.002 | |
| 500 | ~$0.001 | |
| 25 (native NEAR); 10 (tokens, new contract) | ~$0.005 |
Duplicates, Batching and Results (new contracts)
Shown only after the new airdrop contract is deployed on that chain. The behaviour below applies once the app has confirmed the chain's airdrop is the new build (on Cosmos the sorted, de-duplicated list is always used, because every Cosmos airdrop build accepts it). An older contract keeps today's behaviour.
- Duplicates are handled before you sign. The app shows a line-by-line report of your list. When everyone gets the same amount, repeated addresses are removed. When you use custom amounts (CSV), repeated addresses are merged into one transfer with the amounts added together, which is what an older contract would have paid in total.
- Sorted lists. The new contracts reject duplicate recipients, and on EVM, SUI, Aptos and Cosmos they require recipients in a fixed order. The app sorts the list for you.
- Automatic batching. A list longer than the chain's limit is sent as several transactions, with "batch i of n" progress. On EVM each batch is checked before you sign it (order, zero amounts, your token allowance and balance).
- Skipped transfers (EVM). If a transfer to one recipient fails, the new EVM airdrop skips that recipient instead of failing the whole batch. A skipped token transfer never leaves your wallet, and a skipped ETH transfer is refunded to you. The result screen lists every skipped recipient.
- Results on every chain. After each batch the app reads the airdrop's result from the chain and shows what was delivered.
NEAR: token airdrops by anyone, and failed transfers
- With the new NEAR airdrop contract, anyone can airdrop a fungible token (previously only the
contract owner could). The tokens are sent to the airdrop together with the instructions in one
ft_transfer_call, 10 recipients per batch. The app first registers the airdrop on the token and adds a small storage deposit if needed. If the contract refuses a batch, the tokens are refunded and the app shows the reason, so you can send that batch again. - Failed transfers are credited, not lost. If one recipient cannot receive (for example, the account is not registered on the token), that amount is credited to you in the airdrop contract. The Failed transfers card lists your credits (native NEAR on every airdrop build, tokens on the new one) and lets you withdraw them.
Best Practices
- Test first -- Always test with a small batch on testnet before mainnet
- Check balances -- Ensure you have enough tokens AND gas for the full batch
- Verify addresses -- Double-check all recipient addresses are valid
- Large airdrops -- The app sends long lists in batches. Check each batch's result before you top up and retry