OCTO
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.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 20:25 UTC |
| Creator | 224JYHt2RzHanBFLaoYpAspMr2sJSwxjg4FoNTDZ4KCC |
| Creator took | 8.0% of supply in the first block |
| Outside buyers | 19 distinct wallets, not counting the creator, bought on the bonding curve: 19 within the first 30s, 10 bundled into the creation block. |
| Graduated | 2 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 | iC6gbTmEk1UV2PGxGYVQKx… slot 452,394,286
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 20:25:20 UTC Slot 452,394,286, which is the chain's own clock for this moment. |
| Creation block | 10 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-10-01 20:25:20 UTC
0.000e+0 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 | 19 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-10-01 20:27:31 UTC +2m 12s 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 picture | No other launch we hold a picture for used this one. |
| This ticker | On 29 launches from 25 creator wallets, including this one. See them → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 23:42 UTC, just now |
What this launch claimed to be
| Name | Octo Protocol |
| Metadata held | sha256 fb544c1f25387f4175f5f168a115189188fa5b0a024671b0c024dca0457eca55 · 195 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 ae5a285e0452b3442e8564af7db9853b9f6ed7b0eeb89b4e4a0265e04ec6bbeb · 189,009 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 20:25 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.