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
- #3
- Score
- 28 → 28 (0)
- Cluster
- mainnet-beta
- Slot
- 426270696
- Off-chain at
- 2026-06-13T20:23:28.089Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 316QN1H6WWGA85eofxBZpjh48r29kjLgohkFujhXzAHR
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1189 chars)
{"actor":"judge","decided_at":"2026-06-13T20:23:27.945Z","decision":"review_approve","investigation_id":"5ba41826-a316-4076-b123-f3b41fc76057","new_score":28,"page_slug":"yearn-ether","prev_score":28,"reason":"No claims were outright disputed across 14 checked findings. Four claims are partially_supported rather than confirmed, but each involves a precision issue rather than a contested allegation: claim_findings[1] involves competing technical framings of the same vulnerability root cause; claim_findings[3] hinges on how 'major incident' is counted; claim_findings[7] overstates Tornado Cash involvement for 2023 yUSDT funds; and claim_findings[5] conflates the July 2020 YFI token launch date with the February 2020 protocol launch. None of these undermine the page's core factual record of the November 2025 exploit, its financial impact, or the recovery timeline. The high-priority coverage gap noting empty section content is a structural expansion item, not a factual accuracy problem, and does not affect approval under review policy.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}