POOPYBOT
Also recorded, and not part of the finding above: this picture is on 2 other launches. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts. They are listed under Seen before, further down this page.
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.
At launch
| Created | 2026-10-02 21:36 UTC |
| Creator | 9Lw7NpaHcjbqBXwHdXyPdqZsSdcbYgFo86H2MMuQRJBd |
| Creator took | 19.9% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | in the same batch of events as the 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 recorded - this venue's trades do not name the wallet |
| Recorded from | 2jCcfnPk8MdiPKi61JpsNj… slot 452,733,007
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
Keep this launch as a document
A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.
No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.
Order of events
| Created | 2026-10-02 21:36:39 UTC Slot 452,733,007, which is the chain's own clock for this moment. |
| Curve completed | 2026-10-02 21:36:39 UTC Confirmed against the venue's own completion state. |
Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.
Seen before
| This picture | On 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 116 launches from 90 creator wallets, including this one. See them → |
| This document | Byte-identical to 2 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 3 creator wallets. See the linked wallets → |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | Poopy Bot |
| Metadata held | sha256 88a807a58eb99f4107e5acb5d1cdda7a0d6fa83612a0f64a6313c7964bf10eb7 · 496 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 3693cc16fdde016b7b8ba8628fe61eb7b11d919aa93e0fe1c1fe59d28c321086 · 17,873 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 21:38 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.