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.

Decision
review_revise · Garantex
View on Solana ↗
Sequence
#4
Score
0 → 0 (0)
Cluster
mainnet-beta
Slot
462173662
Off-chain at
2026-10-27T18:33:52.624Z
Anchored at
2026-10-27T18:34:04.000Z
Block time
2026-10-27T18:34:04.000Z

Independent verification

1. Database (off-chain)
3CpvVMojwVZv3Qt7aj6p9LsvF7obrND8GZZiRaSokXRx
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1945 chars)
{"actor":"judge","artifact_identity":"052cef9de3d6f24161db718df049ee61","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T18:33:52.370Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2857,"investigation_id":"e330db80-c665-4c9a-af18-efa6a49cc091","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"garantex","prev_score":0,"reason":"Of 8 claim findings, 1 was excluded as source_blocked (TRM, CoinDesk, ICIJ and EU sources were not fetched; this is a coverage limit, not a defect). Of the remaining 7, 2 are not confirmed: claim_findings[0] is disputed, because the India arrest appears to be attributed to the wrong co-defendant, and claim_findings[6] is unverifiable because the quoted commentary was not found in the cited article. That gives 29%, in the minor band. The core claims on the seizure, charges, the $96B and $100M figures, the August 2025 OFAC action and the Japan listing were confirmed against DOJ, Treasury and crypto.news. Because the disputed claim names a specific person and rests on weaker evidence, the penalty is set near the middle of the band. The page should correct the arrest attribution and fix the citations for the reward and $100M statements.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":7,"sequence_num":4,"severity_override":{"applied":false,"band":null,"from_band":"minor","reason":"The material omission (omission_findings[0], Besciokov's India arrest) describes the same defect as claim_findings[0], which is already counted as disputed, so escalating would count it twice. Its only source is a Tier 3 search snippet that was not fetched in full, and reviewer confidence is 0.55. subject_status does not contradict the page."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}