blastBonding-curve builder
Plan a launch and inspect its economics before preparing transactions. Start with the example, change one setting, and compare the opening price, final curve price, and pool price. Use How pricing works for the derivations, or Allocations and design choices for the tradeoffs.
Change a setting to recalculate. Exact token and quote amounts use contract atomic-unit rounding. Prices are approximate ratios; chart coordinates are illustrative.
Your curve at a glance
Baseline: buy to selected progress, then buy to the target; no sells. Each leg is one buy unless its input exceeds u64, in which case it splits into bounded buys. Other paths can differ by rounding. Pool price uses allocations before venue rounding.
Solid: curve spot price. Dashed: nominal pool opening price. Move the progress slider to inspect the curve; values are also available below.
Token reserve falls as real quote reserve rises. Virtual quote is included in pricing, never in spendable liquidity.
Graph data and reserve checkpoints
Where every asset goes
Unsold curve tokens are disposed of, not added to the pool. A sell burn waits for graduation. Fixed supply sends disposal to the zero address; burn-only reduces recorded supply.
One-time protocol payouts at assumed partner rate
Partner cuts shown per isolated example balance. Actual payout applies the current partner rate to the accumulated claim balance, so rounding can differ.
Example trade breakdown
The quote uses the selected reserve state. A sell assumes the wallet already holds the input tokens; this planner does not check wallet balances.
Opening-round example
This pot buys once from the opening reserve. Participant amounts assume first delivery; later deliveries use remaining balances and the final bidder takes the remainder. No bid withdrawal is available.
Future LP-fee routing example
These are example collected fees, not projected revenue. Blast is taken first from each asset; every remaining atom is assigned by largest remainder.
Auto-liquidity needs both assets at the current pool price. Rewards require funded rounds. Burn quote waits for an administrator-triggered buyback. Partner cuts use the assumed rate at payout.
Save your plan
Download the inputs and exact outputs as JSON. It is a local planning document, not a transaction or a deployable coin package.
Before launch: verify deployment, admitted coins and decimals, live policies, wallet destinations, creator recipient, venue tier and coin ordering. Network fees and exact venue deposits are outside this model.
Reading the results
Section titled “Reading the results”Spot price is the marginal reserve ratio. Average price divides the quote actually used or received by the tokens actually received or supplied, including both asset fees. Nominal pool price divides the pool’s allocated quote by its allocated tokens. These prices can differ substantially.
The baseline has two legs: buying from the opening state to the selected progress, then to the target. Each leg uses one buy unless its gross input exceeds u64; that leg then splits into bounded buys. The sample trade and opening-round pot are separate experiments. A sample sell also shows disposal if buys subsequently reach the target. Repeated trades can change results through rounding; wallets, balances and lifecycle gates still apply on-chain.
Amounts are calculated in integer atomic units. Displayed ratios use ≈ when truncated for readability. Graphs use approximate coordinates and provide a table of exact reserve amounts. A checkpoint that cannot execute as the stated single buy at atomic precision is left unplotted and identified in the table. The pool seed’s sqrt_price_x64 uses atomic coin ordering, not whole-coin display decimals. The value alone does not establish that a venue accepts the tick, price or pair.
What a plan cannot establish
Section titled “What a plan cannot establish”The builder does not validate a live Cetus tier, reserve a coin pair, calculate venue-specific position liquidity or residuals, check accepted partners or admitted coin types, verify actual recipient addresses, or estimate network fees. It treats entered Bluefin pool costs and the launch creation fee as SUI assumptions. It does not calculate yield, automatic reward eligibility, or a buyback schedule.
A launch also needs reviewed metadata, a creator recipient, published coin/ticket objects, current package versions and policy objects, correct pool inputs, and an operational migration path. See the creation checklist, fee policy, custody and authority, and migration reference.