Enterprise - by agreement
On the chain, a launch that has happened 397 times looks brand new
GUCCI was launched as a Solana token in 397 launches from 34 wallets. Put any one of those launches in front of a scanner and it reads as new: a wallet with no history, a mint created seconds ago, an ordinary allocation, a curve that fills like any other. Everything a scanner reads was created minutes ago, so there is nothing in it to recognise. The four-hundredth run of an operation and a genuine first launch are the same object on chain.
What separates them is the file the launch declared about itself - its name, its ticker, its description, its links and its picture, published off-chain at the moment of creation. Reused across a run, it is byte-identical, and we hash it at the creation transaction for every launch on the venues we record. That turns the unrecognisable into a count you can read in the second a token appears, and decline on, instead of meeting it again in a complaint. It is not a rare case: one in five of every creator recorded launched with a file another wallet also launched with.
It also works where money tracing stops, which is the part nobody expects. Twelve wallets whose funding never converges launched 33 tokens in 48 hours, and no chain of transfers joins any two of them. Their own files connect them. Money can be routed apart; the files a brand is made of cannot, because relaunching something fast means reusing them.
What the same file means
{
"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.
Nobody can assemble this afterwards, which is why it does not already exist. Those files live on hosts the creators control and can stop being served at any time. There is no archive to buy, no endpoint to query and no amount of money that reconstructs a file nobody kept. The only way to have it is to have been capturing it, at the creation transaction, without stopping. We started on 2 September 2026.
36 of 400. One host carried the launch documents of 123,751 recorded launches, and on 28 September 2026 served 36 of 400 asked for at random. We hold them as they stood at launch.
For platforms, exchanges, investigators and compliance teams that want that as infrastructure rather than page by page: the creation feed as we record it, the documents corpus, bulk history scoped to the window your matter needs, and custodian declarations for records used as evidence. Every agreement is scoped and priced to what is actually being asked for. There is no standing download and no plan that opens one.
What an agreement can cover
| The record | Launches with their birth artifacts by hash, coverage windows, and the corrections register - at the depth and over the window your matter needs, not as one fixed file. The schema is public, column by column. |
| The documents corpus | The launch documents we hold, hashed at capture and dated to the second - including files whose hosts no longer serve them. Scoped per agreement. It is what connects operations whose funding never converges: in one measured case, twelve wallets financed through fifty pass-through wallets, no two chains meeting, were linked by five byte-identical documents. Money can be routed apart. The files a brand is made of get reused, because relaunching it fast means reusing them. |
| The feed | Token creations as we record them, for pipelines that cannot wait for the record cycle. Scoped per agreement. |
| Custody | Build fingerprints are published and snapshots are held off-site; custodian declarations for records used as evidence are available under agreement. |
See the data itself
The record's full schema, column by column with sample rows - the live documentation page, embedded here:
Listing diligence, on the record
Every launch we cover carries the same documented check - the same thresholds, published in Method, applied identically to every token and every customer. The result is a fact about the record ("checked, no markers found" / "findings on record"), never a judgment about a team. Your diligence file cites our record; the method and the corrections register stand behind it.
Why this and not Brand Protection
Brand Protection unlocks the pages for a person. An agreement hands your systems the data those pages are rendered from - the record over the window you need, the documents corpus by hash, and the feed - with terms, service levels and custody in writing. If your team asks "can we get this into our pipeline", you are an Enterprise conversation.
Invoiced, under a signed agreement, with a named contact. No checkout: this is a conversation.
Useful in a first email: what you would put the record behind, the venues and window you need, and whether records will be cited as evidence (that decides the custody terms). hello@chainoftitle.org