PPPLABS
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-10-02 13:27 UTC |
| Creator | HjeEmC8WVGx6j4GDk15Bh6vuhdEtHFvBRxjYms8tgAoz |
| Creator took | 61.0% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | yes; we did not record when |
| 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 recorded - this venue's trades do not name the wallet |
| Recorded from | 5hTYQov8i9kYB61JUeJDno… slot 452,623,487
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Order of events
| Created | 2026-10-02 13:27:30 UTC Slot 452,623,487, which is the chain's own clock for this moment. |
| Highest price seen | 2026-10-02 13:27:30 UTC
8.490e-8 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. |
| Curve completed | Recorded as complete; we did not record when.
Confirmed against the venue's own completion state. |
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. |
| This ticker | On 2 launches from 2 creator wallets, including this one. See them → |
Who took the curve
One transaction bought 82 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →
That is the same transaction the token was created in: the launch and the purchase of its float are one signature.
Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.
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 | PPPump Labs |
| Description | A disruptive toolset for the degen space: trading terminal, DEX aggregator, launchpad, and more. Fees generated by each tool are automatically routed to a dedicated program on-chain that executes buybacks and burns, making the token deflationary. |
| Metadata held | sha256 15ab27bf6f1c677fb289c2aa609a1c3de901ff187a4ba53b5d97c604240918a2 · 550 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 7ffa7c9841d1d0891f9f699d18b79d5c52395db2638d5074577b4f5b44af0bbe · 1,508,502 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 13:27 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.