2,653,228 launches on record
Coverage from 2 Sep 2026
Archive read 22:00 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

SSF

The creator took 20% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

Also recorded, and not part of the finding above: this picture is on 57 other launches from 36 creator wallets in all, and this creator has 511 other launches on record. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 54% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.

A8MR7NnYgyXP9pa94rSsWuhHBYD18Sd7GsL5VQM42Mkc Solscan pump.fun

Cite this record as: Chain of Title, SSF (Scam Center Strike Force), mint A8MR7NnYgyXP9pa94rSsWuhHBYD18Sd7GsL5VQM42Mkc, observed at creation 2026-10-27 16:17 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/A8MR7NnYgyXP9pa94rSsWuhHBYD18Sd7GsL5VQM42Mkc

Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.

noteThe creator took 20.1% of supply at launch.

At launch

Created2026-10-27 16:17 UTC
CreatorG3eWaBWuboTjBARo2otA6o3GEg9LFkd1Pf7N3yw8sSz1
Creator took20.1% of supply in the first block
Outside buyers0 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 0 within the first 30s, 0 in the very same block the token was created in.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldnot while we watched
Recorded from23KxHnfRJUPK8cHvJjrh91… slot 462,135,077
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Several launches in one matter

A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.

Order of events

Created2026-10-27 16:17:12 UTC
Slot 462,135,077, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Highest price seen2026-10-27 16:17:12 UTC
4.233e-8 SOL per token. Decoded from an on-chain transaction that executed at that price. A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not here.
Thirty seconds inNo buyer, within the first thirty seconds.
A snapshot taken off a tick at the thirty-second mark, so it carries no moment of its own; it is placed here because that is where it happened.

Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.

Seen before

This pictureOn 58 launches from 36 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 54% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 53 launches from 33 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 88.4% wear one that more than one creator wallet has launched. See this ticker's page →
This creator469 earlier launches, 5 confirmed complete on chain, 1 with findings on record. Across the archive, 70.1% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 341 other creator wallets, across 352 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 62.1% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.

What this launch claimed to be

The picture this launch published at birth
NameScam Center Strike Force
DescriptionFees to @jncquant via UsePaid
Metadata heldsha256 473392c01e21998d25ab19d17de05215c547dd57362dfe8363d0bf6b71e837f9 · 385 bytes
Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree.
Picture heldsha256 516a697135abd559a568da0e90f4eaf4631d2716d658628be7ec86cfb2ff7dbc · 10,580 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-27 16:17 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another