Every token looks like a first launch. We show which ones are not.
We record every Solana launch as it is created and keep the files it published. So the record shows how many launches a wallet made, and which other wallets launched with the identical files: 236,666 wallets so far, in 81,020 groups, the largest of 591. Paste a token to see what is behind it.
The chain remembers what a token did. We keep what it claimed to be, copied and hashed as it launched, because the host those files sit on stops serving them.
One file. Fifteen wallets. 37 milliseconds.
{
"name": "BRAIN",
"symbol": "BRAIN",
"description": "Scroll less. Think faster. Ape smarter 🧠$BRAIN turns timeline chaos into a notice-think-ape loop built around conviction instead of noise.\nCreator rewards feed planned buybacks, burns, and on-chain receipts while organic frens rally around @brainclub_fun without bot-farmed hype 📲",
"image": "https://ipfs.io/ipfs/bafkreiawbz2wzxobciazym4rde6uj6374odpntcyfliz6yoh6af55hqdeq",
"showName": true,
"twitter": "https://x.com/brainclub_fun/status/2104290425922040081",
"telegram": "",
"website": "https://www.apeonbrain.fun",
"banner": "https://ipfs.io/ipfs/bafkreie4afuv7bgy3elmb2it5zecuofcso5pr2at53aw4yk3e7sa34fsui"
}| Wallet | Token | Launched | Fingerprint of its document | |
|---|---|---|---|---|
| 1 | 6459…jPd1 | 2svC…GJWF | +0 ms | 6151611e…e77d04 |
| 2 | 9L9x…bDzX | CscP…8t7m | +6 ms | 6151611e…e77d04 |
| 3 | 4zDw…22QB | 79LC…aoNr | +17 ms | 6151611e…e77d04 |
| 4 | BDc1…efRG | 43XG…oyj1 | +18 ms | 6151611e…e77d04 |
| 5 | 4rgY…vYy1 | 4BvL…V8RP | +19 ms | 6151611e…e77d04 |
| 6 | Crmq…zG6n | 9TY8…AmbV | +19 ms | 6151611e…e77d04 |
| 7 | 8Hzg…1tkt | GWKs…RQDf | +22 ms | 6151611e…e77d04 |
| 8 | hwGG…ky9S | 5ZXD…f9DX | +23 ms | 6151611e…e77d04 |
| 9 | AFNh…vJdi | Az55…gS5Q | +27 ms | 6151611e…e77d04 |
| 10 | A2L1…wVyC | 33WT…PWoj | +28 ms | 6151611e…e77d04 |
| 11 | Do2o…hpjk | EKnp…b7XL | +28 ms | 6151611e…e77d04 |
| 12 | 5zEr…pM4B | 285H…EZoC | +29 ms | 6151611e…e77d04 |
| 13 | DjNv…hS2c | E9JW…asb1 | +31 ms | 6151611e…e77d04 |
| 14 | DcLr…5Q3H | 4rus…68cC | +34 ms | 6151611e…e77d04 |
| 15 | DgzE…ugN6 | EFZa…AaHc | +37 ms | 6151611e…e77d04 |
9d34004a28966075d4b02572e615c3da5339283d89803d849d37de4afd8ad45binstead of 6151611e…e77d04. Nothing in common.A real launch document from the record, 27 September 2026 (UTC), printed as it was captured. Wallets and tokens are truncated. Times are our capture clock; a copy of every one of the fifteen was held within six seconds of its launch.
The match
Every launch publishes a small file about itself: its name, its ticker, a description, its picture, its links. Above, fifteen tokens from fifteen wallets carry one: the same 281-character description, the same emoji, the same links in the same order, 694 bytes and not one of them different. A fingerprint is computed from every byte. There are about 1077 of them, and no two different files have ever been shown to share one. These are not fifteen similar files. It is one file, fifteen times.
The line it draws
A wallet costs nothing and takes a second to make, so a new one arrives with no history, and money can be routed so that no transfer ever joins two of them. The file is the one thing that gets reused, because launching again quickly means reusing it. So every match draws a line between two wallets that nothing on the chain connects.
What the lines add up to
Lines join. One wallet shares a file with a second, the second shares a different file with a third, and three unrelated wallets become one group, with every launch any of them made. A thousand wallets stop being a thousand strangers and become a handful of groups that can be counted, dated and followed.
Why this is the whole thing. Without the file, every launch is a stranger's first. With it, counsel is looking at one group of wallets and not a thousand unrelated ones; a brand is looking at one run of launches and not hundreds of separate incidents; and a wallet app can tell its user that this exact file has launched before, in the second the token appears. None of it can be rebuilt afterwards: the files stop being served, and a fingerprint can only be taken of a file somebody kept.
Made, not stumbled on. A name is reused over weeks. A file is reused within minutes: of 85,952 groups of launches carrying one identical document, 81.83% were complete inside five minutes. The one route to identical files with nobody copying, a launch tool's blank default, is the kind shared least. What a match means, measured 2 September to 19 October 2026.
How a match leads to who. A match establishes that the same file was used, and a connection is never drawn from one coincidence. The person behind a wallet is known to the exchange or service its money came through, and a subpoena is how that is obtained. The provenance report traces each wallet's funding upstream hop by hop, with the transaction behind every hop, so counsel knows who to subpoena.
Twelve wallets no money trail joins. 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, and no two of those chains converge within the four hops the trace reached. 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, each with the second it was taken recorded beside it. No funding trail we could follow joins these twelve wallets. Their files do.
Same-second graduation on its own is ordinary: 3,419 of the 7,339 DBC graduations on record when the exhibit was built. 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
Because we kept the files, we connect what money cannot. 1,149,804 launches on record came from a wallet that has launched nothing else. 500,946 of those carried a launch document or an image a different creator had published first: not a lookalike, the same bytes, hashed at the second we took each copy.
On the chain each of them reads as brand new. In the record it is a count. What a match means.
The launch layer that wallet and flow analytics do not see.
A launch is in dispute.
One launch in full: 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.
$7,500Provenance report Brands and rights holdersA name is being launched without its owner.
An alert, usually within minutes, when a launch we record uses a name, ticker, creator wallet or image on the watch list. With unlimited lookups and the launches and wallets behind every count.
$79 a monthBrand Protection Wallets, terminals and researchUsers are asking where a token came from.
One request per token, returning the launch record and the transactions behind each figure, 250,000 requests a day - or a cent a read over x402, no key.
$299 a monthAPI Platforms and compliance desksThe record belongs in a pipeline.
For intelligence platforms, investigators and compliance desks: the record over the window a matter needs, the documents corpus by hash, and the creation feed, with service levels and custody in writing.
By agreementData agreementOne launch, as a document you can send: $49. A dated extract of a single launch with every other launch that carried the identical document or picture. No account and nobody to talk to: look the launch up and buy it from its own page. $200 for 10.
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.
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, where a third of launches put those files on a host the creator controls. Asked for documents it had served before, one such host answered for 60% of them on one date and 9% on another; on 14 October it answered for 123 of 230.
We capture that document at launch, a median of 0.3 seconds after we first see it, 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.
A few hours after a launch, looking at it tells you very little. The supply has been spread across many wallets and the pool holds real money, so a launch where the creator kept most of the supply and one with a genuine spread of buyers look alike. Every check you can run in the present tense comes back fine. That is not a gap in inspection, it is what inspection is: the early moments have stopped being visible. Replaying the whole chain afterwards recovers what the launch did, and never what it said it was. The measurements behind that.
36 of 400. The transaction is permanent. The name, the picture and the promise are not. One host carried the launch documents of 123,751 launches this archive had recorded by 28 September 2026; asked for 400 of them that day it served 36, and the Internet Archive's index of the whole host holds 32 of the documents this archive holds from it. Nobody can go back for the rest. 88% of this record was watched as the launch happened; the rest we found later from chain history, and every row says which.
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. Each figure counts the whole record unless it says otherwise, and the one that does not says so in its first line.
Shared image
The launch image, byte for byte, used by more than one creator wallet.
The creator's history
Prior launches and graduations confirmed on chain for the wallet behind this one.
Shared ticker
The same ticker, used by more than one creator wallet.
Identical documents
A launch document byte-identical to another launch's.
Who funded the buyers
The funding behind the wallets around a launch: chain facts and measured behaviour, never a label.
The document that stopped being there
A launch document rewritten or withdrawn after launch, measurable because we hold the bytes as they stood at that second.
One request per token.
Available today with an API key: the one call a wallet, terminal or compliance desk makes at the moment of contact. What the launch shares with others, what is known about the creator, and an evidence pointer for each observation. Every test reports whether it matched, came back clear, or could not be run at all, so a corpus we could not read is never returned as a clean result. Read the API.
The launch record itself, with what the creator took in the first block, who bought the curve and the transactions behind each figure, is GET /api/v1/token/{mint}. Looking up a single record on this site stays free.
// signals response { "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" } }
Five steps, the same for every launch.
Capture
We watch launches as they happen and copy each one's document and artwork while the host still serves them.
Hash
Every file is hashed at capture, with the second it was taken recorded beside it.
Connect
The same bytes on different launches are counted, across wallets no funding trail joins.
Corroborate
A connection is never drawn from one coincidence. Two instruments, or nothing.
Clear
Where a shared funder turns out to be a payment terminal, the record says so and clears the group.
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.
- CheckableEvery record cites the transaction it was decoded from, so a figure can be checked against the chain without trusting us.
- One methodThe same record for every customer: nothing here is written to order, and no customer can change what the record says.
- CorrectionsWhere we get something wrong, we correct it in the open and say what changed, including corrections to anything we sell.
- No verdictsWe publish observations and their evidence, never a verdict about a person.
The names the most wallets launched this week.
A name is free to reuse, and the record keeps every use. These are the tickers taken by the most distinct creator wallets in the seven days ending 2026-11-22 (UTC), counted from the record. Every name links to its full record: each launch that wore it, the wallets that launched it, and what became of each.
Counts are observations over recorded launches, not statements about any project carrying the name. They move as the archive grows.