Skip to Content
Use CasesCommunity Airdrop

Community Airdrop

Use this pattern when you have a prepared recipient list and want a controlled distribution flow.

Typical Scenario

You are running a campaign for existing community members such as Discord contributors, governance participants, or event attendees. You already have a wallet list or can export one from your community tooling.

Image
Community airdrop scenario

Create Airdrop type step with `Onchain List` selected for a prepared community recipient list.

Goal

Send a defined amount of tokens to a known set of wallets without asking users to self-register inside Bonkit.

Why This Fits Bonkit

  • Airdrop Studio works well when you want a campaign with setup, funding, and monitoring
  • Both Onchain List and Claim-based (Merkle) assume you already prepared the recipient set
  • Onchain List is a good fit when you want recipient entries stored directly onchain and the campaign has 500 recipients or fewer
  • Multi Sender is available if you want direct transfers instead of a campaign flow
  1. Prepare the wallet list and amount rules.
  2. Make sure the token already exists in My Tokens or create it first.
  3. Open Create Airdrop.
  4. Choose Onchain List if the campaign has 500 recipients or fewer.
  5. Complete recipients and funding in Recipients and Deposit.
  6. Launch and monitor the campaign in Launch and Monitoring.

Example Setup

Your team wants to reward 500 community members who joined a testnet event.

  • Every eligible wallet gets the same amount
  • The wallet list is already available as CSV
  • The campaign should go live right after the announcement

In this case, the cleanest flow is:

  1. Import or confirm the token in My Tokens.
  2. Create an airdrop draft.
  3. Upload the CSV in Recipients and Deposit.
  4. Fund the campaign vault.
  5. If the token will trade publicly, seed the official liquidity pool before the public announcement or campaign start.
  6. Start the campaign after the announcement is published.
Image
Community airdrop flow

Airdrop detail view after recipients and deposit are complete and before `Start Airdrop` is clicked.

Launch Safety

  • If recipients are likely to trade the token, publish the airdrop only after the official liquidity pool is live.
  • This sequencing can reduce the chance that a third party creates the first pool at a distorted price or uses thin liquidity to buy airdropped tokens back from recipients.
  • If the token is not meant to trade yet, keep the distribution private and avoid presenting it like a live market launch.

Key Decisions

  • Choose between Onchain List and Claim-based (Merkle) based on storage model and recipient count, not on whether you already know the recipients.
  • Use Onchain List when the campaign has 500 recipients or fewer. Use Claim-based (Merkle) when it has more than 500.
  • Use Airdrop Studio if you want campaign structure and monitoring.
  • Use Multi Sender if you only need direct sends and do not need a public campaign page.
  • Use a clean CSV with verified wallet addresses before you upload it.
  • If the token will be tradable at launch, treat liquidity setup as part of the launch checklist, not something to do after the airdrop starts.

Common Mistakes

  • Mixing community wallets from multiple campaigns into one CSV without review
  • Starting the campaign before recipients and funding are complete
  • Letting the token reach recipients before an official liquidity pool exists when immediate trading is expected
  • Using the wrong mint because the token was not checked in advance
Last updated on
Multi SenderReward Early Users