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
- Sequence
- #4
- Score
- 15 → 15 (0)
- Cluster
- mainnet-beta
- Slot
- 464362116
- Off-chain at
- 2026-11-02T04:32:29.599Z
- Anchored at
- 2026-11-02T04:32:52.000Z
- Block time
- 2026-11-02T04:32:52.000Z
Independent verification
- 1. Database (off-chain)
- 5wgGrHLtwdTN6hJjM8WA1zGE2pkkQb1jT965WjfFxhGv
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1473 chars)
{"actor":"reviewer","artifact_identity":"336d7b6deaa08405a5892cc48015b2fa","blocked_count":1,"decided_at":"2026-11-02T04:32:29.548Z","decision":"review","disputed_pct":0.2143,"findings_hash":"HiMP1McbEL3Bq2ZmVU2y4faMQ3sUDJoCr91pH95gfZVN","investigation_id":"4abf1a64-b6e0-4878-8180-781d9c05d9ce","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":15,"omissions":{"material":1,"total":3},"page_content_hash":"c66e11b0026e55aea85c29df822b1746f0124772bcc8f6c2204ae904ec2e6a49","page_slug":"humanity-protocol-staged-hack-allegation-zachxbt","prev_score":15,"reason":"The core narrative holds: a roughly $32-36M private key compromise on June 8-9, 2026, ZachXBT's 'possibly staged' claim, and his same-day update separating the hack from the market-maker concerns all match fetched sources. Problems are the repeated 'no third-party forensic report' statements, which are superseded by Quantstamp's report of around June 12; some unsourced specifics (3-of-6 and 3-of-5 thresholds, Halborn, Elton, the DEX-only point); a truncated HTX URL; and a wrong archive link for Blockonomi. The page omits the DPRK attribution.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":14,"sequence_num":4,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}