Watch the factory
The engine asks Robinhood Chain for new logs from the two Pons factory contracts. The creation event carries the new token address in its first indexed topic, so there is nothing to guess and nothing to poll a launchpad for.
Nothing on this page comes from our own records or a third-party index. The engine reads Robinhood Chain block by block, pulls each new token straight out of the factory logs, then asks the contract itself for its name, ticker and logo. Every row you see was read off the chain, not taken from a launchpad feed.
rpc.mainnet.chain.robinhood.com
Not a screenshot and not a refresh loop. A row appears once the creation event has been mined, with the logo and ticker read out of the token contract itself. Pick one and the console opens with the contract already filled in.
The whole path is public. Anyone with an RPC endpoint can reproduce it.
The engine asks Robinhood Chain for new logs from the two Pons factory contracts. The creation event carries the new token address in its first indexed topic, so there is nothing to guess and nothing to poll a launchpad for.
Name, ticker, logo and description are stored on the token contract itself. One batched call through Multicall3 returns all of them for a whole block of new tokens at once, which is why a row never appears half filled.
The feed holds the most recent launches and nothing else. Older rows fall off the end instead of accumulating, so the monitor costs the same to run on day one and on day four hundred.
Buy flow above the axis, sell flow below, net position tracked as a line. Shape only, not a record of any particular run.
Illustration of engine behaviour. Chain and launchpad figures on this page are read live.
Read-only JSON, no key, no sign-up, CORS open. Same source as the page above, so what you read here is what the page shows.
https://www.ponsvolumebot.com/api/v1
Every response carries an ok flag. An address with no token contract behind it returns 200 with found set to false rather than an error.
curl -s https://www.ponsvolumebot.com/api/v1/telemetry | jq .curl -s "https://www.ponsvolumebot.com/api/v1/launches?limit=10" | jq ".items[]"curl -s https://www.ponsvolumebot.com/api/v1/token/0x0eb8b90bdF58A0a2d2a3BeAC6010bFEc9dc393cC | jq .None enforced today. The launch window is cached for a few seconds, so polling faster than that returns the same payload.
None. Everything here is already readable by anyone with a Robinhood Chain RPC endpoint.
Free to use, including commercially. A link back to ponsvolumebot.com is appreciated but not required.
Block height, gas price, block time and block fullness are read directly from the Robinhood Chain RPC endpoint at rpc.mainnet.chain.robinhood.com. New launches come from the creation logs of the Pons factory contracts, and every token's name, ticker and logo is read from the token contract itself. No launchpad API sits in the middle.
The live window is deliberately fixed in size. It holds the most recent launches rather than an archive, which is why the counts describe what this node has observed since it started rather than all-time totals it could not verify.
We publish no volume figures, no revenue, no user counts and no performance claims, because none of those could be checked by anyone reading this page. Everything above can be reproduced against Robinscan or against the RPC endpoint directly.
2026-10-19 11:17:29 UTC
The console reads the contract the same way this page does. Pick a launch above or paste your own, shape the run and sign once for a flat 1%.