Curve fees, LP fees, and rewards

Rates below describe contract limits and formulas, not current live quotes. Read each launch and the relevant policy objects. The presale fee schedule does not apply to the bonding curve.

Before the pool launches

Charge	How it works
Creation fee	Exact amount of SUI set by Blast, paid once when the launch finalizes, regardless of quote coin.
Quote trade fee	Charged on quote input when buying and gross quote output when selling. Snapshotted per launch; at most 10%.
Token trade fee	Charged on gross token output when buying and token input when selling. Snapshotted per launch; at most 10%.
Sell burn	Up to 50% of sold tokens after the token fee. This part does not reach the curve; it waits for disposal at migration.
Migration allocation	Blast’s snapshotted share of the original supply and final real quote reserve, accounted at pool launch.
Network and venue costs	Separate Sui network fees. Bluefin migration also requires its current SUI pool-creation fee.

Trade fees round up in atomic units. Each fee splits between Blast and the creator. Blast’s share rounds up and is read from a live policy at every trade; the creator receives the rest. Blast can set its share from 0% to 100% without a delay. Changing this split changes who earns fees, while each launch’s total trade-fee rates remain fixed under the current code.

Creator fees accumulate in the launch until claimed with the live curve-fee capability. Blast’s trade fees, creation fee, and migration allocation wait in its fee ledger until a permissionless payout. Creator fee claims remain available after migration.

After the pool launches

The DEX charges its own trading fee. Anyone can collect fees earned by the vault’s liquidity position. At collection:

1. Blast’s live LP-fee share is taken separately from each asset, rounding up. A per-coin policy overrides the defaults. Blast can set each share from 0% to 100% without a delay in the current code.
2. The remainder splits between creator, auto-liquidity, holder rewards, burn, and named recipients. Integer remainders are apportioned so every unit is assigned.

Part	Where it goes
Creator	Accumulates in the vault; claimed with the same live curve-fee capability.
Auto-liquidity	Reinvested at the pool’s current price when both assets are available; unused balances wait.
Holder rewards	Both assets wait in the vault until Blast publishes funded reward rounds.
Burn	Token part is disposed of immediately. Quote part waits for an administrator-triggered buyback, then the purchased tokens are disposed of.
Named recipients	Paid directly during collection.

The capability holder can change this split after existing pool fees are collected under the old one. Accumulated balances retain their assigned purpose. Collection, buybacks, and reward publication require transactions; an allocation does not promise a schedule or yield.

The migrators policy initializes LP shares at zero in source. That initialization is not a live fee quote and is separate from presale LP policy. Resolve the actual deployment’s policy before showing a percentage.

Partners

A partner named at creation receives a cut of Blast’s fees, including its creation fee, curve fees, migration allocation, and LP fees. It does not add a fee to the trader or reduce the creator’s part separately. The partner’s share can be at most 80% of Blast’s part, is read when paid, and rounds down. Blast’s changes to that share or the partner’s managing capability wait seven days.

Partnered LP fees wait in the vault until anyone triggers their separate payout. Removing a partner from admission for new launches also waits seven days; it does not remove the partner from existing launches.

Claiming holder rewards

Blast computes allocations off-chain and publishes a funded Merkle root. Anyone can submit a valid claim for an unpaid allocation; coins go only to its named beneficiary. Launchpad reward rounds have no expiry in the current code.

Proofs establish that an allocation matches the published root. They do not prove that the off-chain holder calculation was fair. Blast’s rewards administrator chooses the allocation; the current contract cannot cancel a published round or recover a mistaken root’s budget. See Safety and authority and migration integration.