Documentation Index
Fetch the complete documentation index at: https://blank.build/docs/llms.txt
Use this file to discover all available pages before exploring further.
Supply Actions
Supply Actions are creator-only actions you can take after launch from your
token management page. Every action runs from a verified creator wallet and
uses tokens that wallet already holds.
Burn
Permanently reduce token supply.- Burned tokens are removed from circulation forever; the action is irreversible.
- The amount you enter is shown as a percentage of the original total supply.
- Completed burns appear in the public Supply Actions history on the token page and as a
Bmarker on the chart.
Lock
Escrow tokens until a chosen unlock date.- Tokens are escrowed through Jupiter Lock on Solana and verifiable on-chain.
- The beneficiary is always your creator wallet. Locks cannot be assigned to a different wallet.
- The full amount unlocks in one shot on the unlock date. There is no linear release.
- Completed locks appear in the public Supply Actions history and as an
Lmarker on the chart.
Vest
Escrow tokens with a linear vesting schedule.- Tokens are escrowed through Jupiter Lock on Solana and verifiable on-chain.
- The beneficiary is always your creator wallet. Vesting cannot be assigned to a different wallet.
- You set a start date and an end date. An optional cliff date holds all tokens locked until that date, after which vested amounts become claimable.
- After the cliff (or from the start date if no cliff), tokens vest linearly toward the end date.
- Completed vesting schedules appear in the public Supply Actions history and as a
Vmarker on the chart.
Airdrop
Distribute tokens you hold to wallets that hold another Solana token.Airdrops use a campaign model. You snapshot a target token’s holders, review
the cost, fund the campaign, then Blank delivers the tokens directly to each
recipient. There is no claim step for recipients.
Eligibility
- Target may be any Solana SPL Token or Token-2022 mint.
- Holder balances are aggregated by wallet owner. Token accounts owned by the same wallet are summed.
- Wallets with a zero target balance are excluded.
- Known program, protocol, pool, and Blank custody accounts are excluded.
- You can set an optional minimum target-token balance to filter dust holders.
- Campaigns are capped at 10,000 eligible wallets in v1.
Allocation modes
Fixed
Every eligible wallet receives the same amount of your token. Total cost in
tokens is
eligible wallets × amount per wallet.Proportional
You set a total token budget. Each wallet receives a share weighted by its
balance of the target token. Wallets whose allocation rounds to zero are
dropped before funding.
Workflow
Pick the target
Enter the target token mint. Blank fetches token metadata and the program
(SPL Token or Token-2022) so you can confirm you’re targeting the right
project.
Snapshot holders
Blank scans current holders at a finalized slot and builds the eligible
recipient list. Holder snapshots are point-in-time and tied to the slot they
finalized at.
Review
Review the campaign before funding: recipient count, total token amount,
allocation mode, missing recipient token accounts, estimated SOL delivery
cost, and a safety buffer.
Fund
Sign one funding transaction from your verified creator wallet. The
transaction moves the token budget into a campaign vault and pays the
expected SOL delivery cost up front.
Deliver
Blank executes the campaign in batches: it transfers tokens directly to each
recipient’s associated token account, creating the account first if it does
not exist.
Cost
You fund two things up front:- Token budget — the total amount of your token to distribute.
- SOL delivery budget — covers associated token account rent for recipients who do not already have your token, transaction fees, priority fees, and a safety buffer.
Privacy and public display
- In-progress, funded, and failed campaigns stay private to you.
- Recipient lists are private to you and Blank operators.
- A completed campaign shows in your creator dashboard.
Safety rails
- The on-chain campaign program enforces the approved recipient list. The relayer that submits delivery transactions cannot redirect tokens or add recipients.
- Each recipient can be delivered to only once, enforced on-chain.
- If a batch fails repeatedly, the campaign moves to
Needs Attentionso you can retry from the dashboard or contact support. The campaign stays private in this state. - Remaining SOL and token dust stay in the campaign vault as a buffer for retries. They are not automatically refunded.