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 · Yearn Finance
- Sequence
- #3
- Score
- 32 → 20 (-12)
- Cluster
- mainnet-beta
- Slot
- 426278692
- Off-chain at
- 2026-06-13T21:16:32.369Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GyVEEYp58VGrnLCCJSukUfheTYQ4dGCEAQrFUcVzejTr
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1299 chars)
{"actor":"judge","decided_at":"2026-06-13T21:16:32.154Z","decision":"review_revise","investigation_id":"4d531127-e978-430c-8f36-6eac186ef860","new_score":20,"page_slug":"yearn-finance","prev_score":32,"reason":"Ten of eighteen claims are confirmed and the core narrative — multiple exploits between 2021 and 2025, aggregate losses exceeding $20 million, and the founder's SEC-pressured departure — is well supported by Tier 1 and Tier 2 sources. However, claim_findings[9] identifies a phantom timeline entry dated February 13, 2021, describing a Yearn iearn vault exploit that no independent source confirms on that date; the reviewer concludes this event was either fabricated or conflates the December 2025 TUSD vault hack. claim_findings[10] places the Alpha Homora exploit on February 27, 2021, while multiple reputable sources consistently date it to February 13, 2021 — a two-week material date error. Two high-priority structural gaps further reduce reliability: all nine page sections contain empty content fields (coverage_gaps[0]) and source URLs are stored in the wrong database column (coverage_gaps[1]), making citation context unverifiable.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}