Launch record · observed at creation 2026-11-04 00:44 UTC

PUP

PredictingUncertainPossibilities

BJETZv725tW33siYKfWQDt5xQbPzdk6mZ6HjkzrjqMFp Copy Solscan

What this launch shares with other launches

Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.

Its own first blocks

Also recorded, and not part of the finding above: this picture is on 3 other launches from 2 creator wallets in all, and this creator has 34 other launches on record. 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, 56.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.

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.

not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.

At launch

Created	2026-11-04 00:44 UTC
Creator	9CZYtpG9NBQJd2nMneHTAb9wJJSxH1gkX6hbBrGDWSXk
Creator took	0.0% of supply in the first block
Outside buyers	unknown 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.
Graduated	1 min after launch
Curve 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	2FSBDUAhoTUMPYbwrabm5u… slot 465,104,746 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. peak_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.

Order of events

Created	2026-11-04 00:44:24 UTC Slot 465,104,746, which is the chain's own clock for this moment.
Curve completed	2026-11-04 00:45:29 UTC +1m 05s Confirmed against the venue's own completion state.

Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.

Seen before

This picture	On 4 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.5% of the launches whose picture we hold carry one a different creator also used. See them →
This ticker	On 647 launches from 518 creator wallets, including this one. See this ticker's page →
This document	The same launch document, byte for byte, as 3 other launches, across 2 creator wallets in all. Across the archive, 33.4% of the launches whose document we hold carry one byte-identical to a different creator's. See them →
This creator	34 earlier launches, 34 confirmed complete on chain. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other wallets	Launches by this creator were made with files byte-identical to those of 7 other creator wallets, across 14 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.7% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

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	PredictingUncertainPossibilities
Metadata held	sha256 9ba617342c4c6769d93930c6880f9cf949c9806b664dd4ba3fad47f4264abe3a · 506 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 12183d4ac70702fdac13d299ae2f72b40e182a227e0757abb278d8fb093a10ee · 4,362 bytes

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