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 · Compound V2
- Sequence
- #5
- Score
- 68 → 68 (0)
- Cluster
- mainnet-beta
- Slot
- 457441940
- Off-chain at
- 2026-10-16T00:44:18.916Z
- Anchored at
- 2026-10-16T00:44:44.146Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- cehw5iwCPn8LLxMPyyyCA2FTeTx7gToqWGH3EY3JtvA
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1902 chars)
{"actor":"reviewer","artifact_identity":"edc710b9e3a3e53cede3fbcdc5bd4d2a","decided_at":"2026-10-16T00:44:18.673Z","decision":"review","disputed_pct":0.3793,"findings_hash":"GkzdUAfv2jqCNn7etZNjePsf7BPVH8XztDrwSYnRuaNJ","investigation_id":"e3219d4b-6244-46ee-8372-f93fec77fb12","mode":"findings_only","new_score":68,"page_content_hash":"9c8948df7015bf072708ffc7b7634f59fa9ceabd40eb4ea41c40151f087284ad","page_slug":"compound-v2","prev_score":68,"reason":"Most of the page's well-known historical incidents (the 2021 COMP distribution bug, the November 2020 oracle liquidation, the July 2024 website hijack, the 2023 X-account hack, and the Rari Capital/Sonne Finance fork exploits) are solidly supported by the cited sources and independent corroboration, with only minor date/attribution slippage. The weakest part of the page is the July 2024 'Golden Boys' governance-attack narrative, where the proposal numbering is demonstrably wrong (the real on-chain Proposal 118 is an unrelated 2022 Gauntlet vote; the actual sequence was Proposal 247 then Proposal 279 before Proposal 289 passed) and a specific Bybit-withdrawal/81%-quorum mechanic is misattributed to the wrong proposal. The page's central framing claim -- that V2 was formally deprecated via a December 7, 2025 vote with 99.99% approval pausing all borrows/mints and setting reserve factors to 100% -- could not be independently verified against governance records despite substantial search effort, and its own cited comp.xyz source does not support it. The page also omits a live, directly relevant controversy over alleged Compound Foundation misuse of V2 reserve funds for governance voting power, and the broader regulatory/legal history (an active securities class action) is entirely absent.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}