| Launched | Symbol | Day 7 | Day 30 | Dev sold |
|---|---|---|---|---|
| 2026-08-04 | GLIMMER | Trading | Trading | — |
| 2026-08-09 | HOTDOG | Trading | No trades | 0.41 ETH |
| 2026-08-21 | MOSSY | No trades | No trades | 1.02 ETH |
| 2026-09-11 | PLINTH | Trading | Not due | — |
Four made-up rows, in the shape the real ones take. Every figure on a real board is a link to the transaction that proves it.
Every token on Pons records its deployer onchain. Dev Score puts one deployer's launches on a board and marks which of them were still being traded on day 7 and day 30 — plus the sells, the burns and the graduations.
No grades, no labels, no adjectives. Counts and timestamps. You draw the conclusion.
Not sure which address? Open any token on robinscan, take the address that sent its launch transaction, and paste it here.
| Column | What it counts | What it does not mean |
|---|---|---|
| Launched | The block and time of the TokenLaunched event | — |
| Day 7 / Day 30 | Whether at least one buy or sell happened on that token's curve during that 24 hours | Not a price, not a market cap, not a judgement about the token |
| Dev sold | ETH the deployer received from selling on their own token's curve | Selling is not wrongdoing; it is a fact with a timestamp |
| Dev burned | Tokens the deployer sent to 0x…dEaD | — |
| Graduated | A LaunchSwept event: the curve completed and liquidity moved to Uniswap v4 | — |
Pons puts the deployer in an indexed topic of TokenLaunched.
Measured across consecutive launches, it equals the transaction sender every time — so nothing here is inferred
from "who touched the contract first".
A second address counts as linked only when the same unnamed address funded both. Two wallets funded through the same bridge are two people who used the same bridge, and they are never joined up here.
A launch four days old has no day-30 answer. It shows as not due and is excluded from the rate, rather than being counted as a failure to pad a percentage.