DPAID
Checked, 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 5.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 17:54 UTC |
| Creator | 8U3E54LqY68hCm5m4hvW1JqWSttZPmWLww5CRcqvR1pQ |
| Creator took | 0.7% of supply in the first block |
| Outside buyers | 800 distinct wallets, not counting the creator, bought on the bonding curve: 83 within the first 30s, 5 bundled into the creation block. |
| Graduated | 10 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 | 5sJCNTbtejFKkZ6Us1FX8p… slot 451,714,818
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 17:54:42 UTC Slot 451,714,818, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 83 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-29 18:04:58 UTC +10m 16s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 18:04:58 UTC +10m 16s
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 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 21 launches from 14 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 1 earlier launch, 1 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 | 5.5 SOL |
| Read from chain | 2026-10-01 06:53 UTC, just now |
What this launch claimed to be
| Name | DiscordPaid |
| Metadata held | sha256 2abc76fbf1f66a4b0773a0a4b5eb94654e3e8fd2111ef1969c32edc58b1c0167 · 326 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-09-30 17:56 UTC. |
| Picture held | sha256 f49b3913af08109b32ef3c7163845a0dfcb70e7abf1a992485ba446fd97d207b · 10,579 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 17:54 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.