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 · Yearn Finance
- Sequence
- #2
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 426278688
- Off-chain at
- 2026-06-13T21:16:32.279Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- DKGkbx7j4HR7gWdwrjQyCUdcRBYpRDnK3B1YA6Tk3etE
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1146 chars)
{"actor":"reviewer","decided_at":"2026-06-13T21:16:32.154Z","decision":"review","investigation_id":"4d531127-e978-430c-8f36-6eac186ef860","new_score":32,"page_slug":"yearn-finance","prev_score":32,"reason":"The page's core narrative — that Yearn Finance suffered multiple security exploits between 2021 and 2025 and that its founder departed due to SEC pressure — is well supported by reputable independent sources. However, two material errors undermine reliability: the Alpha Homora exploit date is wrong by two weeks (page says February 27, 2021; confirmed date is February 13, 2021), and the February 13, 2021 timeline entry claiming a second Yearn iearn vault exploit appears to conflate a December 2025 event with 2021, introducing a phantom timeline entry. The 'four exploits' count and '>$20M aggregate losses' figures require careful qualification as vault-level losses rather than attacker profits. All nine page sections are structurally empty, limiting the review to the summary and timeline.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}