Liquidity for Pons and pools.trade tokens

Introduction

Two other launchpads already run on Robinhood Chain: Pons, a bonding-curve launcher whose tokens graduate into a Uniswap v4 pool, and pools.trade, Uniswap Labs' launchpad, whose instant-launch strategy opens a hookless v4 pool against native ETH right away. Neither is Hookr. hookr.fun/launchpads lists the tokens each has proven on chain and, for each one, whether a Hookr pool already exists for it or whether one can be opened.

How the page reads its rows

Every row comes from a bounded, cached read of a verified contract's own events, never from an indexer or a market feed.

Pons. The launch factory (PonsV2LaunchFactory) emits TokenLaunched once per token and PoolGraduated once its curve fills. PoolGraduated is what puts a token on this page: a token that has not graduated is still on its bonding curve, not in a plain pool. The pool's own v4 PoolId is not in either of those events; it comes from PoolRegistered, which the Pons hook (PonsV2MemeHook) emits on the same graduation. The page joins all three: a graduation missing its own launch record or its own pool registration is dropped from the list rather than shown with a guessed field.

pools.trade. The two deployed InstantLaunchStrategy contracts each emit their own TokenLaunched, naming the token, the exact PoolId, and the full v4 PoolKey in one event. No join is needed. The PoolId is recomputed from that key and checked against the emitted value before the row is trusted; a launch whose key does not hash to its own PoolId is left off the list. LiquidityLauncher's own TokenCreated carries no PoolId, so it is not the source here.

Both scans run in fixed-size block ranges from each contract's own deploy block, cached for a minute at a time. Pons and pools.trade fail closed independently: a Pons read failing never hides a working pools.trade list, and the other way around. Each list is capped to its newest 200 proven tokens.

What opening a pool for an existing asset does, and does not do

Choosing "Open a Hookr pool" for a launchpad token takes you into the existing-asset lane of the Hookr launch wizard, with that token pre-filled as the subject. Opening a market there is one transaction, and it is exactly this:

• It gives you no power over the token. The record says who opened the pool, nothing more.
• The pool starts with zero liquidity and no founding position. Nobody's tokens are moved by opening it.
• The base LP fee goes to liquidity providers in full.
• The protocol earns only inside the add-ons the pool opts into (surge, snipe tax, LP rewards, a pot, burn), frozen at creation. A base-fee-only pool pays the protocol nothing.

Opening a pool does not touch the token's supply, its owner, or any allowance. It does not close, pause, or migrate the launchpad's own pool. It only opens one more place the token can trade, under whatever rules you choose on the terms step.

The Hookr pool is independent of the launchpad pool

A token's Pons or pools.trade pool keeps running exactly as it did before, with its own liquidity, its own price, and its own fee split. A Hookr pool for the same token, whether one already existed or one is opened from this page, is a separate Uniswap v4 pool with its own PoolKey and its own liquidity. The two are not linked, merged, or arbitraged automatically; they are simply two different pools that happen to share a token on one side. When a Hookr pool already exists, the page links straight to it; when one does not, opening one does nothing to the pool that already exists elsewhere.