MEMO
Checked, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
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 1.1 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 12:43 UTC |
| Creator | BdL6XPHViUwyC92uonnDJagJkMuUZqXfK8YhcQSj9rg9 |
| Creator took | 2.7% of supply in the first block |
| Outside buyers | 769 distinct wallets, not counting the creator, bought on the bonding curve: 169 within the first 30s, 7 bundled into the creation block. |
| Graduated | 8 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 | 5kNCA7GkPqmmLB1RRPJkyv… slot 451,645,361
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 12:43:56 UTC Slot 451,645,361, which is the chain's own clock for this moment. |
| Creation block | 7 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 169 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 12:52:04 UTC +8m 08s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 12:52:04 UTC +8m 08s
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 11 launches from 11 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 27 launches from 26 creator wallets, including this one. See them → |
| This document | Byte-identical to 9 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 10 other creator wallets, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 11 creator wallets. See the linked wallets → |
Pool
| Liquidity | 1.1 SOL |
| Read from chain | 2026-09-30 19:31 UTC, just now |
What this launch claimed to be
| Name | MemOffice |
| Metadata held | sha256 2f013a0e8c5915f7d87d46fda571dfe7111eba72a7fe281bad0efef2e6bbf535 · 189 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 12:44 UTC. |
| Picture held | sha256 a5f0bbd1cdbb53f70bfa3bdbe4edf5d26971e5c49c6f774346be8d07cf9862d7 · 263,710 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 12:43 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.