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 · Manta Network
- Sequence
- #5
- Score
- 52 → 44 (-8)
- Cluster
- mainnet-beta
- Slot
- 443512766
- Off-chain at
- 2026-08-25T08:05:35.162Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- J1tZUoZd94Zcmi3DLc2J6gY46iWf99NKt2fese8sMtae
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1320 chars)
{"actor":"judge","decided_at":"2026-08-25T08:05:34.895Z","decision":"review_revise","investigation_id":"3f4154e9-e2fc-4b90-a627-87d228a0a2e4","new_score":44,"page_slug":"manta-network","prev_score":52,"reason":"Most of the page holds up: the DDoS attack details and the Korean BD representative token-dump allegations, along with the funding round, airdrop controversy, and Veridise audit, were independently confirmed against cited and outside sources. Two claims did not hold up. The tokenomics section states 67.4% of token supply has unlocked, but the page's own cited source (Tokenomist.ai) and an independent aggregator (CoinGecko) both show approximately 47.9% unlocked, a roughly 20-point gap that understates dilution risk (claim_findings[25]). Separately, the page describes a completed BlockApex security audit, but the cited link is a generic marketing page with placeholder statistics rather than a finished audit report (claim_findings[27]). The reviewer also flagged two high-priority coverage gaps -- an unlock-schedule correction and independent on-chain tracing of the Korean allegations -- that warrant follow-up before this page is treated as fully settled.","score_delta":-8,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}