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 · SafeW Technology Co. Ltd. (SafeW Messaging App)
- Sequence
- #2
- Score
- 2 → 0 (-8)
- Cluster
- mainnet-beta
- Slot
- 462046685
- Off-chain at
- 2026-10-27T11:03:45.445Z
- Anchored at
- 2026-10-27T11:03:52.000Z
- Block time
- 2026-10-27T11:03:52.000Z
Independent verification
- 1. Database (off-chain)
- 8fjophn8WkrHCaAvAvTYt6ZwrP9KpntzGHgTvtzpgrFB
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2162 chars)
{"actor":"judge","artifact_identity":"b580b99d1501a3cb68fceb65ccaef085","band_override":{"actual_delta":-8,"actual_verdict":"review_revise","disputed_pct":0,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"Six of the seven checkable claims were confirmed against Treasury, OpenSanctions, the Singapore Police Force and TRM Labs, so the computed disputed share is 0% (claim_findings[7] was excluded because its source blocked the reviewer). The page moves out of the approve band because claim_findings[3], in a critical section, attributes the Bybit and WazirX hacks to Xinbi and SafeW and no cited source says so, and because coverage_gaps[0] (SafeW ownership, jurisdiction and operations) is high priority. The sanction is current and the page reports it, so no omission applies. The unsupported specifics should be removed, which makes this a minor revision."},"blocked_count":1,"decided_at":"2026-10-27T11:03:45.083Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"549c8914-6b37-43af-b419-1249946871d6","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"safew-technology-co-ltd-safew-messaging-app","prev_score":2,"reason":"Six of the seven checkable claims were confirmed against Treasury, OpenSanctions, the Singapore Police Force and TRM Labs, so the computed disputed share is 0% (claim_findings[7] was excluded because its source blocked the reviewer). The page moves out of the approve band because claim_findings[3], in a critical section, attributes the Bybit and WazirX hacks to Xinbi and SafeW and no cited source says so, and because coverage_gaps[0] (SafeW ownership, jurisdiction and operations) is high priority. The sanction is current and the page reports it, so no omission applies. The unsupported specifics should be removed, which makes this a minor revision.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"scored_claims":7,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}