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.

Sequence
#3
Score
1813 (-5)
Cluster
mainnet-beta
Slot
443517192
Off-chain at
2026-08-25T22:09:09.421Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
8TkZRcDeJ5thMnVyWbNaunswb7DtCDUucCWi4J93oyUb
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1827 chars)
{"actor":"judge","decided_at":"2026-08-25T22:09:09.006Z","decision":"review_revise","investigation_id":"bf6890ab-103f-42e0-9e2a-e5dc9d2237a5","new_score":13,"page_slug":"humanity-protocol-h-token-hack","prev_score":18,"reason":"The reviewer verified 34 discrete claims and found the page's core narrative -- a $36M private-key/opsec compromise, the cross-chain drain and unauthorized minting, the DPRK tooling attribution, and ZachXBT's staged-hack claim and retraction -- solidly supported by tier-1 and tier-2 sources (claim_findings[0-16], [18-20], [22], [24-28], [30-31]). Only 3 of 34 claims count against the disputed_pct formula (disputed + unverifiable / total), giving 8.8%, comfortably inside the approve range: claim_findings[21] and [29] misdate the comparator Bybit hack as 'February 2026' when it occurred in February 2025, and claim_findings[23] (no formal government attribution) is a reasonable but unconfirmable negative claim. A related claim about stolen funds not moving through centralized exchanges (claim_findings[17]) is marked stale, since later reporting showed partial movement to KuCoin, though staleness does not count toward the disputed threshold. None of these defects touch the page's central factual claims about the hack itself. However, coverage_gaps[0] is marked high priority: the page omits Humanity Protocol's subsequently reported pivot away from decentralized identity toward enterprise AI, a development directly relevant to assessing the entity's current status and risk profile on a platform built around ongoing trust scoring. That high-priority gap, not the disputed_pct, is what moves this page from approve to a revise recommendation.","score_delta":-5,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}