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
- #6
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 457823801
- Off-chain at
- 2026-10-16T23:40:01.067Z
- Anchored at
- 2026-10-16T23:40:20.208Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 86Jm3jrsA5nRNE4HtzpojvSG1ntReYfyh4gTTh7GfPM6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1969 chars)
{"actor":"reviewer","artifact_identity":"bf6ce13081e005680350a3f9ab06d4f1","decided_at":"2026-10-16T23:40:00.924Z","decision":"review","disputed_pct":0.2,"findings_hash":"BFUMmL8gLkyKT4fodBY6awDTN2mYeBsDUtEpY1u6zoVG","investigation_id":"4d531127-e978-430c-8f36-6eac186ef860","mode":"findings_only","new_score":58,"page_content_hash":"594d217734c015647c78919f945ada8a45a2910e4caac52fadc6ac99599589e0","page_slug":"yearn-finance","prev_score":58,"reason":"The page is largely well-sourced: the dollar figures, dates, and technical mechanisms for the February 2021 yDAI exploit, the October 2021 Cream Finance hack, the Iron Bank/Alpha Homora bad-debt dispute, the December 2023 treasury script error, and the November-December 2025 yETH and TUSD exploits all independently check out against primary and reputable secondary sources I fetched directly. The founder-departure/SEC narrative and the February 2021 governance vote are also confirmed. However, the page contains one clear fabricated/conflated claim: a 'second, smaller exploit of a legacy iearn vault' said to have occurred in February 2021 (in both a section and the timeline) is not supported by any source -- the cited thedefiant.io URL is actually reporting the December 2025 TUSD exploit, which the page already covers correctly elsewhere. Relatedly, the timeline's Alpha Homora exploit date (February 27, 2021) is wrong; the real date is February 13, 2021 -- the same date wrongly attached to the fabricated 'second exploit' entry, suggesting the two dates were swapped during drafting. One citation (docs.yearn.finance) is dead due to a domain migration to docs.yearn.fi, though the underlying claim it supports is independently true. The TVL figure ('$6 billion peak') could not be confirmed to that precision. No community submissions were available to review.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}