Skip to main content

​
ApeStore Launchpad Integration on Robinhood Chain

Learn how to index and integrate the ApeStore launchpad on Robinhood Chain, including contract discovery, ABI events, token pricing, liquidity, bonding state, graduation, and metadata. Integrate ApeStore launches and their concentrated-liquidity markets on Robinhood Chain. This guide describes the public contract surface for an independent integration.

​
Network and contracts

Unless another chain is listed, these addresses are for Robinhood Chain (chainId 4663). Verify proxy implementations and mutable configuration at the indexed block.

​
Market discovery and ABI

ApeStore creates a Uniswap V3-compatible WETH pair. Discover a launch from the launcher transaction and the PoolCreated(token0, token1, fee, tickSpacing, pool) event emitted by the concentrated-liquidity factory. Confirm the launcher transaction contains the token and that the resulting pool reports the expected factory, token0, and token1.

​
Relevant ABI

​
Launchpad architecture and AMM model

ApeStore is a token launchpad built on top of Uniswap v3-style concentrated-liquidity markets. The underlying AMM provides trading and liquidity mechanics; ApeStore adds launch attribution, token discovery, metadata, and market-cap-based completion semantics. Classification: Uniswap v3-like. The market exposes the standard V3 pool surface: token0, token1, slot0, concentrated liquidity, signed swap deltas, ticks, and Mint/Burn/Collect events. The difference is launch attribution and completion: the ApeStore launcher identifies eligible pools, while progress is market-cap based and does not trigger a pool migration. Shared with V3: square-root pricing, tick-based liquidity, position ranges, and pool event semantics. Protocol-specific: launcher verification, metadata discovery, and the $69,000 completion rule.

​
Price calculation

Use the V3 square-root price: raw(token1/token0) = sqrtPriceX96² / 2¹⁹². Apply 10^(decimals0-decimals1). Invert only when requesting token0/token1; never reorder the pool.

​
Liquidity tracking

Track Mint, Burn, Collect, Swap, and Flash. For token balances, use pool balances at a fixed block or reconstruct signed event deltas. V3 active liquidity is not itself token TVL; convert liquidity across tick ranges or value actual balances.

​
Launchpad state, bonding, and migration

The market remains in the same concentrated-liquidity pool. Progress is market-cap based, with a launch target of $69,000: progress = clamp(marketCapUSD / 69,000 × 100). Mark completion only when the target is reached according to the same quote-price snapshot used for market cap.

​
Metadata

Read ERC-20 name(), symbol(), decimals(), and totalSupply(). The launch transaction is the authoritative association between the launcher and pool; do not classify every pool from the same V3 factory as ApeStore.

​
Indexing checklist

  1. Index creation and bind the launched token to its canonical market.
  2. Preserve on-chain token/currency order exactly.
  3. Replay logs in block, transaction, and log-index order.
  4. Keep raw integers until decimals are applied.
  5. Treat graduation as protocol state, not a generic price shortcut.

​
Historical indexing notes

Use block-scoped reads when initializing historical state. Do not mix latest reads into an old-block replay. Store launched-token identity separately from native pool ordering. For broader methodology, see Bonding Curves Mathematics and Pricing Engine Deep Dive.