BP
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.
noteOnly 2.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 01:07 UTC |
| Creator | FUJRgtzjYzQcayhoJoiFoqMsKW9uReVF18DRJiH47H1 |
| Creator took | 1.5% of supply in the first block |
| Outside buyers | 10 distinct wallets, not counting the creator, bought on the bonding curve: 8 within the first 30s, 2 bundled into the creation block. |
| Graduated | 14 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 while we watched |
| Recorded from | sRBB13qgr6h9maxYiEuz2Q… slot 451,811,709
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 01:07:35 UTC Slot 451,811,709, which is the chain's own clock for this moment. |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 8 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-09-30 01:21:28 UTC +13m 53s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 01:21:41 UTC +14m 06s
6.425e-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 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 303 launches from 248 creator wallets, including this one. See them → |
Pool
| Liquidity | 2.9 SOL |
| Read from chain | 2026-10-01 15:40 UTC, just now |
What this launch claimed to be
| Name | Baddest Potato |
| Description | Baddest Potato |
| Metadata held | sha256 4870e67c7808221e2d82651cdbb5ce4b0af2e670c69ee154e1f5d54bd94245f8 · 210 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-10-01 01:09 UTC. |
| Picture held | sha256 50ef3f6ae009bcd84938b2bc62a97fd13a71b1bf508126adc60a6bacc577680b · 285,362 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 01:07 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.