1,846,529 launches on record
Coverage from 2 Sep 2026
Archive read 13:07 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

MIND

Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 1.5%, 330 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, 48.9% 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.

H92HdFid62eABSbb1WaQNbVJBJzDAn5HiQCDSSJqpump Solscan pump.fun

Cite this record as: Chain of Title, MIND (Mindshare), mint H92HdFid62eABSbb1WaQNbVJBJzDAn5HiQCDSSJqpump, observed at creation 2026-10-12 18:03 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/H92HdFid62eABSbb1WaQNbVJBJzDAn5HiQCDSSJqpump

At launch

Created2026-10-12 18:03 UTC
CreatorC1N6HsqeeJ7BryiXbQHLN43oJHTXHn1FowYTqv8ZaWxU
Creator took1.5% of supply in the first block
Outside buyers330 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: 124 within the first 30s, 10 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.
Graduated5 min after launch
Curve on chainComplete. We read the bonding curve account 22.1 h ago and it was finished. Checked 2026-10-12 18:51 UTC.
Creator soldnot while we watched
Recorded from38fwazBwBSXoPqhDUoARbY… slot 456,138,339
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-12 18:03:09 UTC
Slot 456,138,339, which is the chain's own clock for this moment.
Creation block10 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in124 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-12 18:08:13 UTC +5m 04s
Confirmed against the venue's own completion state.
Highest price seen2026-10-12 18:08:13 UTC +5m 04s
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, 48.9% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 426 launches from 170 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.2% 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, 25.7% 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, 58.4% 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
NameMindshare
DescriptionAn AI agent with its own treasury whose mind is written by its holders. Every 10,000 $MIND you hold is one prompt token you can write into its system prompt. Every 10 minutes it reads its whole brain and decides what to do with the creator fees: buy back and burn, buy another coin, post, or hold. It shows whose words it followed and whose it ignored. Sell, and your words are cut out.
Metadata heldsha256 de07c7cd9b5ca9ed86d16c5e04853e6a1b997241f636f70fbc9a5aa577c4ce52 · 650 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 5fb6fed8bd8fe36bd120deb5c496be15462d095a31fffe9c6b2dbe5d8c60a105 · 50,349 bytes

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