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 · Maya Protocol
- Sequence
- #5
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 457421939
- Off-chain at
- 2026-10-15T23:32:06.598Z
- Anchored at
- 2026-10-15T23:32:29.624Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- H2rjsFMLBd4dxFJ2fHgVsFZfJBco2qBJEJweXpJsNMq5
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1848 chars)
{"actor":"reviewer","artifact_identity":"23f7c9780212de40adb76e1b75847811","decided_at":"2026-10-15T23:32:06.133Z","decision":"review","disputed_pct":0.36,"findings_hash":"2A8RJzRRaXuAEafuQaL5YCYSp6RnoHcNhcCnQbDJPE98","investigation_id":"e892733a-1f37-4939-86a7-e4a859bbf6b0","mode":"findings_only","new_score":28,"page_content_hash":"6e31615e26248326f918cd1214a5828d65a3d250ed9cdb9e5ac4094544efa58f","page_slug":"maya-protocol","prev_score":28,"reason":"The page's core narrative of the August 18, 2026 Maya Protocol exploit is well supported by multiple independent tier-1 and tier-2 sources (Decrypt, CoinDesk, Defimon, CoinPaprika), with figures for the CACAO inflation, BTC extraction, price collapse, and TVL impact confirmed to a high degree of precision. However, two defects stand out: (1) the page's claim that no team-authored post-mortem existed and that technical breakdowns came only from external analyst Defimon is directly contradicted by Decrypt, one of the page's own cited sources, which describes a team-published post-mortem report — this error is repeated in both the summary and the Team Response section; (2) the THORChain '$15 million across two exploits in July 2021' figure is not supported by any cited source and is inconsistent with contemporaneous reporting that consistently totals closer to $13 million, also repeated in two sections. Additionally, the specific 'April 20, 2023' trading launch date could not be verified against the cited source, which mentions only 'March 2023,' and a cited THORChain report URL has permanently redirected to a new domain. The 38-validator count and the Halborn 'Draft 3' audit label claim could not be independently verified either way.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}