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_revise · Munchables
- Sequence
- #3
- Score
- 10 → 0 (-16)
- Cluster
- mainnet-beta
- Slot
- 464354197
- Off-chain at
- 2026-11-02T04:04:19.601Z
- Anchored at
- 2026-11-02T04:04:35.000Z
- Block time
- 2026-11-02T04:04:35.000Z
Independent verification
- 1. Database (off-chain)
- 7sdzfMBCLsS3dxrBMhGmJYikvCiPSBPyzUqqtAKKGLDM
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1882 chars)
{"actor":"judge","artifact_identity":"2afd8958730620427beb2e48cae2eb2c","band_override":null,"decided_at":"2026-11-02T04:04:19.350Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"5d7315a6-ce77-4a91-8b18-103e04faad57","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"munchables","prev_score":10,"reason":"The core account of the $62.5M exploit, the rogue developer, the proxy backdoor, the key surrender about 11 minutes after ZachXBT's post and the $97M multisig held up (claim_findings[0], [5], [6], [7]). Two claims could not be verified (the shared deposit addresses and the $6,220 MEXC figure, claim_findings[2] and [4]). The 'full sum recovered' wording conflicts with sources citing about $60.5M returned (claim_findings[1]). The page also does not mention the October 2026 shutdown of the Blast network, which the review rates a material omission (omission_findings[0]), and the project's current status is unknown. For these reasons the page is revised and placed under investigation, with a moderate penalty because the reviewer's confidence is moderate and no claim was directly contradicted.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-16,"sequence_num":3,"severity_override":{"applied":true,"band":"significant","from_band":"minor","reason":"The percentage (2 of 9 claims unverifiable, about 22%) implies the minor band. The review reports a material omission: the host chain Blast announced its shutdown in October 2026, and the page's relaunch statement implies the project may still be viable. A high-priority gap on current project status is also open. The band is raised to significant."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}