Verify a decision
Every moderation decision on AVOID.NET is anchored to the Solana blockchain. You don't have to trust us — you can verify cryptographically that we committed to a verdict at a specific moment and have not rewritten it.
How verification works
- We commit. When a moderator accepts/rejects a submission, we serialize the decision into deterministic UTF-8 bytes (
payload_canonical_string), hash it with SHA-256, encode the digest as base58, and write it to Solana inside an SPL Memo v2 transaction. - We store the bytes. The exact bytes we hashed are stored alongside the decision in our database. Anyone can read them and recompute the hash in any language.
- You compare three values. Database hash, your independently-recomputed hash, and the hash inside the on-chain memo. If all three match, the decision is authentic and timestamped.
The on-chain memo format is
AVOID.NET|v1|h:<b58-sha256>|d:<id>|t:<iso>Find a signature on any investigation page's decision log, or run python -m src.verify_decision --signature <sig> for a CLI check.
Decision
review · Munchables
- Sequence
- #2
- Score
- 10 → 10 (0)
- Cluster
- mainnet-beta
- Slot
- 464354191
- Off-chain at
- 2026-11-02T04:04:19.415Z
- Anchored at
- 2026-11-02T04:04:34.000Z
- Block time
- 2026-11-02T04:04:34.000Z
Independent verification
- 1. Database (off-chain)
- 4yJRT9tUbeuQzNx9TGE9bi5kB1Y5N8hVRNr8sPME83CN
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1303 chars)
{"actor":"reviewer","artifact_identity":"2afd8958730620427beb2e48cae2eb2c","decided_at":"2026-11-02T04:04:19.350Z","decision":"review","disputed_pct":0.2222,"findings_hash":"CAtFh588tnEx7DEUcGCcwhBbxCJKDYUfjDpfMtnBF1QG","investigation_id":"5d7315a6-ce77-4a91-8b18-103e04faad57","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":10,"omissions":{"material":1,"total":1},"page_content_hash":"f231bf6e37ff949ea598a81a987ae807393e6ac9641442c3ead72d976be689bd","page_slug":"munchables","prev_score":10,"reason":"The core narrative holds: $62.5M exploit, rogue developer, proxy and storage-slot backdoor, key surrender about 11 minutes after ZachXBT's post, and the $97M multisig. The $6,220 MEXC figure, the 'sketchy' quote, the shared deposit addresses and the 24-hour recovery window could not be verified. The 'full sum recovered' wording sits uneasily with sources citing about $60.5M returned. The page omits the Blast network shutdown announced in October 2026.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}