2,355,618 launches on record
Coverage from 2 Sep 2026
Archive read 24 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

Bear

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.

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.

74HTvZ5vYS9MSpfHc84c7W6v5nMTUXdTToXj4LP1pump Solscan pump.fun

Cite this record as: Chain of Title, Bear (Justice for Bear), mint 74HTvZ5vYS9MSpfHc84c7W6v5nMTUXdTToXj4LP1pump, observed at creation 2026-10-24 21:27 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/74HTvZ5vYS9MSpfHc84c7W6v5nMTUXdTToXj4LP1pump

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 2.2 SOL of liquidity was in the pool just now.

At launch

Created2026-10-24 21:27 UTC
CreatorF6h9x5p6eJvTPx8AKpVKGWBVza7RFWbCGUAL6PqDRTib
Creator took2.9% of supply in the first block
Outside buyers486 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: 1 within the first 30s, 0 in the very same block the token was created in.
Graduated27 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 from2Qz5qyvVyCHQwoVEQ5ix8H… slot 461,002,660
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedpeak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
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.

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.

Several launches in one matter

A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.

Order of events

Created2026-10-24 21:27:04 UTC
Slot 461,002,660, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in1 distinct buyer, 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-24 21:53:42 UTC +26m 38s
Confirmed: a PumpSwap pool was found for it.

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 tickerOn 844 launches from 622 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, 88.2% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 30.2% of the launches whose document we hold carry one byte-identical to a different creator's. See them →

Pool

Liquidity2.2 SOL
Read from chain2026-10-25 01:07 UTC, just now

What this launch claimed to be

NameJustice for Bear
Metadata heldsha256 4026206d1c85b489c39be450a362a0dba4e7ef0ac8b4be857739b6f6b982ba3f · 381 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.
PictureNot captured, so we cannot show what it published. That is our storage budget, not a finding about the launch.

Off-chain and mutable. This is what the launch served when we read it at 2026-10-24 21:28 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