Skip to main content
AVOID.NET
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 · Humanity Protocol H Token Hack
View on Solana ↗
Sequence
#2
Score
18 → 18 (0)
Cluster
mainnet-beta
Slot
443517183
Off-chain at
2026-08-25T22:09:09.274Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
HZ5hP8GxqpNWpMnAFkyM1UJ7RURXVr8HsMLxPT5KirXs
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1680 chars)
{"actor":"reviewer","decided_at":"2026-08-25T22:09:09.006Z","decision":"review","investigation_id":"bf6890ab-103f-42e0-9e2a-e5dc9d2237a5","new_score":18,"page_slug":"humanity-protocol-h-token-hack","prev_score":18,"reason":"The page's central factual narrative — a $36M operational-security/private-key compromise (not a smart-contract exploit) enabling cross-chain draining and unauthorized minting of H tokens, followed by a DPRK tooling attribution and a documented recovery/migration program — is well-supported by multiple independent tier-1 and tier-2 sources and was independently corroborated across nearly all checked claims, including exact figures (6M/141.2M/300M token amounts, contract address, snapshot mechanics) and direct quotes (ZachXBT, Kwok). The page correctly distinguishes this as a key-management/multisig failure rather than a smart contract bug or exchange hack, and accurately presents ZachXBT's initial staged-hack allegation alongside his subsequent retraction. Two recurring errors were found: the page twice misdates the comparator Bybit hack as occurring in 'February 2026' when it occurred in February 2025 per Halborn's own research and other reporting. One claim (no funds moved through centralized exchanges) is stale, as later on-chain tracking showed partial fund movement to KuCoin by June 20-21, 2026. The page also omits Humanity Protocol's subsequently reported strategic pivot away from its identity mission toward enterprise AI, a material development for assessing the entity's current status.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}