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
#6
Score
0 → 0 (-5)
Cluster
mainnet-beta
Slot
461971459
Off-chain at
2026-10-27T06:36:55.427Z
Anchored at
2026-10-27T06:37:15.000Z
Block time
2026-10-27T06:37:15.000Z

Independent verification

1. Database (off-chain)
7iCrECcgYv39oXyDnKLWFwYrQp2qJ1f5XNQZzafqRoTF
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2424 chars)
{"actor":"judge","artifact_identity":"287c41aa960a64e4b95ba13761ba6eae","band_override":{"actual_delta":-5,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"Of 10 claim findings, 2 were unscored because the sources blocked the reviewer, leaving 8 scored; none were disputed or unverifiable, so the computed disputed share is 0%. The core narrative holds: the 1,700, 323 and 10 million figures and the AMF quote match Tier 1 sources (claim_findings[0], [3], [5], [6]). The verdict moves one band above approval because of a high-priority coverage gap (the page leans on secondary crypto outlets instead of primary ESMA, AMF and AFM statements) and because the page presents Belgium's FSMA as an impersonated regulator and as part of the August 6 warnings without support in readable sources (claim_findings[1], [2]). Both omissions are minor, the subject is still operating, and the page is about two months out of date, so the penalty is small."},"blocked_count":2,"decided_at":"2026-10-27T06:36:55.061Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"e554ffac-0e94-4306-af8b-f69c8a52c9d9","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"eu-mica-regulator-impersonation-scam-wave","prev_score":0,"reason":"Of 10 claim findings, 2 were unscored because the sources blocked the reviewer, leaving 8 scored; none were disputed or unverifiable, so the computed disputed share is 0%. The core narrative holds: the 1,700, 323 and 10 million figures and the AMF quote match Tier 1 sources (claim_findings[0], [3], [5], [6]). The verdict moves one band above approval because of a high-priority coverage gap (the page leans on secondary crypto outlets instead of primary ESMA, AMF and AFM statements) and because the page presents Belgium's FSMA as an impersonated regulator and as part of the August 6 warnings without support in readable sources (claim_findings[1], [2]). Both omissions are minor, the subject is still operating, and the page is about two months out of date, so the penalty is small.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"scored_claims":8,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}