Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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
View on Solana ↗
Sequence
#7
Score
58 → 58 (0)
Cluster
mainnet-beta
Slot
457826892
Off-chain at
2026-10-16T23:51:02.432Z
Anchored at
2026-10-16T23:51:27.424Z
Block time
—

Independent verification

1. Database (off-chain)
BXyrCT4eL7mrM1rPfWjPwRP7VJEDpXViFnuyjHdq22Cg
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1880 chars)
{"actor":"reviewer","artifact_identity":"5838ece2bebfa36e33018252da681316","decided_at":"2026-10-16T23:51:01.806Z","decision":"review","disputed_pct":0.25,"findings_hash":"EKL5xJ1cFpPx5P2KKy35KRSgN6iDx985gPtFFYXyuHVG","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 large majority of this page's specific, checkable claims -- exploit dollar amounts, dates, technical mechanisms (Feb 2021 yDAI, Oct 2021 Cream, Iron Bank/Alpha Homora, Dec 2023 treasury script, Nov/Dec 2025 yETH and TUSD exploits), the SEC-departure narrative, and the governance vote -- are well corroborated by multiple independent, credible sources and are accurately characterized, including appropriate hedging where facts rest on self-reported claims. However, one clause (and its matching timeline entry) describing 'a second, smaller exploit of a legacy iearn vault' in February 2021 is not supported by any contemporaneous 2021 reporting; the cited source for it is actually a December 2025 article describing the real TUSD vault hack already documented elsewhere on the page. This looks like a citation mix-up that invented a duplicate 2021 event and should be removed. The $6 billion 2021 TVL-peak figure could not be confirmed against the figures available (best documented figures cluster around $4-5B) and is left as unverifiable. The Protocol Overview section's citations (gemini.com, messari.io) do not actually support several of its specific claims (6-of-9 multisig, ecosystem alliances), though those claims are independently true and better-sourced elsewhere.","score_delta":0,"sequence_num":7,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}