CHRM
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, CHRM (CHROMA CRITTER), mint 73zHxEXR9UNNzwLpnNk7SBW9Kh4qmxxuzB2R5jfVpump, observed at creation 2026-09-03 11:03 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/73zHxEXR9UNNzwLpnNk7SBW9Kh4qmxxuzB2R5jfVpump
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-03 11:03 UTC |
| Creator | 3d3mTLTMWofB3a78LfNNDzgeLP99KqFBdRLyE2ETQoJc |
| Creator took | 0.2% 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: 75 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 | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | 5HLfetvgZdJH3Uga3jTLaR… slot 443,955,061
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-03 11:03:37 UTC Slot 443,955,061, 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. |
| Highest price seen | 2026-09-03 11:03:37 UTC
5.045e-7 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. |
| Curve completed | 2026-09-03 11:03:37 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 75 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 9 launches from 8 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 → |
Pool
| Liquidity | 2.0 SOL |
| Read from chain | 2026-10-24 04:48 UTC, just now |
What this launch claimed to be
| Name | CHROMA CRITTER |
| Description | Broadcasting from the wrong channel. $CHRM. Eyes on chain |
| Metadata held | sha256 018731e19a7e8f7396c298f5728730feda3c5d869c52ccd596334300b46db877 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-22 17:38 UTC. |
| Picture held | sha256 3fb97f9997cc34a0e62c4a69ed8504415a7c98fbe166e2d29ea3ef3b133f40fd · 39,254 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-12 05:34 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.