2,416,505 launches on record
Coverage from 2 Sep 2026
Archive read 25 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

XTX

The curve completed in the same batch of events as the 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 2 other launches. 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. 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.

v2sv5awjgCV1jgMDz15u8Z7Gk5rwpNpqgrsfJxYpump Solscan pump.fun

Cite this record as: Chain of Title, XTX (PROJECT CORTEX), mint v2sv5awjgCV1jgMDz15u8Z7Gk5rwpNpqgrsfJxYpump, observed at creation 2026-10-25 23:00 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/v2sv5awjgCV1jgMDz15u8Z7Gk5rwpNpqgrsfJxYpump

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.

findingOnly 9 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.

At launch

Created2026-10-25 23:00 UTC
Creator9L1VSAtM6HnZ4ycLPdMaMEfB2YvmHG4o9WtuMhDm7vyz
Creator took1.0% of supply in the first block
Outside buyers9 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: 9 within the first 30s, 9 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.
Graduated0 min after launch
Curve on chainNot read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch.
Creator soldnot while we watched
Recorded from5yDEsvJKgf1Ft43KxGEL4k… slot 461,436,020
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

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-25 23:00:50 UTC
Slot 461,436,020, which is the chain's own clock for this moment.
Creation block9 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-10-25 23:00:50 UTC +0s
Confirmed against the venue's own completion state.
Thirty seconds in9 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.

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.

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
NamePROJECT CORTEX
DescriptionProject Cortex is the first decentralized "memory layer" for AI—a blockchain that doesn't just store data, but actively synthesizes and connects information across chains into a living, queryable knowledge graph. Instead of competing with AI models, Cortex acts as their shared long-term memory, letting any agent or application recall verified context from across the crypto ecosystem. Powered by proof-of-cognition consensus, it rewards nodes for mapping relationships between data rather than simp
Metadata heldsha256 db3986b129ddb035c9505197b3ed8211a067e40543cf1da9a3643491abd6117d · 955 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 b547925dbb9794df46346f0a4bac96ad49a527ba8d7d7e35bfd4bf874e861b3d · 752,521 bytes

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