RBTX
Also recorded, and not part of the finding above: this picture is on 3 other launches, all of them this same creator's, and this creator has 77 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, 14.4% 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, RBTX (ROBOTAXI), mint A5LciM1YUD9rCpgbBkMwC4YdS6PWhEiYLvDZhYWdpump, observed at creation 2026-09-03 03:30 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/A5LciM1YUD9rCpgbBkMwC4YdS6PWhEiYLvDZhYWdpump
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-09-03 03:30 UTC |
| Creator | AfCAdGcvFkZRTrW5GL6zZoFuLZYhoNRNdv41Te2kLa1a |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | unknown 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: 3 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 12 min after launch |
| Curve on chain | Complete. We read the bonding curve account 33.9 days ago and it was finished. Checked 2026-09-10 00:19 UTC. |
| Creator sold | yes |
| Recorded from | 2Y5FNU4wBpkx1egaDRWdBN… slot 443,868,635
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
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.
Order of events
| Created | 2026-09-03 03:30:58 UTC Slot 443,868,635, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Highest price seen | 2026-09-03 03:30:58 UTC +0s
5.257e-8 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
| Thirty seconds in | 3 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 completed | 2026-09-03 03:42:36 UTC +11m 38s 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 4 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 14.4% of the launches whose picture we hold carry one only their own creator reused. See them → |
| This ticker | On 28 launches from 8 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 document | The same launch document, byte for byte, as 3 other launches, all of them this same creator's. Across the archive, 11.2% of the launches whose document we hold carry one only their own creator reused. See them → |
| This creator | 77 earlier launches. All 3 that reached the graduation threshold on our feed were read on chain, and none had completed. Across the archive, 70% 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 | ROBOTAXI |
| Description | RoboTaxi is becoming the car of the future. Leaving Uber and Lyft behind. BIG TIME |
| Metadata held | sha256 c26ddef1f53df7e4dd0dddd1433bcd831aa3de791d038b34bac6e103ccb5bfad 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-22 18:14 UTC. |
| Picture held | sha256 2fef84a3a9de7ebca4214d8e004e9033fb8feeddc57315803667a994f1bf8078 · 429,147 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-12 03:30 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.