508,371
launches on record, ~36k a day
Every Solana token launch, recorded the moment it happens
The chain remembers what a token did. We remember what it claimed to be.
Every launch presents itself with a name, an image and a promise, on hosts that can stop serving within days. We record each launch from its creation transaction and keep the half of the record that cannot be rebuilt later - and because we keep the files, we connect what funding trails cannot: wallets with no money in common, linked by the artifacts they launched with. We keep the copy.
Pricing and data access
See it done: the graduation machine
Looking up a token is free, with no account.
Record of provenanceIllustrative specimen · not a real token
MintSPECI…MENpump
Document capturedcreation + 1.36 s
Creator share, block 11.74%
Image sha2564367b4…6f655f
Signals, with evidence
image appears on 12 launches, 3 distinct creators
ticker used by 7 creators
creator has 14 prior launches, 2 confirmed graduated
graduation confirmed against the curve account
Every line on a real record links to the transaction or hash it rests on.
0.6 s
median, creation to our copy of the launch document
1,859,176
token creations read chain-wide, every program
2 Sep 2026
observed since, 46 min recorded downtime
What the record caught
Twelve wallets with no money in common. Their files connected them.
Over 48 hours, twelve wallets launched 33 tokens on Meteora DBC. All 33 graduated, every curve completing in the same second its token was created, and every launch set the creator's share to exactly 19.99%. The wallets were financed with 3,088 SOL routed through about fifty single-use pass-through wallets, four or more layers deep, with no two funding chains converging. To a funding-flow tool, twelve strangers.
Five of their launch documents were byte-identical. We hold those files because we copied them as the launches happened, from hosts that stop serving within days.
12
wallets
33 of 33
graduated
19.99%
creator share, every launch
3,088 SOL
through ~50 pass-through wallets
5
byte-identical documents across the wallets
Same-second graduation on its own is ordinary: 3,419 of 7,339 in this archive. Thirty-three of thirty-three, on identical parameters and a shared schedule, is not. Every figure here is from one published exhibit, dated and citing the transaction behind it.
Read the exhibit All published exhibits What a provenance report contains
What only the record holds
A launch is a claim before it is a track record.
The transaction ledger is public and permanent, so anyone can reconstruct what a token did. What cannot be rebuilt is what it said it was at launch: the metadata, the image and the socials, served from a host the creator controls. One host that carried tens of thousands of launches stops serving each document within two to three days.
We capture that document at launch, a median of 0.6 seconds after creation, hash it, and keep it. When a promotion disappears, the record of it does not. When a story changes after launch, we hold the original to measure the change against.
Hours later the first blocks stop being observable. Once the float is spread across wallets and the pool holds real SOL, a launch whose creator took the supply and one with a spread of buyers read the same: pool depth reconciles, holder concentration looks ordinary, the authorities are clean. Every present-tense check passes. That is not a gap in after-the-fact analysis; it is a property of it. The measurements behind that.
What a lookup returns
Signals, each with the evidence behind it.
Given a token, what it shares with other launches and what is known about its creator: measured observations with the rows behind them, and never a verdict. The figures below are measured on the current record.
image.crossCreator
Shared image
The launch image, byte for byte, used by more than one creator wallet.
522 creator wallets on the most-shared image
creator.repeat
The creator's history
Prior launches and graduations confirmed on chain for the wallet behind this one.
31,128 creator wallets with two or more launches
symbol.shared
Shared ticker
The same ticker, used by more than one creator wallet.
34,795 tickers used by two or more creators
metadata.duplicated
Identical documents
A launch document byte-identical to another launch's.
152,593 launches sharing a document
funder.sharedCohort
Who funded the buyers
The funding behind the wallets around a launch: chain facts and measured behaviour, never a label.
89 launches where a recorded buyer's funder also funded buyers of other launches, infrastructure excluded
metadata.changed
A document that changed
A launch document rewritten after launch, measurable because we hold the original.
3 documents re-read after launch no longer match their launch-time capture
For builders
One request per token.
GET /api/v1/token/{mint}
Available today with an API key: the launch record, what the creator took in the first block, who bought the curve, how it graduated, and the transactions behind each figure. Read the API.
In development: the signals response on the right, for the one call a wallet, terminal or compliance desk makes at the moment of contact. Looking up a single record on this site stays free.
// signals response, in development { "mint": "…", "birth": { "capturedAfterSec": 1.36, "devPct": 1.74, "imageSha256": "…" }, "signals": [ { "code": "image.crossCreator", "creators": 3, "evidence": "/api/v1/image/…" }, { "code": "creator.repeat", "priorLaunches": 14, "graduatedConfirmed": 2, "evidence": "/api/v1/creator/…" } ], "outcome": { "graduatedConfirmed": true, "confirmedBy": "curve_account" } }
What we sell
The launch layer that wallet and flow analytics do not see.
Provenance report$7,500 per tokenOne launch in full, for a dispute or a listing file: what the creator took in the first block, who bought the curve, what the launch claimed about itself as captured at the time, and the transaction behind every figure. Dated, scoped and signed - and a specimen is published.
Data agreementby agreementFor intelligence platforms, investigators and compliance desks: the record as a file, the documents corpus by hash, and the creation feed, with service levels and custody in writing.
API$299 a monthFor wallets, terminals and research: one request per token, returning the launch record and the transactions behind each figure, 10,000 requests a day.
Watches$79 a monthFor a team protecting its name: an alert within hours when a launch we record uses a name, ticker or image on your list, and the launches and wallets behind every count.
All plans and data access hello@chainoftitle.org
A report engagement is scoped in writing before it is quoted, and declined where the record cannot support the work.
How to check us
We record. We do not adjudicate.
Every figure cites a transaction. The method is published and runs the same on every launch, whoever is asking.
Where we get something wrong, we correct it in the open and say what changed, including corrections to anything we sell. We publish observations and their evidence, never a verdict about a person.