Create Airdrop with the CLI

Create Airdrop

This section creates the airdrop as a series of real Solana transactions. The studio guides you through four required steps and a completion view.

Airdrop creation mutates on-chain state. Start on devnet when you are trying the flow for the first time.

Four On-chain Steps

Draft

Create the airdrop account on-chain.

Recipients

Append recipient wallets and allocations. The studio batches 16 entries per transaction.

Deposit

Transfer the full allocation total into the campaign vault.

Start

Activate the airdrop. End-users can claim from this point.

Step 1. Draft

Create the airdrop account.

Inputs:

Network — devnet or mainnet-beta
RPC URL — use a public endpoint on devnet; on mainnet, use your own
Token Mint Address — the studio auto-fetches decimals, symbol, and name
Claim Mode — onchain or merkle
Schedule — start and end date (optional at this step; finalized in Start)

After the draft is created, Network and Token Mint cannot be changed. To switch, reset the airdrop from the panel and start the draft again.

Result: airdropAddress and draftSignature are recorded in .bonkit/workspace.json.

Step 2. Recipients

Input methods:

Quick add — type one recipient at a time
Upload CSV — drop a .csv file
Paste — paste rows from a spreadsheet

Limits:

MAX_APPEND = 16 entries per transaction
MAX_RECIPIENTS = 10,000 total per airdrop

Batch progress is tracked across two files. .bonkit/batch-draft.json holds the in-progress slice — the not-yet-submitted entries and the current position. .bonkit/batch-history.json records each successfully submitted batch (signature, size, timestamp). If the process is interrupted, the next session reads batch-draft.json to resume the remaining entries and uses batch-history.json as the append-only record of what already landed on-chain.

Result: recipientsSignature is recorded and the complete batch history is saved.

Create Airdrop Recipients step with batch progress — Recipients step

Step 3. Deposit

Transfer the full allocation total into the campaign vault.

The panel shows:

Wallet token balance
Vault balance (real-time polling)
Required deposit amount — sum of all registered allocations
Transfer fee estimate for fee-bearing tokens

Result: depositSignature is recorded.

Step 4. Start

Activate the airdrop after verifying the pre-condition checklist.

Pre-condition checklist:

Draft created on-chain
Recipients registered
Tokens deposited
Schedule set (optional)

Schedule editing is available at this step. Start and end dates are written on-chain in the Start transaction.

Result: startSignature is recorded and the airdrop is live.

Completion

The completion view summarizes all four transactions. The full activity log is at .bonkit/activity-log.json.

Reset

The airdrop panel has a Reset action that clears the airdrop fields in workspace.json so you can choose a different network, mint, or claim mode.

Reset only clears the local studio references. Already-created on-chain accounts remain on-chain.

Common Issues

Insufficient SOL → the wallet needs SOL for transaction fees.
Insufficient token balance → the wallet must hold at least the deposit total.
RPC rate limit exceeded → on mainnet, use your own RPC endpoint. Public RPCs will rate-limit batch transactions.
Mint not supported → the token may use a Token-2022 extension that the airdrop program rejects. The Draft step surfaces the specific reason.

Next Step

Continue to Signing Modes to choose between a browser wallet and a local keypair.