RSI
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
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.
noteOnly 2.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 08:24 UTC |
| Creator | GC1ZqBW3pVgZQ2b4K3b2jrybCa82HdhJBGB2mMSNbBDg |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 200 distinct wallets, not counting the creator, bought on the bonding curve: 0 within the first 30s, 0 bundled into the creation block. |
| Graduated | 2 min after launch |
| Curve, read 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 | 5H1Sx7UPhwdRozos5P5HAv… slot 452,555,237
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 08:24:04 UTC Slot 452,555,237, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | No buyer, 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. |
| Curve completed | 2026-10-02 08:25:39 UTC +1m 36s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 08:30:39 UTC +6m 36s
0.000e+0 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. |
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 8 launches from 8 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 160 launches from 131 creator wallets, including this one. See them → |
| This document | Byte-identical to 4 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 6 other creator wallets, across 3 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
| Liquidity | 2.0 SOL |
| Read from chain | 2026-10-02 15:27 UTC, just now |
What this launch claimed to be
| Name | Recursive Super Inu |
| Description | Rsi>agi >ai Basically the final boss |
| Metadata held | sha256 58ff01f872dc33777f8d53133ad82dcfd7605bee7b64b6a56554c67274ceb07e · 339 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 9b0a59d578b04ad94542281ee9c599e2f50ade8d7a844f36207c5cf4dc6bccdd · 523,084 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 08:24 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.