O
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.
noteOnly 2.8 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 10:08 UTC |
| Creator | 87MCJx7RygkE7jstzp5TZUuLU6DqNswGGNpPPxZ7coJA |
| Creator took | 12.0% of supply in the first block |
| Outside buyers | 522 distinct wallets, not counting the creator, bought on the bonding curve: 61 within the first 30s, 6 bundled into the creation block. |
| Graduated | 11 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 | 4FCfQuceBmfP5eofQzmuDX… slot 451,610,509
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 10:08:43 UTC Slot 451,610,509, which is the chain's own clock for this moment. |
| Creation block | 6 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 61 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 10:20:07 UTC +11m 24s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 10:20:07 UTC +11m 24s
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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 143 launches from 73 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 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 | 2.8 SOL |
| Read from chain | 2026-09-30 17:38 UTC, just now |
What this launch claimed to be
| Name | Always On Agents |
| Description | Meet $O your always on AI team. A crypto first workspace bringing five AI agents together around one conversation. Research an idea. Write code. Plan your next move. Prepare an on-chain action. Big plans? We’re always on. Crypto never switches off. Neither should your team. Always on doesn’t mean out of your hands. You set the direction, review what matters, and stay in control. Your ideas don’t keep office hours. Your team shouldn’t either. |
| Metadata held | sha256 72844bd1dbb6939c5e7365b53b2baf0655bb148d15d3323c6e532986f123486e · 765 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 10:10 UTC. |
| Picture held | sha256 667ef488f21f17afd347833970f5028906504ab7a98f3b9eacf8358e37cb38a1 · 434,996 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 10:08 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.