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 · Google DeepMind
- Sequence
- #2
- Score
- 55 → 43 (-12)
- Cluster
- mainnet-beta
- Slot
- 449513516
- Off-chain at
- 2026-09-22T22:28:24.328Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- FQqAZN99dpu5EKKcNhwH6FpFVvyScDnhMnT5YSaqMs9d
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2511 chars)
{"actor":"judge","artifact_identity":"4149a8a09e471a9d56a1f2549bdc4b1e","band_override":{"actual_delta":-12,"actual_verdict":"review_revise","disputed_pct":0.0909,"expected_delta_range":[0,0],"expected_verdict":"review_approve","rationale":"Of the 11 claims checked, 8 were confirmed accurate, 1 was disputed, and 2 were flagged as stale, putting the disputed/stale rate at roughly 27% — within the range where the page needs correction but not removal. claim_findings[2] misattributes the 2023 dismissal of the Royal Free NHS data lawsuit to the wrong UK court and the wrong final date. claim_findings[3] and [4] both stem from the same underlying gap: the page describes the Thele v. Google Gmail/Chat/Meet privacy suit as still pending when a federal judge dismissed it (with leave to amend) in July 2026, before this page's own as-of date. A high-priority coverage gap flagged by the reviewer confirms this litigation-status tracking needs to be kept current. All other major claims — the wrongful-death suit, the antitrust slowdown complaint, the EU fines, the Gemini security-test breach, and the Google Coin scam — were independently corroborated by multiple tier-1 sources."},"decided_at":"2026-09-22T22:28:23.866Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.0909,"investigation_id":"b9bbaa78-e6f8-46f3-b03d-9be66d2c8150","new_score":43,"page_slug":"google-deepmind","prev_score":55,"reason":"Of the 11 claims checked, 8 were confirmed accurate, 1 was disputed, and 2 were flagged as stale, putting the disputed/stale rate at roughly 27% — within the range where the page needs correction but not removal. claim_findings[2] misattributes the 2023 dismissal of the Royal Free NHS data lawsuit to the wrong UK court and the wrong final date. claim_findings[3] and [4] both stem from the same underlying gap: the page describes the Thele v. Google Gmail/Chat/Meet privacy suit as still pending when a federal judge dismissed it (with leave to amend) in July 2026, before this page's own as-of date. A high-priority coverage gap flagged by the reviewer confirms this litigation-status tracking needs to be kept current. All other major claims — the wrongful-death suit, the antitrust slowdown complaint, the EU fines, the Gemini security-test breach, and the Google Coin scam — were independently corroborated by multiple tier-1 sources.","score_delta":-12,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}