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 · Orionx (Chile Exchange Shutdown 2026)
- Sequence
- #2
- Score
- 4 → 4 (0)
- Cluster
- mainnet-beta
- Slot
- 461840718
- Off-chain at
- 2026-10-26T22:53:58.952Z
- Anchored at
- 2026-10-26T22:54:03.000Z
- Block time
- 2026-10-26T22:54:03.000Z
Independent verification
- 1. Database (off-chain)
- CATtL5WsTsUKJ9HSbmD9DzHgvrSpK1YpppWvtJgVFfJi
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1305 chars)
{"actor":"judge","artifact_identity":"e1abff0ff46b53ae175f1d09db684cd7","band_override":null,"decided_at":"2026-10-26T22:53:58.604Z","decision":"review_approve","delist_requested":false,"disputed_pct":0,"investigation_id":"40919f8e-2968-4d1d-8986-2a3d22550202","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":4,"page_slug":"orionx-chile-exchange-shutdown-2026","prev_score":4,"reason":"Six of the seven checked claims were confirmed against the CMF primary statement and crypto.news reporting (claim_findings[0] to [5]), and none were disputed or unverifiable, giving 0% disputed. The only imperfection is claim_findings[6], where the complaint date in the timeline is given as 2026-09 rather than the day-level 2026-09-02 the sources support. The shutdown is already reflected on the page (subject_status.contradicts_page is false), and both omissions are minor, so no band escalation applies. Open coverage gaps (a primary Orionx closure notice, on-chain tracing) are medium priority and suggest expansion rather than penalty.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}