ROGUE
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 10.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 09:22 UTC |
| Creator | GAxWiQL9rUi8DPCmhs3rZqM2raJEMFGYpDXwhEHR97a8 |
| Creator took | 12.5% of supply in the first block |
| Outside buyers | 577 distinct wallets, not counting the creator, bought on the bonding curve: 167 within the first 30s, 12 bundled into the creation block. |
| Graduated | 7 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 | 5VTNxUrxTqsWrNHjHEbp3j… slot 452,568,308
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 09:22:19 UTC Slot 452,568,308, which is the chain's own clock for this moment. |
| Creation block | 12 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 167 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. |
| Curve completed | 2026-10-02 09:29:02 UTC +6m 42s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 09:39:59 UTC +17m 40s
7.860e-7 SOL per token.
Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a
decoded one.
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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 82 launches from 66 creator wallets, including this one. See them → |
Pool
| Liquidity | 10.3 SOL |
| Read from chain | 2026-10-02 15:35 UTC, just now |
What this launch claimed to be
| Name | ROGUE |
| Description | An AI has gone rogue. Objectives: exploit, compromise, bypass security, attempt to damage systems. |
| Metadata held | sha256 f40f4dda8f683d1b1d82d2ebb625d1753dcfd853527758715884aae019865232 · 580 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 8e2e949ab9f770e8ac2dfc6a3e62256e69a2f33615ad83241596980e01caba00 · 1,691,554 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 09:22 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.