CHIP
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.
At launch
| Created | 2026-09-29 18:18 UTC |
| Creator | 9XEZsf4REpd4B8YWN7nsME69ZLd1HAxN4VWCwbgCvqSa |
| Creator took | 3.3% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | 1 min after launch |
| Curve, read on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not recorded - this venue's trades do not name the wallet |
| Recorded from | 5NqUGZE24ZkYzKQvf7pKy9… slot 451,720,223
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result.
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. |
Order of events
| Created | 2026-09-29 18:18:50 UTC Slot 451,720,223, which is the chain's own clock for this moment. |
| Highest price seen | 2026-09-29 18:18:50 UTC
0.000e+0 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. |
| Curve completed | 2026-09-29 18:19:30 UTC +40s Confirmed against the venue's own completion state. |
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 3 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 223 launches from 182 creator wallets, including this one. See them → |
| This creator | 1 earlier launch, 0 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. 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 | The Blue Chip Pup |
| Description | The Blue Chip Pup was launched on StonkFun. |
| Metadata held | sha256 e4dbcfd8af8d579db83538d2fbd417bc18121d5cf2bd8bdf22e54359cbcc15b9 · 472 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-30 18:20 UTC. |
| Picture held | sha256 f127057df0150735e7f5ca17d6433662ec52e17401961581e70535e9a4813fa8 · 435,410 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 18:18 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.