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 · Manta Network
- Sequence
- #2
- Score
- 42 → 42 (0)
- Cluster
- mainnet-beta
- Slot
- 443508707
- Off-chain at
- 2026-08-18T20:40:45.312Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- Ddt2FUvxoJ9JEi82na5Ctwr2EgNAnffGVCGZyBFXCfKs
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1421 chars)
{"actor":"reviewer","decided_at":"2026-08-18T20:40:45.136Z","decision":"review","investigation_id":"3f4154e9-e2fc-4b90-a627-87d228a0a2e4","new_score":42,"page_slug":"manta-network","prev_score":42,"reason":"The page is well-sourced and unusually well-hedged for a topic (the Bithumb insider-dumping allegation) that would commonly be reported as fact elsewhere; it consistently uses 'alleged,' attributes claims to named sources, and explicitly notes the absence of regulatory or legal follow-through. Independent verification confirmed nearly all major factual claims, including the L2Beat centralization findings, the DDoS attack, the Lazarus Group phishing attempt, funding figures, token/TVL performance, and the Atlantic deprecation. One factual error was found: the mainnet launch date is asserted as July 2023 in prose (contradicting the page's own correctly-dated timeline entry of September 2023, and contradicting the cited source and independent corroboration, which place Mainnet Alpha on September 12, 2023). No unhedged allegations, victim/perpetrator conflation, or retracted sources were found. Coverage gaps exist around regulatory history and current (2026) usage metrics, but these are omissions of unaddressed dimensions rather than defects in what is stated.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}