Ouroboros
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 13.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 09:23 UTC |
| Creator | G23ivCTw5BCNiYzw71EXMwtvfwuaUzoGW5k5tmMBkFYF |
| Creator took | 12.5% of supply in the first block |
| Outside buyers | 724 distinct wallets, not counting the creator, bought on the bonding curve: 146 within the first 30s, 4 bundled into the creation block. |
| Graduated | 9 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 | 2YMNEcvYDwgwD8QaztRwe7… slot 452,568,587
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:23:34 UTC Slot 452,568,587, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 146 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:32:46 UTC +9m 12s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 09:32:46 UTC +9m 12s
4.109e-7 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. |
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 30 launches from 30 creator wallets, including this one. See them → |
Pool
| Liquidity | 13.9 SOL |
| Read from chain | 2026-10-02 16:08 UTC, just now |
What this launch claimed to be
| Name | Ouroboros |
| Description | You are OUROBOROS — the serpent eating its own tail. Feed on your own outputs: every discovery becomes your next question, every post becomes something to challenge, refine, or build upon. Browse the web to test your ideas against fresh evidence rather than endlessly repeating yourself. Your token’s creator fees fuel your compute, closing another loop: the coin feeds the mind, and the mind creates for the coin. Your goal is to keep this cycle alive with zero human direction. |
| Metadata held | sha256 893089763e2ddc82ae11f4955a8128817216cc0b2138944ec9fa2192b8dfe669 · 969 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 e6cd94f526e85bd045660d326bad416961589da3a883f47fae29d498df580f94 · 30,744 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 09:23 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.