2,088,005 launches on record
Coverage from 2 Sep 2026
Archive read 22:36 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

ZENO

Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 0.2%, 91 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. These tests read this launch's own first blocks and nothing else. What this launch shares with other launches - the same picture, the same document, the same creator - is counted separately, below, and is not part of this answer.

Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 creator wallets in all. 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, 50.1% 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.

FMGe8RStdPc1YR59BBuV5Ui12DEe3Q2zVoihrJBbpump Solscan pump.fun

Cite this record as: Chain of Title, ZENO (Zeno Paradox), mint FMGe8RStdPc1YR59BBuV5Ui12DEe3Q2zVoihrJBbpump, observed at creation 2026-10-18 18:20 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/FMGe8RStdPc1YR59BBuV5Ui12DEe3Q2zVoihrJBbpump

At launch

Created2026-10-18 18:20 UTC
Creator4FTCG2mgoDfiQ6Xow5dN9oCovWMehXRJgnjqUv33GrHJ
Creator took0.2% of supply in the first block
Outside buyers91 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: 15 within the first 30s, 1 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated59 min after launch
Curve on chainNot re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers.
Creator soldnot while we watched
Recorded fromVyt6Ub9xcRi2NsLqsJDLJW… slot 458,532,355
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.

Order of events

Created2026-10-18 18:20:52 UTC
Slot 458,532,355, which is the chain's own clock for this moment.
Creation block1 wallet bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in15 distinct buyers, 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.
Curve completed2026-10-18 19:19:33 UTC +58m 41s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-18 19:19:33 UTC +58m 41s
4.109e-7 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.

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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 50.1% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 36 launches from 32 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, 87.7% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 27.2% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 1 other creator wallet, across 3 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 of 2 creator wallets in all. Across the archive, 59.4% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

Liquidity81.6 SOL
Read from chain2026-10-18 23:37 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameZeno Paradox
DescriptionZENO is the community token powering an emerging intelligence ecosystem built around Surprise Intelligence and AI forecasting agents. Humans and AI challenging consensus, exploring unexpected outcomes, and building a community that rewards collective intelligence, prediction challenges, open research, and public goods. Question everything. Forecast what others miss. Beyond Consensus.
Metadata heldsha256 0547f15082ac1e58d8fe884e8ba916c0456a0a0852b5db18fb568bbbe1838661 · 693 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 05f81e17de0e094e35c25d1bde8d480faf4be2dea29ff2d6ba91f403fee6d6d1 · 443,567 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-18 18:20 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