Launchpad share
Every new token needs a pool. Counting pool creations across both Uniswap streams shows which launchpads are winning Robinhood Chain — and whether anyone is eating into Pons' share.
New pools · 24h27,06017,802 Uniswap V3 · 9,258 V4
Pons launches · 24h15,776exact, from TokenLaunched events
Pons share43.8%of tracked token launches
How this is measured
- Every new pool on the chain emits an on-chain event — Uniswap V3
PoolCreatedor V4Initialize. We count all of them over the last 24 hours. Launchpads we've identified are counted exactly — Pons from its factory'sTokenLaunchedevents, the smaller factories from their inbound launch transactions (rows tagged “exact”). The remaining long tail is attributed by sampling ~35 pool-creation transactions per stream and extrapolating, so those rows carry sampling error. - Labels come from verified contract names, official docs, and launch metadata found in creation calldata (Varo's factory, for example, embeds its asset-CDN URLs). One high-volume V4 factory remains unidentified — an unverified proxy shown by its address until it can be attributed.
- Flap launches on a bonding curve, so no Uniswap pool exists until a token graduates — it would be invisible to a pool count. Its launches are instead counted exactly from
newTokenV6calls to its Portal contract. Other bonding-curve launchpads we haven't identified yet (several appear on community dashboards) are still missing from this table. - Not every new pool is a token launch — some are ordinary liquidity pools created directly on Uniswap. Those appear under the “Direct” rows.