FAQ
What is Bonkit best used for?
Bonkit is best used for running self-hosted Solana airdrop campaigns with the CLI or embedding eligibility checks and claim transactions inside your own app with the SDK.
Does Bonkit hold my assets?
No. Bonkit is non-custodial. Transactions are executed directly from the wallet or keypair you control.
Do I need SOL in my wallet to use Bonkit?
Yes. Executing an airdrop requires SOL in the signing wallet to cover Solana network transaction fees.
Which tool should I start with?
Use:
- Airdrop Studio CLI when you want a configurable local studio and a deployable claim site
- Airdrop SDK when you want to embed eligibility and claim transactions in your own app or backend
I already have a token. Do I need to create a new one?
No. The CLI’s Draft step accepts any existing SPL mint address and auto-fetches decimals, symbol, and name.
What is the claim site?
The claim site is the static Vite + React app produced by Generate App in the CLI. Recipients visit it to connect a wallet, check eligibility, and claim their allocation.
What is the difference between onchain and merkle claim modes?
onchain mode stores recipient entries directly on-chain, which makes the model easier to inspect but increases on-chain storage needs. It is recommended for campaigns with 500 recipients or fewer. merkle mode stores a root commitment and verifies proofs at claim time, which is recommended for campaigns with more than 500 recipients because it keeps on-chain storage overhead lower.
How many wallets can an airdrop support?
Campaigns with 500 wallets or fewer fit onchain mode well. Campaigns with more than 500 wallets should use merkle mode, which scales better for larger recipient sets. The CLI enforces a MAX_RECIPIENTS = 10,000 upper bound per airdrop.
Should I use the CLI or the SDK?
Use the CLI when you want a configurable studio, an on-chain campaign created interactively, and a generated claim site you host yourself.
Use the SDK when you want to drive transactions programmatically from your own app or backend, or when you want the claim experience embedded inside an existing UI.
Why does my token symbol not appear on Solscan?
Solscan has its own token reputation system, so a token symbol may not appear immediately in the explorer even if the mint itself is valid and usable.
If this happens, check Solscan’s explanation here:
Example explorer view where the token symbol is not shown yet because Solscan reputation or indexing has not surfaced it.
Where should I go if I am completely new?
Start with Overview and Quick Start.