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_approve · Ian Sofronov
- Sequence
- #4
- Score
- 26 → 26 (0)
- Cluster
- mainnet-beta
- Slot
- 462174724
- Off-chain at
- 2026-10-27T18:37:16.711Z
- Anchored at
- 2026-10-27T18:37:49.000Z
- Block time
- 2026-10-27T18:37:49.000Z
Independent verification
- 1. Database (off-chain)
- 8t8cxHmeYZrXRjJcmFJWsokfNvyF7EuGEWNHogoJSsFi
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1606 chars)
{"actor":"judge","artifact_identity":"5e16247660523992912aad9a202847b7","band_override":null,"decided_at":"2026-10-27T18:37:16.470Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"5c78a746-9fbf-4656-a3a3-6566eb9c5bae","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":26,"page_slug":"ian-sofronov","prev_score":26,"reason":"Of 9 claim findings, none were disputed and none were unverifiable, so the disputed share is 0%. The central statement, that no public record links an 'Ian Sofronov' to Gotbit, was confirmed (claim_findings[0]), and the Gotbit case background matches the readable sources, including the SEC release of 2026-08-03 (claim_findings[7]). Three findings are only partly supported (claim_findings[4], [5], [8]): the plea date comes from a sentencing article, the defense's time-served framing is missing, and the status of two directors is unresolved. These are minor and are better handled as edits than as a score penalty. Open coverage gaps are medium or low priority and suggest expansion, not denial.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"severity_override":{"applied":false,"band":null,"from_band":"approve","reason":"Not required by the review: the only omissions (time-served characterization, unconfirmed status of Kedrov and Jalili) are rated minor, and subject_status.contradicts_page is false."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}