Pons Launchpad API on Robinhood Chain: PonsLaunchFactory Launches, PonsLauncherToken Trades and Graduations
Pons (Pons Family) is a token launchpad on Robinhood Chain. Its V2 launch factory gives every token a real bonding curve that graduates into a Uniswap v4 pool behind a Pons-owned hook with permanently locked liquidity, and it lets a creator quote a launch in native ETH, USDG, cbBTC, or a tokenized stock or ETF such as TSLA, NVDA or SPY. This guide shows how to track new Pons launches, bonding-curve trades, snipe tax, graduations, the liquidity lock, and post-graduation prices and liquidity with Bitquery GraphQL APIs, using the EVM(network: robinhood) and Trading cubes. Part of the Robinhood Chain API docs.
Pons publishes protocol and integration docs at docs.ponsfamily.com and states that there is no Pons API: integrators are told to index the factory and the curves themselves. That is what this page does through Bitquery, so nothing here depends on Pons infrastructure. Every query runs as written in the Bitquery IDE. Live data and the last month of Trading cube history are on every paid plan; history back to the first V2 launch sits on the archive dataset, which paid plans add through the Robinhood archive add-on and the trial does not include (see Historical Pons data).
Video Tutorial | Pons Launchpad API on Robinhood Chain - Track Launches, Trades & Graduations
Video Tutorial | Build a Robinhood Chain Trading Bot: Pons Launches, Curve Trades & Graduations
Video Tutorial | How Many Pons Coins Survive a Week? 1,923 Robinhood Chain Launches, 7 Days Later
Contracts: PonsLaunchFactory and PonsLauncherToken
Pons has two generations of contracts on Robinhood Chain. PonsLaunchFactory is the Pons V1 factory, and PonsLauncherToken is the ERC-20 contract it deploys for every V1 launch, so each V1 token is its own PonsLauncherToken contract rather than a proxy of one shared implementation. The verified source of the Pons token itself (PONS, 0x39dbed3a2bd333467115de45665cc57f813c4571) is also PonsLauncherToken. New launches go through the V2 versions, PonsV2LaunchFactory and PonsV2LauncherToken, which add the bonding curve and graduation. All four names are the verified contract names on the Robinhood Chain Blockscout explorer.
| Contract | Address | What it emits | Queried in |
|---|---|---|---|
PonsLaunchFactory (V1 factory) | 0xa5aab3f0c6eeadf30ef1d3eb997108e976351feb | TokenDeployed and TokenLaunched (V1 signatures, one Uniswap V3 pool per launch), plus admin events such as LaunchConfigAdded, DexConfigAdded and LaunchFeeUpdated | Pons V1 topic0 values |
PonsLauncherToken (V1 token) | one contract per V1 launch, deployed by PonsLaunchFactory, for example BANKERS 0x97133372cc4391a4f6889b4d52387649b76bc7ec | Standard ERC-20 Transfer and Approval; its trades come from its Uniswap V3 pool | Trading cube, Holders and supply |
PonsV2LaunchFactory (V2 factory) | 0x7ed598bcef8bd9edd8c97a195c6d13f40801ec7e | TokenLaunched, LaunchSwept, PoolGraduated, GraduationTokensPermanentlyLocked and the creator-fee events | Factory events, Newly launched tokens, Graduation, Token lifecycle, Launchpad stats |
PonsV2LauncherToken (V2 token) | one contract per V2 launch, deployed by PonsV2LaunchFactory, for example DECK 0x2861f208e71ced7beab010457bf10f0c1ccc0e2d | Standard ERC-20 Transfer and Approval; its curve trades are the CurveBuy / CurveSell events of its own bonding curve | Bonding-curve trades, Trading cube, Holders and supply |
The router, meme hook, locker and the other V2 contracts are listed in the next section.
Pons contract addresses at a glance
Every Pons V2 contract, in one place. Full event lists, the quote-asset table and the caveats are in Pons contract addresses further down.
| Contract | Address |
|---|---|
Pons V2 launch factory (PonsV2LaunchFactory) | 0x7ed598bcef8bd9edd8c97a195c6d13f40801ec7e |
Pons V2 launch locker (PonsV2LaunchLocker) | 0x267444d099b10fb5ed7c3cc7b7c767adca574952 |
Pons V2 meme hook (PonsV2MemeHook) | 0xe5e702641ea86f4ae6cc3cdaed2b886f976be044 |
Pons V2 launch router (PonsV2LaunchAndBuy) | 0xe33e9e479df8802cb0866d5d05258bec4cf62948 |
| Pons V2 graduation executor | 0xc7819b64a1daecd7ec19856d026cb14efbd89046 |
| Pons V2 launch deployer | 0x3711cea4feade896c913c68f01eda97cb06d1a42 |
| Pons V2 fee escrow | 0xd3afeb2a57f70ef218aa82451c51b2fb0416ac9e |
| Pons V2 buyback vault | 0x42df2a798f82289e177311362e8f5ccc45c1219c |
| Pons V2 graduation guard | 0xf5695117b99b6f6401e67d4195bd653628176c6c |
| Pons V1 factory (superseded, no longer launching) | 0xa5aab3f0c6eeadf30ef1d3eb997108e976351feb |
| Uniswap v4 PoolManager (chain-wide, not Pons-only) | 0x8366a39cc670b4001a1121b8f6a443a643e40951 |
Each launched token also gets its own bonding-curve contract, so there is no single curve address — curve trades are matched by event signature instead. The address that receives the launch mint is that token's curve; see Newly launched tokens.
To query or stream data outside the Bitquery IDE, you need an API access token.
Follow the steps here: How to generate Bitquery API token ➤
- Robinhood New Pools & Trending Tokens API — new pools, trending tokens, pair lookup and token search
- Robinhood Chain API overview — every Robinhood Chain API, launchpad guide and stream in one place
- Robinhood Chain DEX Trades API
- Robinhood Meme Coin Launches API
- Pools.trade API on Robinhood
- Flap.sh API on Robinhood
- Robinhood Calls API
- Robinhood Token Holders API
- Robinhood Liquidity & Slippage API
- WebSocket subscriptions
How a Pons V2 launch works
Every launch mints a fixed 1,000,000,000 supply straight into its own bonding curve contract. Traders buy and sell against that curve — not against any DEX — until the curve has taken in its graduation threshold of the quote asset. At that point the curve is swept, and the proceeds seed a Uniswap v4 pool whose liquidity position is permanently locked.
| Property | Value |
|---|---|
| Network | Robinhood Chain (network: robinhood, chain ID 4663) |
| Launch supply | 1000000000 (1 billion, decimal-normalized), 18 decimals |
| Pre-graduation venue | Pons bonding curve, one contract per token |
| Post-graduation venue | Uniswap v4 (Protocol: uniswap_v4) |
| Graduation threshold | 4.2 ETH for native-quoted launches; a per-asset amount for ERC-20 quotes — read it from graduationThreshold in TokenLaunched, set per asset by PairTokenEconomicsUpdated |
| Curve trade fee | 100 bps (1%) of the quote side, set by the launch config rather than a protocol constant |
| Creator tax | set per launch, capped by the factory (maxCreatorTaxBps) |
| Launch fee | 0.0005 ETH |
Graduated pool fee | 0 — all fees are taken by the hook, not by the pool |
Graduated pool tickSpacing | 200 |
Graduated pool hooks | 0xe5e702641ea86f4ae6cc3cdaed2b886f976be044 (PonsV2MemeHook) |
The supply split
The curve's shape fixes exactly how much supply reaches the pool, and it is the same for every launch regardless of quote asset:
| Slice | Share of supply | Where it ends up |
|---|---|---|
| Sold on the curve | 5/7 (≈714,285,714) | Buyers |
| Swept at graduation | 2/7 (≈285,714,286) | Split below |
| ↳ seeds the v4 pool | 10/49 (≈204,081,633) | Locked full-range position |
| ↳ permanently locked | 4/49 (≈81,632,653) | PonsV2LaunchLocker |
How Pons differs from pools.trade
Pons and pools.trade are structurally opposite, and queries do not transfer between them:
| Pons V2 | pools.trade | |
|---|---|---|
| Pre-graduation venue | Real bonding-curve contract | Uniswap v4 pool from block one |
| Graduation event | Yes — LaunchSwept + PoolGraduated | None |
Pool hooks | PonsV2MemeHook | 0x000…000 |
Pool fee / tickSpacing | 0 / 200 | 2500 / 25 or 60 |
| Quote assets | ETH, USDG, cbBTC, tokenized stocks and ETFs | Mostly native ETH |
| Curve trades in trade cubes | Yes, as pons_v2 (Trading, rolling ~30-day window; EVM DEXTrades from 2026-08-14) | N/A — all trades are pool trades |
PonsLaunchFactory at 0xa5aab3f0c6eeadf30ef1d3eb997108e976351feb is the V1 launchpad. It has no bonding curve — each token gets a Uniswap V3 pool at launch — and its events carry different signatures and different topic0 values from V2:
db51ea9ad51ab453a65a4cb7e60c3cb378c9501bb002609f8f97778fb6c4235a TokenLaunched(address,address,address,address,address,uint256,uint256,uint256,uint256,uint256)
1461370115e1c2be79cb529f8cfcbd11316e789d9c6099fc83417b0b4c48c62a TokenDeployed(address,address,address,address,uint256,uint256)
Every query on this page targets V2 only. A "Pons launches" feed built from V2 alone will not include V1 launches — add the V1 factory address and its topic0s if you need both.
V1 has stopped producing launches — its factory now emits only ownership-admin events. Treat it as history — query EVM(network: robinhood, dataset: archive) for logs from 0xa5aab3f0c6eeadf30ef1d3eb997108e976351feb when you need V1 launches, and re-check the realtime dataset before assuming it is dead for good. V1 pools are created by Robinhood Chain's chain-wide Uniswap V3 pool factory, which serves every V3 protocol on the network — a PoolCreated event from it is not on its own a Pons signal.
Datasets
dataset gives you realtime — a rolling window, not historyEVM(network: robinhood) with no dataset argument queries the realtime dataset, which holds only a rolling window of recent blocks. This is the single most common reason a Pons query "works" but returns nothing older than a few days, and nothing in the response says which dataset served it.
If you want history, say so explicitly:
| Dataset | What it covers | When to use it |
|---|---|---|
(omitted) → realtime | Rolling recent window | Live streams, dashboards of the last few hours |
dataset: archive | Full history from the chain's indexing start | Backfills, per-day counts, anything dated |
dataset: combined | Archive merged with the realtime tail | A continuous view from launch day to now; slower |
EVM(network: robinhood, dataset: archive) { ... }
EVM(network: robinhood, dataset: combined) { ... }
See Dataset options, archive, realtime, combined, and data coverage and retention.
Every query on this page runs on archive and combined — Pons V2 history reaches back to the first V2 launch — with one exception, verified:
| Construct | realtime | archive | combined |
|---|---|---|---|
Topics: {includes: […]} filter (incl. topic0) | ✅ | ✅ | ✅ |
Call.Input / Call.Output, incl. Input: {startsWith: […]} | ✅ | ✅ | ✅ |
LogHeader.Address / LogHeader.Data, Log.Signature.Name | ✅ | ✅ | ✅ |
Transfers, Holders, DEXTrades | ✅ | ✅ | ✅ |
Log.Signature.SignatureHash / Call.Signature.SignatureHash, filtered or selected |