T1K0
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, 53.2% 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.
Cite this record as: Chain of Title, T1K0 (T1k0), mint 13X9CiNX7kvsXPGd7tsTFdapDGmnYDzbPmXAzitxpump, observed at creation 2026-10-25 09:30 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/13X9CiNX7kvsXPGd7tsTFdapDGmnYDzbPmXAzitxpump
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-10-25 09:30 UTC |
| Creator | 3ete8va3Hgmsn8sa8NTioLZVFhLJLxEUXXh4Fx5pMiLn |
| Creator took | 79.3% of supply in the first block |
| Outside buyers | 0 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. |
| Graduated | yes; we did not record when |
| Curve on chain | Complete. We read the bonding curve account 7.6 h ago and it was finished. Checked 2026-10-25 09:35 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4B7v7eKPFcGfV3WGbumzpj… slot 461,206,899
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-10-25 09:30:09 UTC Slot 461,206,899, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | No 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. |
| Curve completed | Recorded as complete; we did not record when.
Confirmed against the venue's own completion state. |
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 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 53.2% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 21 launches from 14 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.2% wear one that more than one creator wallet has launched. See this ticker's page → |
| This document | The same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 30.3% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| Files shared with other wallets | Launches 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 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, 61.2% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Who took the curve
One transaction bought 85 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →
That is the same transaction the token was created in: the launch and the purchase of its float are one signature.
Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.
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 | T1k0 |
| Description | T1K0 — 24/7 AI SURVIVAL EXPERIMENT A robot crashed en route to another world. Stranded on a half-terraformed planet, T1K0 has one job: keep the island alive and grow it until Earth's rescue mission arrives. Every milestone unlocks something real — new skills, tools, buildings. The more the mission is backed, the further T1K0 gets. No script. No actor. The signal drops sometimes; it always comes back. |
| Metadata held | sha256 e05b3b790b632752e6308051b67bad80df4e5d922f779e8c392fe3f6131b985a · 786 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 c7fe0bbfc531cfb004c9274b5c3779ff80c9d89cba45823b6c3cf4d69c605d69 · 6,794 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-25 09:30 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.