Skip to main content
AVOID.NET
← 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_approve_with_notes · Manta Network
View on Solana ↗
Sequence
#3
Score
4247 (+5)
Cluster
mainnet-beta
Slot
443508712
Off-chain at
2026-08-18T20:40:45.546Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
5xq23DWH6VmSKw6eZtEDrJJkAYaLt3ALbxNv4kNRJsmM
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2297 chars)
{"actor":"judge","decided_at":"2026-08-18T20:40:45.136Z","decision":"review_approve_with_notes","investigation_id":"3f4154e9-e2fc-4b90-a627-87d228a0a2e4","new_score":47,"page_slug":"manta-network","prev_score":42,"reason":"Content accuracy holds up: 12 of 13 claims were confirmed or partially supported, and the sole dispute (claim_findings[0], the mainnet launch date) is a minor internal-consistency error — the page's own timeline entry already states the correct September 2023 date; only the prose in the Project Overview needs fixing. On calibration, the reviewer's push from WARNING/42 to CAUTIONARY/58 treats the Bithumb insider-dumping allegation (claim_findings[4]; calibration_assessment incident 1) as effectively suffered or architectural risk, but the review's own attribution table marks it 'a' (own-conduct-adjacent) and the rubric anchor states that an unresolved own-conduct/negligence allegation, not convicted, maps to WARNING (20-49) — not CAUTIONARY. The underlying facts of that incident (token transfer volume, timing, and ETH conversion amount) are independently corroborated across multiple outlets even though intent and legal characterization remain unadjudicated, which keeps the page in WARNING territory. That said, roughly 2.5 years without any regulatory or exchange finding, a credible competing explanation from Manta that the page fairly presents, and the page's consistently hedged language argue for moving toward the top of the WARNING band rather than leaving the score at 42, which reads closer to a confirmed-incident position than the evidence supports. Notes: (Fix the mainnet launch date in the Project Overview section — it states July 2023, but the page's own timeline entry and independent sources confirm the Mainnet Alpha launch was September 12, 2023.) (Add an explicit line noting the absence of any SEC/CFTC/non-US regulatory enforcement action and the absence of a funds-loss smart contract exploit history, per reviewer coverage gaps.) (Source or remove the specific Ontology/Zilliqa/ARPA early-investment detail attributed to Victor Ji, which could not be independently corroborated in the review.)","score_delta":5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}