Skip to main content
InkyPump V2 uses a hook per deployment. The hook stores launch state, creates tokens, runs the bonding curve, and owns the post-bond V4 pool logic.
There is no single permanent V2 hook address. Use /api/capabilities for new native launches and the token’s own hook_address for existing launches.

​
Public launch deployments

Checked against production on September 21, 2026: The API also returns a machine-readable version value. Treat it as an opaque deployment ID for routing and diagnostics. Do not show that internal ID as a product name. Read Networks and Deployments for runtime hashes and chain infrastructure.

​
Architecture

​
Entry points

After bonding, use the exact V4 pool key resolved for the launch’s ABI family. Do not derive a WETH pool from assumptions. See Post-Bond Pool.

​
Caller identity

The direct caller becomes the creator and fee recipient. createLaunchFor can direct launch-time tokens and refunds to a prebuy recipient, but the caller still remains creator. A partner should normally let the user’s wallet call the hook directly.

​
Fees differ by deployment

The protocol and variable curve fee are currently 100 basis points each on the checked native deployments. The variable share’s destination differs:
  • Current Ink routes the former buyback share to holder fee distribution.
  • Older Ink deployments use the buy-and-burn design.
  • Creator withdrawal is withdrawFees(uint256) on current Ink and Robinhood, but withdrawFees() on the older Ink hook.
Use feeWithdrawal and deployment version from Capabilities. Do not guess a selector from the chain alone.

​
Constants

Current native deployment values:
xStocks hooks store their own quote-denominated limits. Read them from /api/xstocks/quote-assets.

ABI and events

Exact tuples and event signatures.

Token creation

Native and wrapper-quoted creation calls.

Trading

Curve, pool, approval, and captcha boundaries.

Launchpad quickstart

End-to-end browser wallet example.