COVERT
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.
8zWcEgUZvQKcHgtUoYTnaC6AHX7FmtWVV9WeM4kPuXMR
Solscan
not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.
At launch
| Created | 2026-09-29 22:09 UTC |
| Creator | HXAYJj7g4Dn8bmcGDJmcH1rwS9tEbNjLWizJo2EeFx2y |
| Creator took | 5.1% of supply in the first block |
| Outside buyers | unknown distinct wallets, not counting the creator, bought on the bonding curve. |
| Graduated | 3 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 recorded - this venue's trades do not name the wallet |
| Recorded from | 4KHPW2ZHocPnymVGjvS98b… slot 451,771,894
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.
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. |
Order of events
| Created | 2026-09-29 22:09:49 UTC Slot 451,771,894, which is the chain's own clock for this moment. |
| Highest price seen | 2026-09-29 22:09:49 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. |
| Curve completed | 2026-09-29 22:13:06 UTC +3m 17s Confirmed against the venue's own completion state. |
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 6 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 10 launches from 7 creator wallets, including this one. See them → |
| This document | Byte-identical to 5 other launches' metadata document. See them → |
| This creator | 2 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, 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
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 | Covert Chameleon |
| Description | 🦎 WE ARE LIVE. $COVERT — the first ticker on XMR20, an experimental protocol that records token launches and signed token activity inside Monero transactions. Covert Chameleon has stepped out of the shadows. Blend in. Stand apart. Stay covert. 🤫 🌐 https://covertchameleon.xyz |
| Metadata held | sha256 8bd1d8f7c484661249b1c5e2be4b1b1bdd196b0abc719a4ee75d8ce967779603 · 685 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 22:10 UTC. |
| Picture held | sha256 1de3604a8c4b2ce443a02e3f37ffded04c34de76ee6e472904ff2b0b591f83c2 · 4,562 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 22:09 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.