VeilPay
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 4.4 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 03:46 UTC |
| Creator | CpgYVsW5W4C5wEbHJwWBBVoqFrYDVsHVN9dDw6ek3UDZ |
| Creator took | 1.7% of supply in the first block |
| Outside buyers | 898 distinct wallets, not counting the creator, bought on the bonding curve: 14 within the first 30s, 3 bundled into the creation block. |
| Graduated | 4.3 h 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 | 3fBCeh16DX6U8w29FpnJ2n… slot 451,847,341
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 03:46:11 UTC Slot 451,847,341, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 14 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 08:02:01 UTC +4h 15m 50s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 08:02:01 UTC +4h 15m 50s
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 2 launches from 2 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 4.4 SOL |
| Read from chain | 2026-10-01 21:27 UTC, just now |
What this launch claimed to be
| Name | VeilPay |
| Description | VeilPay is designed around a simple idea: your payment information shouldn't need to be exposed more than necessary. |
| Metadata held | sha256 240d3d86a8f41d0a0a12f41b2d245d27257781e09a0a8060543475206b65fca9 · 479 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 03:47 UTC. |
| Picture held | sha256 739b33aa70a5341eb0a0504ff82550bfcce568315d3c20e8dd3dd44950875ecb · 60,054 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 03:46 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.