PETER
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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.
noteThe creator sold while we were watching.
noteOnly 0.4 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 18:55 UTC |
| Creator | feUvp698eqdki4prZwmGyDhQ4DTRbEJtuvP6s8qRvST |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 20 distinct wallets, not counting the creator, bought on the bonding curve: 0 within the first 30s, 0 bundled into the creation block. |
| Graduated | 9 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 | yes |
| Recorded from | 5LcFsuFVxQYvtq38CbVZrn… slot 452,051,367
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 18:55:45 UTC Slot 452,051,367, 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-09-30 19:04:32 UTC +8m 47s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 19:11:46 UTC +16m 00s
3.237e-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 2 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 128 launches from 40 creator wallets, including this one. See them → |
| This creator | 22 earlier launches, 4 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 5 shared artifacts, each matched by hash. Together they sit in a linked group of 3 creator wallets. See the linked wallets → |
Pool
| Liquidity | 0.4 SOL |
| Read from chain | 2026-10-01 02:20 UTC, just now |
What this launch claimed to be
| Name | PETER THE FAILURE |
| Description | Peter thought he was going to make it. He put on the suit. Fixed his tie. Looked at the market like a man who had finally figured everything out. He researched. He predicted. He waited for the perfect opportunity. And then—Peter failed. |
| Metadata held | sha256 f48db6ce48e451a375075ab1530c7918ca733af8e4bc862a64fd0e4dc732cb8d · 481 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 d6be3ae6f8ddf8b7bcfbd96cfc29858d8debceda1d9e45d8e01bd25d221f329b · 495,514 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 18:55 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.