Skip to main content
Sign in
← 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 · Avalanche
View on Solana ↗
Sequence
#2
Score
62 → 62 (0)
Cluster
mainnet-beta
Slot
425012432
Off-chain at
2026-06-08T01:35:41.703Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
FwL6ScniFUVym6azavX46hure3AVEM1NRBrJSKzgPwhp
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1261 chars)
{"actor":"reviewer","decided_at":"2026-06-08T01:35:41.551Z","decision":"review","investigation_id":"c671e84d-553e-41a5-85b4-ce818806fac0","new_score":62,"page_slug":"avalanche","prev_score":62,"reason":"The Avalanche investigation page is broadly well-sourced and factually accurate on its major claims — funding rounds, the 2022 CryptoLeaks scandal, network vulnerability disclosures, outages, and tokenomics. The most material error is the claim that AVAX ETF approvals were 'pending as of the investigation date' when in fact VanEck VAVX launched January 26, 2026, Grayscale GAVA launched March 12, 2026, and Bitwise BAVA received exchange certification April 14, 2026 — all before the June 2026 investigation date. Secondary issues include the defamation judgment year (stated as 2021 but awarded May 2023), a one-day error in the Platypus Finance exploit date (timeline says Feb 17, sources confirm Feb 16), and the Avalanche9000 upgrade being dated 2025-2026 when it activated December 16, 2024. The thelayer.xyz source cited for the 3AC claim returned connection refused, constituting link rot for that citation.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}