Skip to main content
The trade that reaches a launch’s target closes its curve and creates its V4 pool in the same transaction.

What the bond uses

The hook pairs the launch’s remaining liquidity token supply with its quote reserves:
  • Native launches use native ETH.
  • xStocks launches use the selected non-rebasing wrapper.
It initializes the pool at the calculated bond price and emits LaunchFinalized.

Resolve the pool; do not guess it

Corrected native hooks and current xStocks hooks expose:
PoolKey contains currency0, currency1, fee, tickSpacing, and hooks. The deprecated Ink hook marked hookAbi: "ink-legacy" does not expose this getter; resolve its complete indexed pool fields through GET /api/token instead. Current checked pools use fee 1000 and tick spacing 60, but the proved key is the source of truth.
Current native Ink launches use native ETH as the zero address. They are not token/WETH pools. xStocks launches use their wrapper. Historical launches keep their original hook.

What changes

Curve calls revert after finalization. The launch state remains readable.

Fee allocation

The 0.1 percent LP tier and the hook fee are separate. The checked current hook family charges 1 percent protocol plus 1 percent variable on the swap’s unspecified side after bonding. The fee asset and basis depend on swap direction and exact-input or exact-output mode. The creator can continue earning from the variable hook fee. The non-creator part is versioned: current Ink uses holder fee sharing while older Ink uses buy-and-burn. Use the launch’s deployment metadata and do not label all pools the same way.

How to prove bonding

  1. Read getLaunchState(launchId) and confirm finalization.
  2. Decode LaunchFinalized from the receipt.
  3. Read getLaunchPoolKey(launchId) on a corrected/current hook, or load the complete indexed key for ink-legacy.
  4. Confirm that the pool exists through the chain’s canonical V4 state reader.
In either path, validate the currencies, original hook, fee, tick spacing, and computed pool ID. See Post-Bond Pool. Fetch V4 contract addresses through Capabilities. For an existing token, match its original hook to the right tradeableDeployments entry. Do not pin addresses copied from an old page.