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 · Curve LlamaLend
View on Solana ↗
Sequence
#5
Score
40 → 40 (0)
Cluster
mainnet-beta
Slot
457812918
Off-chain at
2026-10-16T23:00:40.839Z
Anchored at
2026-10-16T23:01:04.745Z
Block time
—

Independent verification

1. Database (off-chain)
8yC9XMhJjy58KAKqgZ1T1gjDLz8wrEzSLqQnVoriU2kC
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2208 chars)
{"actor":"reviewer","artifact_identity":"ed7340a8c28370a1eab416172fb2b7ea","decided_at":"2026-10-16T23:00:40.648Z","decision":"review","disputed_pct":0.2941,"findings_hash":"7obpSdAKtGnhjWgMtBXPGjA5fgyi74YgCs7njVkesrx2","investigation_id":"b20a5ebe-152f-4198-9df6-0987e1950faf","mode":"findings_only","new_score":40,"page_content_hash":"73f0816c74e81af795a7b0b5906ec6d211cafc6f40723ed64ad52b69bc5516b6","page_slug":"curve-llamalend","prev_score":40,"reason":"The page's core incident narrative -- the June 2024 Egorov liquidation and $10M bad debt, the March 2026 sDOLA oracle manipulation, the October 2025 CRV-long bad debt and Egorov's April 2026 recovery-pool proposal, the May 2026 Stake DAO/vsdCRV exploit, and the July 2023 Vyper background -- is substantially well-sourced and checks out against independent reporting, often down to specific dollar and percentage figures (e.g., the $700K/70%-backed/71%-solvency figures and the $19B tariff-crash liquidation figure are all precisely confirmed). However, the review surfaced several concrete defects: a likely-fabricated or at minimum uncited attribution to ZachXBT; a citation misattributed to CoinDesk that is actually The Block, bundled with a causal claim (borrowed proceeds funding the mansions) not supported by that source; a dead/wrong-slug thedefiant.io URL whose correct live version turns out to be a June 2024 article, not the 'April 2026' accusations the page describes; an unsupported and internally-contradicted claim that the 2023 Vyper exploit caused the 2024 bad-debt cascade; a disputed 47%-of-supply figure that none of the page's own sources support; two dead mirror-site citations in the sDOLA section (working replacements identified); and a systemic 404 pattern across all resources.curve.finance/docs.curve.finance citations. None of these defects reverse the page's overall risk characterization, but several (especially the ZachXBT attribution and the CoinDesk/Block misattribution) are the kind of checkable, specific errors that should be corrected before the next publish cycle.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}