TJR
Also recorded, and not part of the finding above: this picture is on 1 other launch, all of them this same creator's. 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, TJR (Top Float Boss), mint 39RWJFgkfkNtLgzZZq9JmvwqrRKnV7j8NqbzGfnkpump, observed at creation 2026-11-09 19:05 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/39RWJFgkfkNtLgzZZq9JmvwqrRKnV7j8NqbzGfnkpump
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-09 19:05 UTC |
| Creator | GKJ1fDr6UBXB8hyVFfT4x79SYtbLfgjLwdCkoCMuvo4D |
| Creator took | 6.5% of supply in the first block |
| Outside buyers | 6 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: 6 within the first 30s, 6 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 | 0 min after launch |
| Curve on chain | Complete. We read the bonding curve account 10.5 h ago and it was finished. Checked 2026-11-09 19:13 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4HEHWXMjwxL79dFkDawua3… slot 467,428,475
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 19:05:22 UTC Slot 467,428,475, which is the chain's own clock for this moment. |
| Creation block | 6 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-11-09 19:05:25 UTC +4s Confirmed against the venue's own completion state. |
| Thirty seconds in | 6 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 556 launches from 345 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.4% 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, all of them this same creator's. Across the archive, 11.9% of the launches whose document we hold carry one only their own creator reused. See them → |
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 | Top Float Boss |
| Description | TJR posted about the 'Top Float Boss', the floating king. The background features a leisurely man floating on the sea, and its emblem shows a long-haired man floating on the water. |
| Metadata held | sha256 9cd1daf66db62aaa6d8c6bcffa10e2041fcc860ec36bdba2daf7289d2dc3ff34 · 446 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 f9e5d3138e85bab9ca917d00056d6551836b094f6913981407e08f4b6e1a3c81 · 41,718 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-09 19:05 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.