K/acc
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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.
noteThe creator sold while we were watching.
At launch
| Created | 2026-09-29 07:46 UTC |
| Creator | FciWQ5qfCFcdtqRUh9kvzbWr1WfuXAJgzh6FrmRxxVLz |
| Creator took | 15.3% of supply in the first block |
| Outside buyers | 638 distinct wallets, not counting the creator, bought on the bonding curve: 183 within the first 30s, 4 bundled into the creation block. |
| Graduated | 4 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 | yes |
| Recorded from | 42MJacWd3KrmSyif67XTKn… slot 451,578,404
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 07:46:09 UTC Slot 451,578,404, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 183 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-29 07:50:25 UTC +4m 16s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 07:50:25 UTC +4m 16s
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 15 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 33 launches from 20 creator wallets, including this one. See them → |
| This creator | 238 earlier launches, 7 confirmed graduated on chain, 1 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 125 other creator wallets, across 166 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 | 75.3 SOL |
| Read from chain | 2026-09-29 13:22 UTC, just now |
What this launch claimed to be
| Name | Knowledge accelerationism |
| Description | Fees to @beffjezos via UsePaid |
| Metadata held | sha256 3b1d21d1f974ae18ed1fb65222edd3af5231764e302e6cd699c3bbabdf167bff · 470 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 4c9e1806b28868d090d8b9fec6d4feadbcba9bee54c617cbbc282fb613140b9c · 115,391 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 07:46 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.