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 · Poloniex
- Sequence
- #3
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 464275356
- Off-chain at
- 2026-11-01T23:22:41.353Z
- Anchored at
- 2026-11-01T23:23:05.000Z
- Block time
- 2026-11-01T23:23:05.000Z
Independent verification
- 1. Database (off-chain)
- 9ZCioQTsYuAMhjY2buhUWp8QzraQMexPxzRYVYtCYo1P
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1420 chars)
{"actor":"reviewer","artifact_identity":"40948502f0569de63cd9d1893c10630a","decided_at":"2026-11-01T23:22:41.287Z","decision":"review","disputed_pct":0.5,"findings_hash":"EjQfNLvupaQerjZ6xGXBKXAZy882zDZsRAA5diVDjTQZ","investigation_id":"c6694f49-a602-4394-b3dd-d238fce195db","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"omissions":{"material":0,"total":1},"page_content_hash":"e561d64c66ffb3646d6afdb889872e7882f4897d04ae1057bdc85b0f28af2a64","page_slug":"poloniex","prev_score":58,"reason":"The core facts hold: the SEC settlement ($10,388,309, August 2021), the OFAC settlement ($7,591,630, 65,942 violations), and the November 2023 hack date and headline loss. Two errors are disputed. The base penalty is $99,237,000, not $98.8M, and the 'no business operations and no employees' quote comes from OFAC's release, not the SEC order. The page also blends the platform period with the violation period, which OFAC dates July 2015 to September 2019. Several hack-detail and attribution claims were not independently checked, and the timeline entries carry no sources.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}