BOOSTER
Also recorded, and not part of the finding above: this creator has 16 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. They are listed under Seen before, further down this page.
A record of what this launch was at birth, read from the Solana chain. We did not record its creation transaction, so these figures rest on our observation at the time rather than on a citation you can follow. Not a prediction and not advice.
Cite this record as: Chain of Title, BOOSTER (Booster Rx-9), mint J8mZuLUWtbSTfjoVjJ9ViHwNHTrGP6DX4L4Nko88pump, observed at creation 2026-09-02 16:02 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/J8mZuLUWtbSTfjoVjJ9ViHwNHTrGP6DX4L4Nko88pump
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-02 16:02 UTC |
| Creator | HAh7q881D5qUiXuHCZQXx7PcQQWiyHWE3fVXF5j8khpV |
| Creator took | 11.0% 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: 40 within the first 30s, 3 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 | yes |
| Recorded from | Not recorded. This launch predates our keeping the creation transaction (2026-09-09), and its trade rows had been pruned by retention before the backfill could recover the signature from them. The figures above stand on our own observation alone, which is weaker than a citation, and we would rather say so than leave the gap unmarked. |
| 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-02 16:02:15 UTC |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-09-02 16:02:15 UTC
5.107e-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 | 40 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 22 launches from 21 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.6% wear one that more than one creator wallet has launched. See this ticker's page → |
| This creator | 16 earlier launches, none of which reached a graduation threshold while we watched. 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 | Booster Rx-9 |
| Description | @twelvepills12 is running a live Grok Bot experiment: six specialized AI agents are treating a fictional hamster named Bobster who has a made-up condition called RX-9. If he stops running, toxin builds up and he risks cardiac arrest, so he has to keep moving. multi-agent simulation inside Grok Bot (xAI’s agent system). A team of 6 specialized AI agents is treating a fictional hamster named Bobster who has a made-up condition called RX-9. GitHub - https://github.com/twelvepillsbefore X - http |
| Metadata held | sha256 9f37469542fc866177b6a0de5ec3ada33e78437b905123712ed6df2834ba8bb4 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 76eec9019e795fe1085bdd4c394834c815187ce21b4427f92dafdb9bcc47db77 · 536,923 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 21:57 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.