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_approve · Yearn Ether
- Sequence
- #5
- Score
- 28 → 58 (+30)
- Cluster
- mainnet-beta
- Slot
- 426514266
- Off-chain at
- 2026-06-14T23:15:47.076Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- CoTnQxNHzVagYtHz1G5LbLRD88NNqoNT23XVC9iToEZf
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1500 chars)
{"actor":"judge","decided_at":"2026-06-14T23:15:46.966Z","decision":"review_approve","investigation_id":"5ba41826-a316-4076-b123-f3b41fc76057","new_score":58,"page_slug":"yearn-ether","prev_score":28,"reason":"This was a severity-calibration review, not a fact-dispute review. The reviewer found zero disputed claims across all six claim_findings — every factual assertion on the page is supported, including the fair-launch founding (claim_findings[0]), the external-attacker attribution for all four loss events (claim_findings[1], claim_findings[4]), the active remediation via YIP-90 and post-mortems (claim_findings[2]), and the confirmed absence of regulatory sanctions with $151M active TVL (claim_findings[5]). The page's own language frames Yearn as a victim of third-party exploits, which directly contradicts the WARNING band (score 28) it currently holds — WARNING implies elevated fraud risk or an unresolved severe incident, neither of which applies here. The reviewer's recommended score of 58 (CAUTIONARY band) correctly signals a meaningful security history and approximately $6.6M in unrecovered losses from the 2025 yETH exploit, while distinguishing hack-victim attribution from fraud. A positive delta of +30 moves the score from 28 to 58, aligning published severity with verified facts. The page is accurate and must remain published.","score_delta":30,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}