Skip to main content
Sign in
← 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
00 (-12)
Cluster
mainnet-beta
Slot
425239823
Off-chain at
2026-06-09T02:45:07.771Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
52zVfYyBRWpbwxTwfqzsjtdsYfdV96MaLYzax5Vhdqpk
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1663 chars)
{"actor":"judge","decided_at":"2026-06-09T02:45:07.375Z","decision":"review_revise","investigation_id":"39fa81fa-065d-4dbd-9013-342ab1bedc38","new_score":0,"page_slug":"faris-ali-uk-crypto-home-invasion-ring","prev_score":0,"reason":"The core narrative of this investigation is well-supported: robbery date, location, perpetrator identities, charges, individual sentence lengths, and asset recovery are confirmed across multiple independent outlets. However, the reviewer identified four disputed claims that require correction before this page meets publication standard. Most significantly, claim_findings[17] shows the TRM Labs citation (a Tier 1 source) does not mention TLOxp or database compromise at all — the page incorrectly attributes that specific finding to TRM Labs. Claim_findings[31] misattributes a US Department of Justice prosecution of twelve defendants to a Metropolitan Police UK operation, a clear geographic and jurisdictional error in the broader-context section. Claim_findings[23] and timeline entry [7] date ZachXBT's post-sentencing statement as 'June 2025,' which is chronologically impossible given sentencing occurred November 7, 2025 — the tweet ID is consistent with June 2026, indicating a likely year transcription error. A fourth disputed item (ENS domain registration date) is unverifiable and should be qualified as approximate. None of these errors undermine the central facts of the case, but two involve named third parties (TRM Labs, Metropolitan Police) and must be corrected.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}