Skip to main content

​
Klik Launchpad Integration on Robinhood Chain

Learn how to index and integrate the Klik launchpad on Robinhood Chain, including contract discovery, ABI events, token pricing, liquidity, bonding state, graduation, and metadata.
Protocol reference: Klik developer documentation

​
Network and contracts

​
Market discovery and ABI

Discover PoolIds from PoolManager Initialize; verify the chain hook and factory registration. Preserve PoolKey currency order.

​
Relevant ABI

Index PoolManager Initialize, Swap, and ModifyLiquidity.

​
Launchpad architecture and AMM model

Klik is a token launchpad built on top of Uniswap v4. PoolManager supplies the AMM, while the Klik hook and factory add atomic token deployment, dynamic launch fees, creator revenue, metadata registration, and inventory-based launch progress. Classification: Uniswap v4-like with a Klik hook. Markets are PoolManager PoolIds and use standard PoolKeys, square-root pricing, ticks, swaps, and liquidity modification. The hook adds dynamic fees and creator/platform fee routing; Klik also treats consumption of the seeded token inventory as launch progress without migrating pools. Shared with V4: singleton PoolManager, currency ordering, hook address in PoolKey, sqrtPriceX96, and ModifyLiquidity. Protocol-specific: chain-specific factory/hook verification, dynamic fee schedule, 1-billion-token seeded inventory, creator fees, and metadata registration.

​
Price calculation

Use currency1/currency0 = sqrtPriceX96² / 2¹⁹², adjusted for decimals. Dynamic hook fees affect execution amounts, not the square-root spot-price definition.

​
Liquidity tracking

Track PoolManager liquidity deltas by PoolId and convert position liquidity to currency amounts using current sqrt price and ticks. Do not treat liquidity L as reserve balances.

​
Launchpad state, bonding, and migration

Klik seeds 1,000,000,000 tokens and does not migrate. progress = clamp((initialSupply - launchedTokenReserve) / initialSupply × 100). Sells return tokens and reduce progress.

​
Metadata

Read tokenInfoByAddress(token).metadata, normalize HTTPS/IPFS, and parse name, symbol, description, image, website, Twitter and Telegram. For broader methodology, see Bonding Curves Mathematics and Pricing Engine Deep Dive.