Skip to main content
Each V2 launch has two trading phases. The token first trades against its bonding curve. After bonding, it trades through its exact Uniswap V4 pool.

​
Route by the token, not the newest hook

An existing token stays attached to the hook that created it. Before building a trade, resolve the token with:
Use its hook_address, launch_id, denomination_kind, and lifecycle state. Do not send an old token to the current creation hook.

​
Quote assets

  • Native launches use the network’s native ETH.
  • xStocks launches use the selected non-rebasing wrapper.
  • Paying with another asset needs a real conversion route with enough liquidity. A USD mark is not a conversion route.

​
Curve phase

The curve prices the output from on-chain state. Preview just before the write, set a minimum output, then simulate the exact transaction. Current native hooks expose buy and sell; xStocks hooks expose wrapper-denominated functions such as buyWithQuote. Anti-snipe authorization may be required during a launch’s configured opening window. Outside it, the empty captcha struct can be used.

​
Bonding

The transaction that reaches the target closes the curve, creates and seeds the launch’s V4 pool, and emits LaunchFinalized. No creator action is needed. Do not build the pool key from a token/WETH assumption. Corrected/current hooks expose getLaunchPoolKey; legacy Ink requires the complete immutable pool fields from the token API. Current native Ink launches use the zero address for native ETH. xStocks launches use their wrapper. Follow Post-Bond Pool and fail closed when the key cannot be proved.

​
Product flow

1

Open the chain-specific page

Use https://inkypump.com/ink/trade/<token-address> on Ink or the matching network slug.
2

Choose Buy or Sell

Confirm the asset shown beside the amount. Native ETH and an xStocks wrapper are not interchangeable.
3

Review the quote

Check output, fee, minimum received, price impact, and route.
4

Sign and wait

Wait for the receipt. A pending transaction must not be submitted again as a replacement launch or trade.

​
Fee allocation

Current curve deployments use a 1 percent protocol fee and a 1 percent variable fee. The creator gets the configured share of the variable fee. The remainder depends on the deployment:
  • Current Ink sends it to holder fee sharing.
  • Older Ink uses buy-and-burn.
  • Other releases must be read from their versioned deployment data.
See Trading contract reference for function signatures and Networks and Deployments for current production discovery.