A coin marked Verified at launch was launched by a wallet that had already proved it owns the brand. The proof is public, so you never have to trust this page.
The handle, domain or org must equal the coin's key exactly. An account called pepe2 cannot claim PEPE. The label says what held at launch, and nothing rechecks it later, since a domain can lapse and a handle can be sold.
Prove the handle, domain or org is yours, then launch on its key.
The code is a hash of the key, the claimant and the time, worked out with no server, so it cannot be copied to another wallet or reused later. This is the code for the key PEPE, claimed by 7xKX…gAsU:
mono-j65wdgmkjbyg5t7hfuuidahyau
@pepe Claiming PEPE on mono: mono-j65wdgmkjbyg5t7hfuuidahyau
The handle equals the key. Account at least 90 days old, with at least 1,000 followers.
_mono.pepe.lol TXT "mono-verify=mono-j65wdgmkjbyg5t7hfuuidahyau"
The first label of the domain equals the key. Registered at least 90 days ago.
github.com/pepe/site .well-known/mono.txt mono-j65wdgmkjbyg5t7hfuuidahyau
The org name equals the key. Public repo, not a fork. Org at least 90 days old.
Every notice and attestation from all verifiers, newest first. Entries are only ever added. The line under each one is the time its claim has left.
No attestations yet.
The latest signed head of each log. Two heads at one entry would prove a rewrite, and this page would say so.
No heads seen yet.
This walks the hash chain of every log, checks each signature against the program, and compares heads across verifiers.
MONO_PROGRAM_ID=4HXTWsXDtzoP6JhrSGDwzLTa2UYQw5nySq4eoVQh1Kzo RPC_URL=<a node you trust> pnpm --filter @mono/verifier verify-log https://public-production-e81bc944.up.railway.app/verifier-0 https://public-production-e81bc944.up.railway.app/verifier-1 https://public-production-e81bc944.up.railway.app/verifier-2
Run it from the mono source, in services/verifier. Without RPC_URL it skips the checks against the chain.