Tomo
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, Tomo (Tomothy), mint DE3hzo1vVQ3nKqQF7bv7S1QVb34gntUXrehCHcXjpump, observed at creation 2026-09-02 22:39 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/DE3hzo1vVQ3nKqQF7bv7S1QVb34gntUXrehCHcXjpump
At launch
| Created | 2026-09-02 22:39 UTC |
| Creator | FEpS8NWgc8FQi6iiPWXzJMioZSQ8vG1naLKjE1akH4on |
| Creator took | 1.1% 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: 2 within the first 30s, 0 in the very same block the token was created in. |
| 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 | 3opMoHg5EsapedqRK4buww… slot 443,813,207
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.
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-09-02 22:39:50 UTC Slot 443,813,207, 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-02 22:40:14 UTC +24s
3.070e-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 | 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. |
| This ticker | On 25 launches from 20 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 → |
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 | Tomothy |
| Description | Jimothy got the short spine, the Google Easter egg, and the city of Seattle. Tomothy got a real neck and zero press. He’s the brother who actually looks like a raccoon. Same mask, same trash-can résumé, same 2 a.m. sidewalk energy….just none of the lore. While Jimothy runs the timeline, Tomothy is in the grass doing raccoon things and wondering why nobody named a coin after him first. This is that coin. The normal one. The one that still dumps in your bins. $TOMOTHY |
| Metadata held | sha256 0d0688cc4911685a8b8e970463b4d6959d74311da1fb8d05e61287714f955d77 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 aa161c089b36e058d846a9c101caf21aa26fdbb2bcb307b21e7bb5250b2a65ef · 471,775 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-11 00:48 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.