Skip to main content
This is the supported first integration for launchpads such as Fomo: create a native-quoted token with the user’s connected wallet, prove the result from the transaction receipt, then poll the read API until the indexer publishes it.
Verified against production on September 21, 2026. Fetch Capabilities at runtime. Do not copy a hook address from an old guide.

The whole flow

  1. Your server fetches the active deployment for the selected chain.
  2. The user’s wallet simulates and signs createLaunch on that exact hook.
  3. Your app records the transaction hash before it waits for a receipt.
  4. Your app accepts the launch only after it decodes one valid LaunchCreated event from that hook.
  5. Your server polls GET /api/token until the token is indexed.
The caller becomes the creator and fee recipient. Let the creator’s wallet call the hook directly. If your backend or a wrapper contract submits the transaction, that address becomes the creator.

1. Resolve the current deployment

Call this from your server. InkyPump read APIs do not currently promise cross-origin browser access.
Use chain 57073 for Ink or 4663 for Robinhood. Always send chainId; never rely on a default.

2. Use the creation ABI

3. Simulate, sign, and prove the receipt

This browser example uses viem and an injected wallet.
Persist all five identity fields. A token address without its chain, hook, and launch ID is not enough to route future reads and trades safely.

4. Wait for discovery

The receipt is the launch truth. The API is an indexed view and may appear shortly after the receipt.
Run this on your server and return the result to your frontend. While it returns null, show Confirmed — indexing with the transaction link.

Native launch limits

Read contract limits from the selected deployment before exposing them in a long-lived client. For xStocks launches, the limits and units are per asset; use the xStocks guide.

Do not do these things

  • Do not hardcode the deprecated Ink hook 0x4cC8…6AC4 for new launches.
  • Do not retry createLaunch because receipt waiting timed out. Resume by hash.
  • Do not treat an API 404 just after confirmation as a failed launch.
  • Do not submit from a shared backend wallet unless that wallet should own the creator fees.
  • Do not guess a post-bond pool. Use getLaunchPoolKey on corrected/current hooks and complete indexed fields on ink-legacy, then validate the computed pool ID.
  • Do not expose a private key in a browser or partner API.

Deployments

Runtime discovery, active hooks, and legacy routing.

Production checklist

Failure cases and release gates before you ship.