Skip to Content
Run Your First Airdrop1. Create Draft

Create Draft

Create the campaign shell first. This step does not add recipients or move tokens yet. It only creates the draft that the rest of the tutorial will build on.

Estimated time: 5-10 minutes

In this tutorial you will:

  • Create an airdrop draft
  • Add recipients
  • Deposit tokens
  • Launch the campaign

UI Elements

  • Step tabs: Type, Schedule, Select Token, Review
  • Back and Next navigation between steps
  • Main action on the final step: Create Draft
  • Success actions: Back to Airdrops, Go to Airdrop Draft
Image
Create Airdrop wizard

Create Airdrop wizard showing the full draft setup flow and step navigation.

Step 1. Type

This step decides the campaign identity and distribution model.

For this tutorial, choose Claim-based (Merkle). The rest of the walkthrough assumes a proof-based campaign flow.

This tutorial uses Claim-based (Merkle). Pick this option so the later recipient upload and claim steps match the walkthrough.

UI elements:

  • Campaign Name
  • Distribution Type
  • Onchain List
  • Claim-based (Merkle)

What to do:

  1. Open Create Airdrop.
  2. Enter a clear Campaign Name.
  3. In this tutorial, choose Claim-based (Merkle).
  4. Use Onchain List when you have 500 recipients or fewer and want direct onchain recipient storage instead of the proof-based flow shown here.
  5. Click Next.

Helpful detail from the product UI:

  • When Onchain List is selected, the UI shows a note that Merkle is recommended for campaigns with more than 500 recipients.
  • The step description in the app is Campaign basics.
  • Claim-based (Merkle) is the tutorial path because the later steps assume merkle upload and claim-style distribution.
OptionBest forWhat it storesWhat to remember
Onchain ListCampaigns with 500 recipients or fewerRecipient entries directly onchainEasier to reason about, but onchain storage grows with the list
Claim-based (Merkle)Campaigns with more than 500 recipientsA compact root onchain, with proofs checked during claimsBetter for scale, but requires the proof-based flow used in this tutorial

Common mistake:

  • moving forward without a real campaign name
Image
Type step

Type step showing the campaign name input and the distribution type options for the draft.

Step 2. Schedule

This step controls when the campaign becomes available after launch.

UI elements:

  • Start Date (optional)
  • End Date (optional) for onchain campaigns
  • End Date for merkle campaigns
  • date and time pickers with Apply
  • Clear actions for existing values

What to do:

  1. Leave Start Date (optional) blank if the campaign should start immediately after launch.
  2. Set a start time only if the campaign needs to go live later.
  3. For Onchain List, the end date is optional.
  4. For Claim-based (Merkle), the end date is required.
  5. Click Next only when the step validation passes.

If you set a start time, it must be at least 5 minutes from now. For Claim-based (Merkle), an end date is required and must leave a long enough claim window. For Onchain List, you can leave the dates empty and launch without a schedule window.

Common mistakes:

  • setting a start time too close to the current time
  • forgetting that Merkle requires an end date
  • entering a short claim window that fails validation
Image
Schedule step

Schedule step showing the start and end date controls used for the draft timing.

Step 3. Select Token

This step decides which token the campaign will distribute.

UI elements:

  • token source selector with My Tokens and Manual Mint
  • helper text: Choose from your token list or enter a mint address manually.
  • Token Program (Auto)
  • detected values such as program, decimals, and wallet balance
  • Use This Mint when using manual entry

What to do:

  1. If the token is already available in Bonkit, use My Tokens.
  2. If it is not in the list, switch to Manual Mint.
  3. If you are not signed in, connect the wallet first so the token list can load.
  4. Confirm the auto-detected token program before moving on.
  5. Continue only when the token validation card shows the mint can be used for an airdrop.

Important behavior from the UI:

  • The token program is detected automatically.
  • The screen shows Token or Token-2022 as a badge.
  • The current wallet balance for that token is displayed, which helps you catch wrong-mint mistakes early.

What counts as a valid token for an airdrop:

  • The mint must be a real initialized token mint on Solana.
  • Bonkit supports standard SPL Token mints and supported Token-2022 mints.
  • The token must have a supply greater than zero.
  • The detected token program must match the actual mint owner program.
  • Some Token-2022 extensions are not allowed for airdrops.
  • If the token has freeze authority, Bonkit may block it until that authority is revoked.

If validation fails, the card in the UI will tell you which check failed so you can switch tokens or fix the mint setup first.

PathUse it whenWhat Bonkit doesTypical blocker
My TokensThe token already appears in your Bonkit listLoads an existing token entry and its detected program infoYour wallet is not connected or signed in, so the list stays empty
Manual MintYou know the exact mint address but it is not in the list yetScans the mint onchain and validates whether it can be used for an airdropThe mint address is wrong or the token fails the validation checks

Common mistakes:

  • pasting a mint address that belongs to the wrong token
  • skipping sign-in and then wondering why My Tokens is empty
  • ignoring the validation card and continuing with an unsupported mint
Image
Select from My Tokens

Choose a token that already appears in your Bonkit token list.

Use this path when the token is already visible in Bonkit and you want the fastest setup flow.

Step 4. Review

This is the final confirmation step before the draft is created onchain.

Creating the draft does not upload recipients, fund the campaign, or launch it. It only creates the campaign shell you will configure next.

UI elements:

  • Campaign summary
  • Token details
  • What happens next
  • final action: Create Draft

What to do:

  1. Review the campaign name, type, and schedule.
  2. Check the UTC labels for start and end time.
  3. If local times were entered, compare them with the local labels shown in the review card.
  4. Verify the mint address and token program.
  5. Read the What happens next block so you know the draft is only the beginning of setup.
  6. Click Create Draft.
  7. Approve the wallet transaction.

Important behavior from the UI:

  • The result screen is titled Airdrop Draft Created.
  • The success card shows Airdrop Address, Type, Start, End, and Transaction.
  • The main follow-up action is Go to Airdrop Draft.

Common mistakes:

  • creating the draft with the wrong mint because the review step was rushed
  • assuming the campaign is already ready to launch after draft creation
  • ignoring the UTC schedule display and misreading the timing
Image
Review step

Review the campaign summary, token details, and schedule before creating the draft.

Image
Draft created

After the transaction succeeds, open the result screen and click Go to Airdrop Draft.

Success Looks Like

  • Airdrop draft created
  • Airdrop Draft Created
  • an Airdrop Address is shown
  • Go to Airdrop Draft takes you into management
  • the summary tells you to continue into recipients, funding, and schedule setup

Common Mistakes

  • Campaign name required
  • Invalid mint address
  • token validation fails
  • schedule validation blocks Next
  • thinking draft creation also uploads recipients or funds the vault

Use Manual Mint only when you already know the exact mint address you want to distribute.

Next Step

Continue to Add Recipients.

Last updated on