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.

Decision
review_revise · HTX
View on Solana ↗
Sequence
#3
Score
188 (-10)
Cluster
mainnet-beta
Slot
426262063
Off-chain at
2026-06-13T19:26:29.337Z
Anchored at
Block time

Independent verification

1. Database (off-chain)
4UYNzcQLLdQPMggK42PbjzKNvZFD1igXzXy1yecQViBd
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1474 chars)
{"actor":"judge","decided_at":"2026-06-13T19:26:29.135Z","decision":"review_revise","investigation_id":"209069f2-af57-47e8-baef-8d5873d176e2","new_score":8,"page_slug":"htx","prev_score":18,"reason":"The page's core legal and event record — guilty plea, $4.3 billion settlement, four-month sentence, incarceration dates, October 2025 pardon, Hamas lawsuit, and the March 2026 DOJ/Fortune Iran investigation — is robustly confirmed by multiple Tier 1 sources with no link rot or stale citations. The reviewer's computed disputed_pct of 12% (one disputed claim out of 17) places this in the minor-issues band. The single disputed claim, claim_findings[0], concerns the birth date stated as February 10, which conflicts with the timeline's own February 5 entry and is unconfirmed by any authoritative source — an internal inconsistency on a peripheral biographical detail, not a core allegation. The most material accuracy gap is claim_findings[8]: the page states a $50 million personal fine but omits the separate $150 million CFTC civil penalty, understating total personal monetary exposure by $100 million. Additionally, all eight section content fields are empty (coverage_gaps[0], priority: high), making the page a summary-and-timeline stub that requires substantive narrative expansion before it meets publication standards.","score_delta":-10,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}