1,754,585 launches on record
Coverage from 2 Sep 2026
Archive read 15:42 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

Jef

Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record - a marker being one of the launch-record tests below that fired - and 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.

Also recorded, and not part of the finding above: this picture is on 42 other launches from 32 creator wallets in all. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 48.5% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

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.

88jUcA4vvbiyXxhhnk6RHyxuGaHhR7NQnfVwd6hBpump Solscan pump.fun

Cite this record as: Chain of Title, Jef (General Jef), mint 88jUcA4vvbiyXxhhnk6RHyxuGaHhR7NQnfVwd6hBpump, observed at creation 2026-10-10 09:19 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/88jUcA4vvbiyXxhhnk6RHyxuGaHhR7NQnfVwd6hBpump

Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.

noteOnly 21.9 SOL of liquidity was in the pool just now.

At launch

Created2026-10-10 09:19 UTC
CreatorCNi16J5Wyq8THtJGCRAS9FMPht9z7NkZJmhe6kjRD1nB
Creator took9.8% of supply in the first block
Outside buyers1,317 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 103 within the first 30s, 5 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduated22 min after launch
Curve on chainNot re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers.
Creator soldnot while we watched
Recorded fromucBsuyapizQstWKkZJZkzU… slot 455,203,373
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Order of events

Created2026-10-10 09:19:09 UTC
Slot 455,203,373, which is the chain's own clock for this moment.
Creation block5 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in103 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 completed2026-10-10 09:41:37 UTC +22m 27s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-10 09:41:37 UTC +22m 27s
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 pictureOn 43 launches from 32 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 48.5% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 133 launches from 105 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 87% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 2 other launches, across 3 creator wallets in all. Across the archive, 25.3% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

Pool

Liquidity21.9 SOL
Read from chain2026-10-11 17:40 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameGeneral Jef
DescriptionDeployed using https://j7tracker.io
Metadata heldsha256 0b429b69d8fbcb315db0557d9ceb408abe7eb9d1d46d946042c4035168da34c7 · 482 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-readByte-identical to the launch-time capture when re-read 2026-10-11 14:11 UTC.
Picture heldsha256 4b67ed3daad6ca55e3a6429818f7f31722e3b72564658e111126efee4c0659dc · 26,254 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-10-10 09:19 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another