JACOB
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 1.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-22 03:18 UTC |
| Creator | 2ndvEZ8ayfkVypHaps7VgzduZPNA7WATqnnEmuXcVwpQ |
| Creator took | 10.5% of supply in the first block |
| Outside buyers | 413 distinct wallets, not counting the creator, bought on the bonding curve: 83 within the first 30s, 3 bundled into the creation block. |
| Graduated | 6 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 | 3fCsV7uYzTcX1bTRGM1oky… slot 449,254,895
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-22 03:18:03 UTC Slot 449,254,895, 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 | 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-22 03:23:34 UTC +5m 31s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-22 03:23:34 UTC +5m 31s
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 | No other launch we hold a picture for used this one. |
| This ticker | On 100 launches from 63 creator wallets, including this one. See them → |
Pool
| Liquidity | 1.3 SOL |
| Read from chain | 2026-09-22 18:49 UTC, just now |
What this launch claimed to be
| Name | Jacob The Trencher |
| Description | Jacob The Trenchor |
| Metadata held | sha256 2a8f871c031b3a938ef95ceebca61442cb2a2386928e77544bb1f8428b470ad0 · 344 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 1ed45fedf0162cc8caa7d34f655c49ba2cb7dbda86b85d220f07468e08d4ddcf · 105,600 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-22 03:18 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.