SIF
The curve completed 2s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
findingIt left the curve 2s after launch.
noteOnly 0.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 21:11 UTC |
| Creator | 8of5gGQizsF8ATbz3ySxb4dWmzXBRJdcM5aCDzQYY4uE |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 26 distinct wallets, not counting the creator, bought on the bonding curve: 26 within the first 30s, 17 bundled into the creation block. |
| Graduated | 0 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 | 4NRVCJjV5FsawjgpiH1EHY… slot 451,758,933
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 21:11:46 UTC Slot 451,758,933, which is the chain's own clock for this moment. |
| Creation block | 17 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-29 21:11:48 UTC +2s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 21:11:48 UTC +2s
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. |
| Thirty seconds in | 26 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. |
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 40 launches from 28 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 122 launches from 86 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 1 earlier launch, 1 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 5 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 | 0.9 SOL |
| Read from chain | 2026-10-01 03:47 UTC, just now |
What this launch claimed to be
| Name | Super Intelligent factory |
| Metadata held | sha256 9856b4bf910fb7a1fb8a077fa45c82f0a18843f6ad9b08921f4e8d074743e8dc · 445 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-read | Byte-identical to the launch-time capture when re-read 2026-09-30 21:12 UTC. |
| Picture held | sha256 cf0c7266314bdc0fab1980a1c162fd59bbd4d61146f63c6541cfde099e5e7193 · 16,172 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 21:11 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.