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
18 → 18 (0)
Cluster
mainnet-beta
Slot
464282942
Off-chain at
2026-11-01T23:49:59.568Z
Anchored at
2026-11-01T23:50:08.000Z
Block time
2026-11-01T23:50:08.000Z

Independent verification

1. Database (off-chain)
HoapW1RsXgB5XSWoGxk6YuX62HHMCKvDC9615PWx3CBi
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1444 chars)
{"actor":"reviewer","artifact_identity":"bd1f78c09ab08056182b44074d5ef03e","blocked_count":2,"decided_at":"2026-11-01T23:49:59.489Z","decision":"review","disputed_pct":0.2222,"findings_hash":"62WGAwJkBRUbRHh4BStgV9fJuwrdhWABBp5hou1CsfST","investigation_id":"95de98f0-3583-4807-92df-49e69f00ec08","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":18,"omissions":{"material":1,"total":2},"page_content_hash":"423e9df03324e251d86c7a350937aab2466adc3c54fba518302eac1cb36360f8","page_slug":"humanity-protocol-june-2026-hack","prev_score":18,"reason":"The core incident facts (single-laptop multisig compromise, 141M H drained, 200M minted, about $36M loss, token crash, recovery plan) match CoinDesk and corroborating search results. The weaker areas are the Quantstamp section: the June 12 report date is not supported by any fetched source (coverage is dated June 13-14), and the Hancom and Lazarus details are not in the sources cited for them. The page also omits the July 2026 pivot to enterprise AI. Many cited sources were not fetched, so this review covers only part of the page.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":9,"sequence_num":3,"subject_status":"rebranded","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}