PIPPAID
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.
At launch
| Created | 2026-09-18 18:21 UTC |
| Creator | CjHwEmePH4ucpKRGakJWyy5qWm7oPYtU7bCd7CvCXDpj |
| Creator took | 3.1% of supply in the first block |
| Outside buyers | 5 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 5 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 1.2 days ago and it was finished. Checked 2026-09-18 18:30 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4E2ANR8aYP9TSL67xwRdGp… slot 448,162,736
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-18 18:21:03 UTC Slot 448,162,736, 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. |
| Curve completed | 2026-09-18 18:21:03 UTC +0s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-18 18:21:03 UTC +0s
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. |
| Thirty seconds in | 5 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. |
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 | No other launch we hold a picture for used this one. |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | Pippaid |
| Description | Nobody knows what Pippaid is. Nobody knows why it exists. It just showed up, looked weird, and became a coin. |
| Metadata held | sha256 8dccbf4b6ea6540e4fe9529e29dcc10a0b6ca1ffb36fcef750ae390292969626 · 422 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-19 18:21 UTC. |
| Picture held | sha256 becc2ce743895791658c2860eb6309a65ed723a7f65e3aa1a6ffdcc8980cdb57 · 219,613 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-18 18:21 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.