Chrome extension · Robinhood Chain 4663

Every launch signs a list. Ponscan reads it.

Who the creator waved through for free, who paid the opening tax to arrive one second early, and where those same wallets have shown up before.

Add to Chrome — soonSee the numbersSee the card
ponsfamily.com/launchpad/0x7a3f…c419ponscan
Live

Read any launch in one call

The roster the creator signed, how much of it actually bought, and the opening histogram second by second — read from one call over the curve, in under a second, for a launch nobody has ever opened.

t=02.57 ETH1.00%
t=10 ETH—
t=20.03 ETH1.19%
t≥31.69 ETH1.00%

one launch, block 49,496,516 · bars are share of ETH in

Cold read
0.3–0.7s
Dune credits per view
0
Wallet needed
none
Live

Every figure hands over its call

verify copies the exact eth_getLogs that produced the card, and it resolves against the public RPC — not against ours.

Live

The Graveyard

98.99% of launches never reach a pool, over a denominator that is stated: 112,080 launches of one factory generation, at one block.

Live

The tax, priced by the second

6.18% at one second, 0.19% at two, nothing after — read from the fee ratio inside the buy event, so no timestamp is needed and no block has to be fetched.

Live

Burned at the gate

The wallets that arrived one second early and paid 99% for it. Rare, permanent, and the only thing on this site that is worth an alert.

Soon

Seen in other launches

The same wallet across rosters — the repetition that turns one list into a pattern.

Soon

Deployer history

Every launch a deployer has signed, and what happened to each of them.

Soon

Shared-roster graph

Which rosters overlap, drawn from the index that already exists.

Soon

Handle reuse

The X account on the launch, and how many other launches carry it.

Soon

Alerts

A gate burn or a community takeover, pushed the moment the log lands.

Soon

$SCAN tiers

Depth and history gated by holding, never the verdict itself.

the live read did not answer — the measured figures below are unchanged

Launches / hour

—

the window query was refused — nothing is inferred in its place

Graduations, all time

1,131

measured 2026-08-30

Launches counted

112,080

factory gen D, to block 50,221,343

Do not graduate

98.99%

1.009% clear the threshold

The signal

pons makes every creator sign the list.

Up to 32 wallets can be exempt from the opening tax, fixed at creation and permanent. The list is public — and missing from the protocol's own catalogue of indexable events.

Exemptions logged

228,980

86,627 unique addresses

In two or more launches

9,649

one address is exempt in 8,188

Wallets in 100+ launches

67

inside the informed window · one in 4,911

The opening tax

The tax is quantised by the second.

One second is ten blocks of resolution. Whoever stood in second one paid 6.18% to be there, and nobody pays that by accident.

Age of launchPublishedOn chain
t = 099%99.00%
t = 1~25%6.18%
t = 2~3%0.19%
t ≥ 3window of 5s0% — base fee only

Measured 2026-08-30 over 1.72M buys. The second is read from the ratio fee ÷ quoteIn inside the buy event — no timestamp is needed.

Burned at the gate

234.62 ETH

≈ $573,000 from 113 wallets that arrived one second early, in 27 days

Wallets that buy informed

1,340 of 116,489

1.1% of everyone who has ever bought. Small, permanent, and on no interface today.

The Graveyard

98.99% never reach the pool.

Nobody publishes that denominator, because it needs one: generation D of the launch factory, at a stated block. The rate rises over time, so a rate without a block was true once.

Graduated

1,131

measured 2026-08-30

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

half of all graduations happen inside it

The extension

The card, on the page you already use.

It sits in the launch feed and on the token page. No wallet, no login, nothing to connect.

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 reads identically either way.

Verify, from your machine

Every card hands over the exact call that produced it, resolved against the public RPC — not against ours.

the UI is still being built · the site works without it

Roadmap

Each line goes one layer deeper.

None of them builds a second product. The graph is a query over an index that already exists, and the wheel is a launch.

Now

  • The launch card, on any launch
  • Declared roster, and who of it bought
  • The opening tax and The Graveyard, with their method
  • verify — the call that reproduces every figure

Next

  • Seen in other launches
  • Deployer history and the burn register
  • Alerts on a gate burn and on a takeover
  • X handle reuse, from the signed metadata

Later

  • Shared-roster graph and holder concentration
  • The wheel — $SCAN inside pons, fees to the pot
  • The call tournament, settled by the chain
  • Public API

The verdict is free. You pay for speed and history.

If the label that protects a buyer sat behind a wall, the product would stop empowering the ecosystem and start taxing it.

Free

Labels, the launch 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.

Keeper

A multiplier on the pot.

Held, not subscribed

Tiers read the balance of a connected wallet. No subscription and no payment backend — sell the token and the access leaves with it.

The wheel

$SCAN launches inside pons with buyback enabled, collects creator fees in the protocol’s own escrow, and those fees fund the pot.

Aligned by construction

There is no version of this that earns while pons loses. More confidence in the feed means more volume, and the revenue is that volume.

$SCAN is not live — it is the Later column. Nothing on this page needs a wallet.