FBI
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, 52.8% 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, FBI (FBI Joined the Lobby), mint 6hL9nyCMVp4pDi26v8tE2P1sCgScEGtVgaxgositpump, observed at creation 2026-10-23 23:28 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/6hL9nyCMVp4pDi26v8tE2P1sCgScEGtVgaxgositpump
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-23 23:28 UTC |
| Creator | BWTGEBjeAbsnkky9QTpo4K8yiLgwZGT777pnJW1CUkZA |
| Creator took | 1.0% of supply in the first block |
| Outside buyers | 5 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: 5 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 9.7 h ago and it was finished. Checked 2026-10-23 23:38 UTC. |
| Creator sold | not while we watched |
| Recorded from | 38QrAnGtm4vtBtmJmqKcF9… slot 460,629,943
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | snap30_buyers - no thirty-second snapshot was taken, and that snapshot is meaningful only for an observed launch.
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-23 23:28:49 UTC Slot 460,629,943, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-23 23:28:50 UTC +1s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-23 23:28:50 UTC +1s
4.109e-7 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
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, 52.8% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 152 launches from 79 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.1% 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.1% 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, 60.5% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
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 | FBI Joined the Lobby |
| Description | A Fortnite player who threatened to shoot the FBI in voice chat was arrested by the FBI WagesOfNinja told another user "Let's see if the FBI is going to show up at my door because I'll shoot them motherf**kers too" |
| Metadata held | sha256 a5396f5735918f3e7ee5b5be7cd300ffd9f65d9af32017e0e99bbb4ad44ee9a5 · 597 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 89c16f699076c8ad0db36248e3ff83e15fb13b7b1c0c2a37c5367565992211b7 · 246,533 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-23 23:28 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.