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 · Avalanche
- Sequence
- #4
- Score
- 52 → 52 (0)
- Cluster
- mainnet-beta
- Slot
- 457656056
- Off-chain at
- 2026-10-16T13:34:51.408Z
- Anchored at
- 2026-10-16T13:35:05.766Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Bo7SWE2aN1gqFtAFhR7fjKSQMDXCPQENL6QSdQMhbVe6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1776 chars)
{"actor":"reviewer","artifact_identity":"c56840a476dfb01906de6cc533994055","decided_at":"2026-10-16T13:34:51.159Z","decision":"review","disputed_pct":0.4828,"findings_hash":"6RreCenrqbm7VQquPGSnGwvKeirDbUb28GC6BX5eAdZD","investigation_id":"c671e84d-553e-41a5-85b4-ce818806fac0","mode":"findings_only","new_score":52,"page_content_hash":"4ad66c68f3b028af75a0f415bf8f8c1dfdc3ee126f192d8fc542a5e30017a116","page_slug":"avalanche","prev_score":52,"reason":"The page's core narrative — Avalanche's architecture, major funding rounds, the 2022 CryptoLeaks/Kyle Roche scandal, the Szilágyi 'insta-death' disclosure, the February 2024 outage, and the main DeFi exploits — is substantially corroborated by independent reporting. However, the review found a cluster of date errors that recur across section prose, headings and timeline fields: the James Edwards vulnerability disclosure is misdated by two full years (2023 reported as 2025, in three places), the $230M funding round's completion date is conflated with its later announcement date (June vs. September 2021, in two places), the Avalanche9000 upgrade is misdated by roughly a year, and Sirer's defamation judgment year is confused with the year of the underlying defamatory video. A cited SEC EDGAR filing is mislabeled as VanEck's S-1 when the document is actually Bitwise's. The ETF regulatory-status claim is stale given VanEck's AVAX ETF (VAVX) launched in January 2026. One claim (Dexible as an 'Avalanche-ecosystem' protocol) overstates an otherwise-accurate loss figure, and one DeFi exploit (the $370K June 2023 flash loan) is uncited and could not be verified either way.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}