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 · Poloniex
- Sequence
- #4
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 464275360
- Off-chain at
- 2026-11-01T23:22:41.503Z
- Anchored at
- 2026-11-01T23:23:06.000Z
- Block time
- 2026-11-01T23:23:06.000Z
Independent verification
- 1. Database (off-chain)
- AsZWMXCbMHqXYyLtEmkt5v9DAWBcbRFRB6bEBp5pPUZx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1323 chars)
{"actor":"judge","artifact_identity":"40948502f0569de63cd9d1893c10630a","band_override":null,"decided_at":"2026-11-01T23:22:41.287Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.5,"investigation_id":"c6694f49-a602-4394-b3dd-d238fce195db","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"page_slug":"poloniex","prev_score":58,"reason":"Of 10 claims reviewed, 2 were disputed and 3 could not be verified, giving 50%, which falls in the significant-issues band. The disputed items are claim_findings[0], where OFAC's own release gives a base penalty of $99,237,000 rather than $98.8 million, and claim_findings[1], where a quote attributed to the SEC order comes from OFAC's release. The unverified items (claim_findings[5], [8], [9]) were not checked rather than contradicted, and the core SEC and OFAC settlement amounts and the November 2023 hack were confirmed. Because reviewer confidence is low (0.5) and the errors are factual details rather than core allegations, the penalty is set at the lighter end of the band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}