Every launch has a toll.
Ponscan reads a pons v2 launch and shows who paid the opening tax, who the creator waved through for free, and where those same wallets have shown up before.
Only what the chain signs. Every figure prints the call that reproduces it, and the call resolves against the public RPC — not against ours.
The Toll
0xcbfa…f1b6- Declared roster
- 33 wallets
- Waved through
- 1 of 33 bought
- Crossed early
- 60.64% of ETH in
- Burned at the gate
- 0 wallets
bars = share of ETH in · rate = fee ÷ quoteIn, which is what identifies the second a buy landed in — no timestamp is read
live · read from Robinhood Chain at block 50,321,161
refreshes every 5 min
Launches / hour
1,668
834 in the last ~30 min
Graduations, all time
1,198
latest at block 50,319,639
Launches counted
112,080
factory gen D, to block 50,221,343
Do not graduate
98.99%
1.009% clear the threshold
Latest launches
token · deployer · age
- 0x334f…392f0x155c…f6ca0s ago
- 0x398c…5c6d0x9022…bfc91s ago
- 0xa49d…b3a90xfe0e…53573s ago
- 0xa501…702d0x5be0…55195s ago
- 0xfdb9…39f70xeeef…2d2e9s ago
- 0x9f43…0f280x9f2d…213a14s ago
- 0x7333…51440xbbcb…0f6a25s ago
- 0x79b9…d1500x5be0…551928s ago
The signal
pons makes every creator sign the list.
A launch carries up to 32 addresses exempt from the opening tax, fixed at creation. The curve emits one log per address and the exemption is permanent. That list is public, and it is not in the protocol’s own catalogue of indexable events.
Exemptions logged
228,980
86,627 unique addresses
In two or more
9,649
11.1% of exempted addresses
One address, exempt in
8,188
launches
Wallets in 100+ launches
67
inside the informed window · one in 4,911
Repetition is the whole product. A roster of one is the ordinary dev buy and it is 89.84% of launches, so the signal starts at two, with the deployer excluded — the deployer is auto-exempt on every launch, which the create form does not say.
The Toll
The tax is quantised by the second.
At 100 ms blocks, one second is ten blocks of resolution. Whoever stood in second one paid 6.18% to be there, and nobody pays that by accident. Published rates and measured rates, side by side.
| Age of launch | Published | Measured on chain |
|---|---|---|
| t = 0 | 99% | 99.00% |
| t = 1 | ~25% | 6.18% |
| t = 2 | ~3% | 0.19% |
| t ≥ 3 | window of 5s | 0% — base fee only |
Measured 2026-08-30 over 1.72M buys, full history. The bucket is read from the ratio fee ÷ quoteIn inside the buy event itself.
Burned at the gate
234.62 ETH
≈ $573,000 · 113 wallets · 27 days
Money that arrives informed
17,732 ETH
3.5% of all ETH into curves
Wallets that buy inside the window
1,340 of 116,489
1.1% of everyone who has ever bought. That set is small, permanent, and on no interface today.
The Graveyard
98.99% never reach the pool.
Nobody publishes that denominator, because it needs one: the count is generation D of the launch factory alone, at a stated block. The rate rises over time, so a rate without a block was true once.
Graduated
1,198
gen D 1,197 · gen E 1
Cumulative rate
1.009%
1,131 of 112,080 at block 50,221,343
Mature cohort
0.872%
719 of 82,452 old enough to have finished
Median time to graduate
~8 min
4,892 blocks. Half of all graduations happen inside it.
Graduation is identified by what it leaves behind, not by a name: the same set of transactions mints a Uniswap v4 position inside the launch locker, emits PoolGraduated, and leaves the launch at phase == 2 — 1,131 of 1,131, with no exceptions. The published signature for that event has one address too many and hashes to a topic that is not on the chain.
The extension
The card, on the page you already use.
A browser extension that anchors the Toll Card into the launch feed and the token page, plus a permanent shareable URL per token and per deployer on this site. No wallet and no login for anything free.
Ponscan · injected here
Declared roster, who was waved through, the opening histogram, and the deployer’s other launches — inside a shadow root, so a host stylesheet cannot reach it.
Anchored, not scraped
The token address comes from the URL, never from the page. When the feed re-renders, the card survives.
Same answer with or without it
The extension and this site render from one engine, so a launch looks identical either way — and the site never depends on the host page.
Verify, from your machine
Every card hands over the exact eth_getLogs that produced it, resolved against the public RPC rather than any endpoint of ours.
Roadmap
Each line goes one layer deeper. None of them builds a second product.
That is the discipline that makes the promise true even where it is unmet: the graph is a query over an index that already exists, the tracking is the same query with more days on it, and the wheel is a launch.
Now
shipping- Toll Card: declared roster, roster that bought, opening histogram, burned at the gate
- Launch terms: creator tax, buyback, phase, distance to graduation
- The Toll and The Graveyard, with their method printed on the page
- verify — the call that reproduces every figure
- Permanent URL per token and per deployer
Next
days, not quarters- Seen in other launches — the same wallet across rosters
- Deployer history and the register of wallets burned at the gate
- Alerts on a gate burn and on a community takeover
- X handle reuse and churn, straight from the signed launch metadata
- Free and Holder tiers live
Later
depth, not new machinery- Shared-roster graph and holder concentration — a GROUP BY over an index that exists
- Exit shape over long history
- The wheel: $SCAN launched inside pons, creator fees funding the pot
- The call tournament — call it before minute ten, the chain settles it
- Public API, so other interfaces can carry the labels
$SCAN
The verdict is always free. You pay for speed, depth and history.
If the label that protects a buyer sat behind a wall, the product would stop empowering the ecosystem and start taxing it — the exact contradiction with its own name.
Free
Labels, the Toll Card, the histogram, the graveyard, the burn register.
Holder
+ 90 days of history, full roster lists, alerts.
Operator
+ roster graph, holder concentration, roster exits, API.
Toll Keeper
+ a multiplier on the pot.
Access by holding, not by subscription
Tiers read the balance of the connected wallet. No subscription contract, no payment backend, no account. Sell the token and the access leaves with it.
The wheel
$SCAN launches inside pons with buyback enabled, so it collects creator fees in the protocol’s own escrow, and those fees fund the pot for callers.
Aligned by construction
There is no version of this product that earns while pons loses. More confidence in the feed, more buyers, more volume, more fees — and the revenue is that volume.
$SCAN is not live. It is roadmap, listed above under Later, and it ships when the product is worth gating — not before. Nothing on this page requires a wallet.