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, (Cybercab), mint Bhuwp5fvaQXhV78irMS7frfyEdKdVWmbDtV64iwppump, observed at creation 2026-11-09 09:21 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/Bhuwp5fvaQXhV78irMS7frfyEdKdVWmbDtV64iwppump
At launch
| Created | 2026-11-09 09:21 UTC |
| Creator | 4XJUtniK4EgWjS59YV3CimUBYr3Y1JZ5iEWTj2muNRks |
| Creator took | 6.6% of supply in the first block |
| Outside buyers | 2 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: 2 within the first 30s, 2 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. |
| Graduated | not while we were watching |
| Curve on chain | Nothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them. |
| Creator sold | not while we watched |
| Recorded from | 7PUQ5JiDjz5tBXGGprEezK… slot 467,265,318
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-09 09:21:46 UTC Slot 467,265,318, which is the chain's own clock for this moment. |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 2 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 | No other launch we hold a picture for used this one. |
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 | Cybercab |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 8ddbad653f7c56704bf63f77fc53c2501402993a4d22505d2854d736a30f45ab · 279 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 edad0477c5c83b27e4912106bf9d477dc93d55683f30620b704ab96f636f1aa4 · 11,468 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-09 09:21 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.