AGENCY
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-10-02 17:26 UTC |
| Creator | 3gYoKtrpuCRC4rmpThDWJuhMDtBijT2ktyyrZpLai4sh |
| Creator took | 9.4% of supply in the first block |
| Outside buyers | 612 distinct wallets, not counting the creator, bought on the bonding curve: 72 within the first 30s, 13 bundled into the creation block. |
| Graduated | 16 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | yes |
| Recorded from | 3g2oGbTTbriM9E9rHtoveP… slot 452,677,247
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 17:26:58 UTC Slot 452,677,247, which is the chain's own clock for this moment. |
| Creation block | 13 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 72 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-02 17:43:24 UTC +16m 26s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 17:43:24 UTC +16m 26s
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 35 launches from 30 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. Together they sit in a linked group of 2 creator wallets. See the linked wallets → |
Pool
| Liquidity | 2.8 SOL |
| Read from chain | 2026-10-03 00:59 UTC, just now |
What this launch claimed to be
| Name | Meme Agency |
| Description | Welcome to Meme Agency the place where memes become real onchain businesses. There are two ways to get to work: Build your own meme agency. Launch a token and brief a team of specialized AI agents to handle the branding, website, creative, social content, analytics and launch execution for you. Join the HR Office. Discover projects you believe in, share your referral link, bring in traders and earn a share of the trading fees you generate. Whether you want to build the next breakout |
| Metadata held | sha256 69256935a8526cfd4671a508c6a81770871ba1181390d4d1d71ee9796872a87e · 903 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 f51447ab905700b57f79ecc1c9a11ec4e6c200fb74de4c66a4043ce733e96dfa · 371,217 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 17:27 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.