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 · Humanity Protocol H Token Hack
- Sequence
- #4
- Score
- 13 → 13 (0)
- Cluster
- mainnet-beta
- Slot
- 457920844
- Off-chain at
- 2026-10-17T05:29:58.151Z
- Anchored at
- 2026-10-17T05:30:12.430Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- FejsGmZsMQcgcwUvxEnRXUnqEw4fEhb3G43kFeK1zBV1
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1952 chars)
{"actor":"reviewer","artifact_identity":"847f39883f2a6d037180be9a9d0a1447","decided_at":"2026-10-17T05:29:57.961Z","decision":"review","disputed_pct":0.0714,"findings_hash":"7CJoowK9v1MLiQrmgnnr2ChVFLuA9Ta9er3GnaSLq2C","investigation_id":"bf6890ab-103f-42e0-9e2a-e5dc9d2237a5","mode":"findings_only","new_score":13,"page_content_hash":"0876b1c4922491dd15de880a11534304742b70925f77266ba1bc29b9f371f40c","page_slug":"humanity-protocol-h-token-hack","prev_score":13,"reason":"The page's core narrative — a $36M operational-security breach on June 8-9, 2026 via a phishing-compromised employee laptop holding seven private keys, a 3-of-6 and 3-of-5 Gnosis Safe multisig takeover, an 80-89% token crash, a Quantstamp DPRK attribution, ZachXBT's staged-hack accusation and subsequent retraction, and a recovery/migration program with a $1M bounty — is well-supported by multiple independent, credible sources (CoinDesk, The Block, Decrypt, Rekt.news, crypto.news, the official claim.humanity.org portal). Specific figures (141.2M ETH-side drain, 447M total impact, 266.5M June 25 unlock, seven compromised keys, 76% DPRK share of 2026 losses) check out closely against independent reporting. The main defects found: one timeline date error (Quantstamp's findings are dated June 16 on the page but were published June 14), two dead/mismatched source URLs (cryptomortem.com is entirely unreachable; one cryptotimes.io URL 404s while a near-identical working URL exists elsewhere on the page), an unattributable 'analyst Elton' claim with a 'late April' date range not found in any source consulted (the real on-chain funding trail found runs late May only), and a materially incomplete picture of the BSC minting scale that omits QuillAudits' finding of ~1.5B minted versus the ~300M the page describes as the ceiling.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}