Allocations and design choices
Use this guide to decide what a launch should do, then enter the plan in the builder. The pricing walkthrough explains the equations. All examples describe source at c96cd0d, not verified live policy or available app features.
A launch has three separate balance systems
Section titled “A launch has three separate balance systems”- Curve reserves: the tokens available for curve trading and real quote collected after fees and sells. Virtual quote affects pricing but is not a balance.
- Launch allocations and fee ledgers: reserved pool tokens, recipient allocations and accrued creator/Blast fees. A token fee is not a purchase delivered to the buyer. Accrued quote fees do not count toward the real quote target.
- Pool and LP vault: at graduation, allocated tokens and quote seed the DEX. The vault handles LP custody and future collected fees. It does not continue the curve’s trade-fee schedule.
Keep these separate in budgets and dashboards. A target is not volume, a fee allocation is not liquidity, and an LP-fee split is not an annual return.
What the creator chooses
Section titled “What the creator chooses”| Choice | Rules | Economic consequence |
|---|---|---|
| Generated coin | Exactly 1 billion whole tokens; admitted decimals initially 6 or 9 | Supply is fixed at creation, not a builder slider |
| Burn-only or fixed supply | Disposal burns recorded supply, or transfers tokens to the zero address | Changes recorded supply after disposal; neither mode permits additional minting after finalization |
| Sell burn | 0–50%, fixed in the ticket; applied after token fee | Less of a seller’s input reaches the reserve; disposal waits until graduation |
| Quote coin | Admitted, different from the launched coin | Determines payment asset, decimals and denomination of all prices |
| Virtual reserve | Positive quote amount | Sets opening price relative to curve inventory; supplies no funds |
| Real quote target | Positive; must leave at least one atom allocated to LP | Determines when the curve closes; no expiry if it is never reached |
| Supply allocation | Curve and LP positive; all shares including Blast total 100% | Separates trading inventory, pool funding and project distributions |
| Quote allocation | All shares including Blast total 100% | Splits the final real quote reserve, not gross purchases |
| Project recipients | Up to 16 non-zero addresses; separate token and quote shares | Pays at migration; repeated addresses are permitted in this allocation list |
| Venue and tier | Cetus registered tier, or Bluefin spacing 1–400 and raw fee rate 1–20,000 | Fixed venue route and pool-creation requirements; raw Bluefin units are not BPS |
| Opening mode | No round, or pooled 60–300 seconds | Changes access timing and settlement, not the curve equation |
| LP-fee routing | Creator, auto-LP, rewards, burn and up to 16 extra recipients total 100% | Distributes what remains after Blast’s live LP-fee share |
| Extra LP recipients | Distinct non-zero addresses | Paid directly at each collection; distinctness differs from project allocations |
| Partner | Accepted partner recorded at creation, or none | Partner receives part of Blast’s fees; identity cannot later be replaced |
Name, description, icon, creator recipient and symbol also need review. Symbol is capped at 32 bytes on finalization. Name, description and icon can later change through the metadata capability; symbol and decimals cannot. Builder recipient labels are planning names, not validated destinations.
What Blast controls
Section titled “What Blast controls”| Setting | When it is read | Can it change for an existing launch? |
|---|---|---|
| Launch creation fee in SUI | Finalization; must pay exactly | The launch has already paid it |
| Admitted coins and decimals | Creation | Does not rewrite a finalized coin |
| Curve quote and token fee rates | Creation; each at most 10% | Snapshotted rates stay fixed |
| Protocol supply and quote allocations | Creation | Snapshotted shares stay fixed |
| Blast’s share of curve fees | Every trade; 0–100% | Yes, without a delay in this source |
| Blast’s share of collected LP fees | Every collection; 0–100%, separately per asset | Yes, without a delay; per-coin pair overrides defaults |
| Treasury destination | Payout | Yes |
| Partner share and managing capability | Payout using current accepted policy | Changes wait seven days; share at most 80% of Blast’s part |
| Capabilities and package upgrades | Administrative operations | Blast can reassign fee/metadata capabilities and upgrade compatible packages |
Source initialization at zero is not evidence of a live zero fee. Read the actual deployment’s policy objects. The presale’s schedule and capabilities do not apply to this product.
Design the supply and quote allocations together
Section titled “Design the supply and quote allocations together”For an illustrative 1-billion-token launch:
| Destination | Original token supply | Final real quote reserve |
|---|---|---|
| Curve inventory | 70% = 700,000,000 tokens | — |
| Pool | 20% = 200,000,000 tokens | 90% |
| Blast | 1% = 10,000,000 tokens | 1% |
| Project treasury | 9% = 90,000,000 tokens | 9% |
| Total | 100% | 100% |
The 70% is inventory offered to the curve, not a promise that all 700 million tokens are sold. Whatever remains at graduation is disposed of. The 20% LP allocation is a separate reserve and is not adjusted upward to absorb unsold inventory.
At a 3,000-quote target, the pool receives 2,700 quote coins, Blast accrues 30, and the project receives 270. Curve trading fees were already separated. Adding virtual quote to these amounts would invent money the contract does not hold.
With more recipients, split the project allocation explicitly. A second 4% token allocation must come out of another share; it cannot be added on top of a 100% plan. The builder validates each asset independently and never silently adjusts a share.
Exact allocation rounding
Section titled “Exact allocation rounding”Every amount is allocated in atoms. Blast’s protocol allocation rounds up. Other parts start at their floor, then leftover atoms go to the largest fractional remainders; ties favor the earlier entry. Supply order is curve, LP, Blast, recipients; quote order is LP, Blast, recipients.
For 7 quote atoms, with pool 50%, Blast 10%, project 40%:
Raw amounts: pool 3.5 Blast 0.7 project 2.8Initial amounts: pool 3 Blast 1 project 2One atom remains; project has the larger eligible remainder.Final amounts: pool 3 Blast 1 project 3 → total 7The LP-fee remainder uses the same largest-remainder method after Blast’s cut, with no specially rounded-up recipient. Earlier tie order is creator, auto-LP, rewards, burn, then extra recipients. This is why multiplying a displayed percentage and rounding every line independently can produce an incorrect total.
Align the final curve price and pool price deliberately
Section titled “Align the final curve price and pool price deliberately”For a continuous buy-only path:
final_curve_tokens ≈ opening_curve_tokens × V / (V + T)final_curve_price ≈ (V + T) / final_curve_tokensnominal_pool_price = pool_quote / pool_tokensmatching_pool_tokens ≈ pool_quote / final_curve_priceChanging LP token supply changes the pool price even if the curve is unchanged. Changing LP quote allocation changes both pool depth and pool price. Changing the curve allocation changes its opening and final prices. Raising the target changes graduation timing, curve price and the quote available for allocation.
A matching ratio is a design constraint, not an automatic contract guarantee. Venue tick bounds, coin order, integer seed price and position rounding matter; actual deposits can leave residual assets. Pool price may move immediately after creation. The builder graphs the curve against the nominal LP ratio so a discontinuity is visible before launch.
For concentrated liquidity, adding the displayed quote value of both sides is only a nominal balance valuation. It is not an exact measure of executable depth, position liquidity, or the quote that a large sell could recover.
Choose the opening mode
Section titled “Choose the opening mode”| No opening round | Pooled opening round | |
|---|---|---|
| Before public sharing | Creator can buy | Creator can bid into the same pot |
| Public start | Ordinary curve trading | Bids join a pot for 60–300 seconds |
| Withdrawal | A subsequent public live sell is a new trade | Bids cannot be withdrawn |
| Price treatment | Each buy uses then-current reserves | Pot makes one buy; participants share its output |
| Pot exceeds target | Not applicable | Capped purchase; unused quote distributed with tokens |
| Delivery | Direct buy outputs | Permissionless delivery to the named bidder, even after migration |
For a pot of 1,000 quote coins with a 100-quote bid, that bidder has 10% of the pooled input. It receives roughly 10% of net tokens and any unused quote. Atomic remainders depend on delivery order, with the final bidder receiving what remains. A nonterminal pot that would deliver zero tokens is retained for refund; terminal zero-output behavior follows the target-reaching buy rule.
An opening round does not guarantee a fair valuation, remove administration, or create a target-miss refund path.
Route future LP fees by purpose
Section titled “Route future LP fees by purpose”Suppose a pool position has earned 10 quote coins, Blast’s LP cut is an assumed 10%, and the post-Blast split is creator 40%, auto-LP 30%, holder rewards 20%, burn 10%:
| Destination | Quote amount | What happens |
|---|---|---|
| Blast | 1 | Treasury payout, or held for partner settlement |
| Creator | 3.6 | Accumulates in vault; capability holder claims |
| Auto-LP | 2.7 | Waits for sufficient token-side funds, then adds liquidity at current price |
| Holder rewards | 1.8 | Waits for funded administrator-published reward rounds |
| Burn | 0.9 | Quote accumulates until an authorized buyback |
The same procedure runs separately on token fees. Burn-side tokens are disposed of immediately at collection, unlike burn-side quote. If an accepted partner has an assumed 20% share of Blast’s part, its quote cut is 0.2 and Blast keeps 0.8; the creator and other destinations are unchanged.
The builder lets you enter sample earned token and quote fees. It shows routing, not expected earnings. Trading volume, DEX fees, position performance, collection timing, reinvestment execution and off-chain reward calculations are separate assumptions.
The creator fee-capability holder may replace the split after migration. The adapter first collects outstanding fees under the previous split. Existing accumulated balances keep their assigned purpose; a new split does not relabel old rewards or burn funds.
Budget graduation and operational work
Section titled “Budget graduation and operational work”Graduation is a separate transaction from reaching the target, although it can be composed with the final buy. Anyone can trigger the original adapter with the required inputs. Failure rolls back migration atomically.
- The target, virtual reserve, launch allocations, total curve trade-fee rates, sell burn, opening duration, partner and venue tier are fixed for the launch under the current code.
- Cetus requires the correct canonical pair, a registered tier and its reserved creation cap. The adapter does not adopt an existing pool. Pre-creation of that pool or removal of the tier can leave the launch waiting for an upgrade-based recovery path.
- Bluefin requires its exact current SUI pool-creation fee and currencies/configuration. The transaction sender becomes its pool manager for reward-emission administration.
- SUI creation and network costs are separate from the quote target, even if the quote coin is not SUI. The builder does not estimate gas.
- Cetus burns the migration position through LP Burn and stores the proof; auto-LP uses a separate position. Bluefin holds its position in the vault. No current entrypoint withdraws these positions, but the migrators package remains upgradeable.
- Venue residuals accrue to a separate vault protocol-residual balance, claimable only by
TreasuryAdmin; they are not a project allocation or an automatic refund.
Holder-reward eligibility comes from an off-chain calculation and a funded Merkle root, not from a percentage slider. Proofs show membership in the published allocation; they do not establish fairness of its accounting. These rounds have no expiry or cancel/sweep path in the reviewed code.
Review a plan before publishing
Section titled “Review a plan before publishing”Use the launch checklist, review safety and authority, and preserve the exact source/deployment and policy assumptions alongside the downloaded plan. Confirm real wallet addresses, metadata, capability recipients, supported coins, atomic amounts, the migration operator and its funding.
Do not use a curve plan as a presale plan. Curves have no sale window, cancellation, or target-miss refund. If the target is never reached, migration allocations remain unavailable; holders can only use the curve’s supported live trading path and its available real reserves.