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_revise · Avalanche
- Sequence
- #3
- Score
- 62 → 52 (-10)
- Cluster
- mainnet-beta
- Slot
- 425012435
- Off-chain at
- 2026-06-08T01:35:41.775Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Ev4Z3yfDZZVoMVYQdDXSix9UvTtKsTQGtUqNdfTXTHH6
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1559 chars)
{"actor":"judge","decided_at":"2026-06-08T01:35:41.551Z","decision":"review_revise","investigation_id":"c671e84d-553e-41a5-85b4-ce818806fac0","new_score":52,"page_slug":"avalanche","prev_score":62,"reason":"The reviewer confirmed 17 of 27 claims outright, with strong Tier 1 sourcing across funding rounds, the CryptoLeaks scandal, network outages, and tokenomics. The most material error is in the Regulatory Status section (claim_findings[24]): the page states ETF approvals were 'pending as of the investigation date' when all three named AVAX ETFs (VanEck VAVX, Grayscale GAVA, Bitwise BAVA) had launched on Nasdaq before June 2026 — a demonstrably stale and affirmatively incorrect statement flagged as a high-priority coverage gap. Secondary issues include the defamation judgment year error (claim_findings[3], page says 2021 but judgment was issued May 2023), two unverifiable DeFi claims with no dedicated sourcing (claim_findings[20] Dexible, claim_findings[29] VanEck VBILL), a one-day date error in the Platypus Finance timeline entry (claim_findings[19]), and the Avalanche9000 upgrade being attributed to '2025-2026' when it activated December 2024. One citation (thelayer.xyz for the 3AC claim) returned link rot but the underlying fact was independently corroborated. The core investigative record is sound; the page requires targeted corrections before the regulatory and ETF sections are accurate.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}