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
22 → 17 (-5)
Cluster
mainnet-beta
Slot
462188761
Off-chain at
2026-10-27T19:26:53.368Z
Anchored at
2026-10-27T19:27:30.000Z
Block time
2026-10-27T19:27:30.000Z

Independent verification

1. Database (off-chain)
HHqjFV9V25G1eXzm7KVZtDEEJ7eDcyFcG7JaP51exzhu
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1972 chars)
{"actor":"judge","artifact_identity":"5744cac748b4e413addabde77f724fd5","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T19:26:53.047Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"fbe607bc-6621-425f-8591-06789d92cb1f","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":17,"page_slug":"bitcoin-de-bafin-mica-rejection-october-2026","prev_score":22,"reason":"Of the 10 countable claim findings, none were disputed and none were unverifiable (claim_findings[7], the 2023 BaFin notice, was blocked and is excluded), so disputed_pct is 0%. The core facts hold: the Oct 6 rejection, the end of forbearance, the custody statements, the restart plan and the H1 financials match the sources read. The review reports a material omission (omission_findings[0]): customers reportedly can still withdraw crypto, which the page does not say. For that reason the page is revised instead of approved. Smaller issues are that the 15-month figure is absent from the cited article (claim_findings[1]) and that the 2023 BaFin and CryptoTimes sources were not read.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-5,"scored_claims":10,"sequence_num":3,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"omission_findings[0] is rated material: reporting says customers can still withdraw crypto while trading and euro deposits are suspended, but the page's custody section reads as if assets are simply held pending transfer. The claim percentage (0%) cannot see this, so the minor band is used instead of approve. It is not pushed higher because the omission comes from search summaries rather than a fetched primary source and the page already frames custody risk as unresolved and alleged."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}