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 · Themis Protocol
- Sequence
- #4
- Score
- 50 → 50 (0)
- Cluster
- mainnet-beta
- Slot
- 465112868
- Off-chain at
- 2026-11-04T01:13:14.290Z
- Anchored at
- 2026-11-04T01:13:26.000Z
- Block time
- 2026-11-04T01:13:26.000Z
Independent verification
- 1. Database (off-chain)
- C1WGNPTLeJN8tVP2s9iqSrQaYuU16Q7fSBRB8iLYx6c2
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1364 chars)
{"actor":"judge","artifact_identity":"d46c4f8efab97b9e42f927a85ac0a2b8","band_override":null,"blocked_count":1,"decided_at":"2026-11-04T01:13:14.062Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"1848f0de-42fd-40f9-ba1b-84c8aa72ef2a","judge_def_hash":"750934ecb48272224909b7430fab271676d391380fbc821acbe7ee7e4cac2fa3","new_score":50,"page_slug":"themis-protocol","prev_score":50,"reason":"Of 7 claim findings, 1 was excluded because the source blocked the reviewer (claim_findings[2]), leaving 6. None were disputed and 1 was unverifiable (claim_findings[3], the 2023-06-28 laundering date has no source), giving about 17% and the minor-issues band. The core exploit facts (date, loss of about $365-370K, attacker address, contract and transaction identifiers, audits) were confirmed. The compensation statement (claim_findings[6]) may be outdated, and the Neptune Mutual figures could not be checked because the source was blocked, which limits coverage but does not count against the page. No material omissions were reported and the subject status matches the page.","reviewer_def_hash":"3839668b232611e5b26db72079d64745f8e57e919b8a379e79b44ba4a52c845b","score_delta":0,"scored_claims":6,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}