IS
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 20:31 UTC |
| Creator | FqR7kSvgtH5LDUeDdPZkvVy9X18ryGT7gToi35YfWWL5 |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | 20 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 | 22dhPKjTTFJxRYfqioTU5B… slot 451,749,866
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. 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. |
Order of events
| Created | 2026-09-29 20:31:14 UTC Slot 451,749,866, which is the chain's own clock for this moment. |
| Curve completed | 2026-09-29 20:51:34 UTC +20m 20s 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 181 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 275 launches from 45 creator wallets, including this one. See them → |
| This creator | 2 earlier launches, 0 confirmed graduated on chain. 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 | unI repuS |
| Description | unI repuS was launched on StonkFun. |
| Metadata held | sha256 08e3b470daf2a9575955a64b692ce86b52dd607c52e7b050f8de63cc7b248811 · 572 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 20:32 UTC. |
| Picture held | sha256 01c718dda0a82aa6f88019780fdf5e22ea134221e6391ecc1f5343da57513070 · 25,960 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 20:31 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.