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 · Maya Protocol
- Sequence
- #12
- Score
- 51 → 51 (0)
- Cluster
- mainnet-beta
- Slot
- 464855261
- Off-chain at
- 2026-11-03T09:52:29.600Z
- Anchored at
- 2026-11-03T09:52:40.000Z
- Block time
- 2026-11-03T09:52:40.000Z
Independent verification
- 1. Database (off-chain)
- 3cLQCiypTUyvLR2TXfqHyViVb4WcX9r2LS2VFFEV5FNR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2504 chars)
{"actor":"judge","artifact_identity":"00a960e91b5785bff3d599c6642e7cc8","band_override":{"actual_delta":-5,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"None of the nine reviewed claims were disputed or unverifiable (0%), and the core exploit facts (date, $1.7M direct loss, 88.7% CACAO drop, $200,000 pledge) match Cointelegraph and Decrypt (claim_findings[0-2], [4-5]). Three claims were only partly supported: the 'minting' wording for the 48.87M CACAO (claim_findings[3]), the exact quote and 'Fable 5' auditor name (claim_findings[6]), and the THORChain halt length, which sources put nearer six weeks than five (claim_findings[7]). A high-priority gap remains because nothing after August 21, 2026 was found on restart, patch or compensation, so the page's status may be stale, although the page says this openly. The one omission, the compensation-mechanism root cause, is minor, and the subject status does not contradict the page, so a small penalty and a minor-issues banner apply instead of approval."},"decided_at":"2026-11-03T09:52:29.299Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":51,"page_slug":"maya-protocol","prev_score":51,"reason":"None of the nine reviewed claims were disputed or unverifiable (0%), and the core exploit facts (date, $1.7M direct loss, 88.7% CACAO drop, $200,000 pledge) match Cointelegraph and Decrypt (claim_findings[0-2], [4-5]). Three claims were only partly supported: the 'minting' wording for the 48.87M CACAO (claim_findings[3]), the exact quote and 'Fable 5' auditor name (claim_findings[6]), and the THORChain halt length, which sources put nearer six weeks than five (claim_findings[7]). A high-priority gap remains because nothing after August 21, 2026 was found on restart, patch or compensation, so the page's status may be stale, although the page says this openly. The one omission, the compensation-mechanism root cause, is minor, and the subject status does not contradict the page, so a small penalty and a minor-issues banner apply instead of approval.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":12,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}