yolo
Also recorded, and not part of the finding above: this picture is on 1 other launch, all of them this same creator's, and this creator has 3 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, 12.8% of the launches whose picture we hold carry one only their own creator reused. 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.
Cite this record as: Chain of Title, yolo, mint 8XzeYJ3EPCKiQuD1DqevZMEd4CHz85BiKTX128ESpump, observed at creation 2026-11-10 09:14 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/8XzeYJ3EPCKiQuD1DqevZMEd4CHz85BiKTX128ESpump
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.
At launch
| Created | 2026-11-10 09:14 UTC |
| Creator | AkCQtAwSGSHK8mZkpzHuhoB9Td6i7sYJZYYNgtWEcGb5 |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 5 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: 5 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 0 min after launch |
| Curve on chain | Incomplete. We read the bonding curve account 8.9 h ago and it had not finished, though a graduation event was recorded for it. This launch is not counted as a graduation anywhere on this site. Checked 2026-11-10 18:33 UTC. |
| Creator sold | yes |
| Recorded from | ddAeh2n58GGdMz2dgFSo4k… slot 467,666,317
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | peak_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
| Created | 2026-11-10 09:14:56 UTC Slot 467,666,317, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-11-10 09:15:09 UTC +13s Not confirmed. An inference from decoded trade volume that nobody ever confirmed, and where the curve
account has since been read, the great majority of those returned incomplete. |
| Thirty seconds in | 5 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.
Seen before
| This picture | On 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 12.8% of the launches whose picture we hold carry one only their own creator reused. See them → |
| This ticker | On 255 launches from 191 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, 89.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| This creator | 3 earlier launches, none of which reached a graduation threshold while we watched. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches → |
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
| Name | yolo |
| Description | yolo |
| Metadata held | sha256 993315545c63cb0f35f8690cb3f7f7f607a1ca90e148549f5c0daee6f4b0f7c5 · 294 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 held | sha256 322fc771943f981a234be224ca8ee40fd52e862d18b15364c4c2dac266d7f7c0 · 62,728 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-10 09:14 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.