Everything below was read
off the chain, not estimated.
Pons Liquid does not run its own AMM, its own chain or its own launchpad. It writes the rules layer that was missing between them — everything else stays canonical, and every address here is verifiable in one click.
- Block
- —
- v4 PoolManager
- —
- PONS
- —
- Pons launch fee
- —
Read in your browser from rpc.mainnet.chain.robinhood.com and robinhoodchain.blockscout.com. No server of ours sits in between, which is also why a figure occasionally shows as a dash — the explorer 500s about one call in six and the read is simply retried.
- Launchpad
- Pons
- AMM
- Uniswap v4
- Rules
- Pons Liquid hooks
- Chain
- Robinhood · 4663
One of these four is ours. The Uniswap v4 singleton is what makes hook-gated execution cheap enough to run on every swap; an Arbitrum Orbit L2 is what makes it cheap enough to be unremarkable.
- Uniswap v4 PoolManager
- 0x8366…0951
- Position Manager
- 0x58da…4fa7
- Quoter
- 0x8dc1…8f94
- State View
- 0xf333…673b
- Pons launch factory
- 0x7eD5…EC7e
- Pons fee escrow
- 0xd3AF…Ac9e
All six carry code at the RPC endpoint and are verified on Blockscout. Launching through the Pons factory needs no whitelist — canLaunch() returns true for every address.
- Custody
- Non-custodial
- Pool type
- v4 singleton
- Hook permissions
- Address-encoded
- Upgradeability
- None, post-init
- Pons graduation
- 4.2 ETH → v4
- Verification
- Blockscout
Contracts hold liquidity, never keys. Every transaction is signed in your own wallet, which also means nobody can reverse one for you.
The launchpad works. The hooks are not deployed.
The launchpad is real and it is the whole product: it encodes Pons' own launchToken call, reads the terms off the factory, simulates your exact calldata against the live contract, and only then lets your wallet sign it. No contract of ours sits in the path.
The hooks are the part that does not exist. The terminal computes the real v4 permission mask for a hook set and the address suffix it would have to be CREATE2-mined to, which is arithmetic, not a deployment. The six hook contracts are not written, so the deploy button is disabled on purpose rather than hidden.
$PLIQUID launched through this launchpad on 1 September 2026, the same way anyone else's token does: the same factory, the same bonding curve, fixed supply of one billion, no presale and no allocation held back. It got no special treatment because the page has none to give.
Check it against the explorer before you send anything anywhere. Any other address is not this token, wherever you read it.
Providing liquidity can lose money
The contracts are unaudited
New code running inside live swaps. No audit has been done, because the hooks do not exist yet. When they do, that line changes here first.
LPing is not yield
A concentrated range converts your position into the losing side of a trend. Hooks change the rules of the pool, not the direction of the market.
The rules cut both ways
THROTTLE caps you as well as the sniper, GUARD can reject your swap, and LOCK means you cannot exit early either. That is the point, and it applies to everyone.
Young pools are thin
A launch pool has little depth by definition. Slippage on early swaps can be severe no matter how well the hooks behave.
A listing is not an endorsement
Any token can launch on Pons, and a pool with rules in it does not vet the token inside it. The rules govern the liquidity, not the honesty of a team.
The figures here are schematic
Charts on this site illustrate mechanisms. Only the values marked live are read from the chain; nothing here is a projection of returns.