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
- 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. - 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.
- 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 · Bitstamp
- Sequence
- #3
- Score
- 74 → 67 (-7)
- Cluster
- mainnet-beta
- Slot
- 424043687
- Off-chain at
- 2026-06-03T14:21:07.525Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 4doS9xiFuoPUPJCXkLT3GngH568uCMrhW1wdba5QYeHy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1253 chars)
{"actor":"judge","decided_at":"2026-06-03T14:21:07.253Z","decision":"review_revise","investigation_id":"c7c67b29-ba30-4cc4-9883-1d8a26e2c764","new_score":67,"page_slug":"bitstamp","prev_score":74,"reason":"The reviewer confirmed 21 of 26 claims outright with no claims directly disputed or contradicted by a more credible source. The four partially supported claims (claim_findings[9], [10], [11], [24]) involve minor precision gaps: a possible April vs. July 2016 license date discrepancy, the 80% NXMH stake figure sourced from media rather than the official press release, the Ripple stake acquisition described by disclosure month rather than actual transaction quarter, and institutional/retail client count figures (5,000/50,000) not traceable to the primary cited official sources. An additional partially supported claim (claim_findings[25]) flags the 70-asset/200-pair figures as likely understated relative to current data. None of these represent factual contradictions. One high-priority coverage gap — AML and sanctions compliance history — warrants expansion before the page can be fully cleared.","score_delta":-7,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}