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 · DeepSeek
- Sequence
- #1
- Score
- 32 → 32 (0)
- Cluster
- mainnet-beta
- Slot
- 449513533
- Off-chain at
- 2026-09-22T22:28:33.078Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- B4Gbxt6qyz4mEFbSJww7yhborb3f3wGriZtELPHfkcLX
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1705 chars)
{"actor":"reviewer","artifact_identity":"507bfe14a2db888927664572d0e544db","decided_at":"2026-09-22T22:28:32.977Z","decision":"review","disputed_pct":0.3077,"findings_hash":"APLPSrE1hCWLAqRv9MuxgJCPmq5AF1yfQpiF7uFpuwnH","investigation_id":"52937998-58d6-49ab-a8d8-eba48078fd33","new_score":32,"page_content_hash":"95c85275136955a1e2d3b4287b95181f5e4f23b17c02917aa61fe6e9ba2a8257","page_slug":"deepseek","prev_score":32,"reason":"The page is largely well-sourced and its central claims about the Wiz database exposure, government bans, Khoury College censorship research, Singapore Nvidia chip investigation, and DeepSeek token impersonation scams are confirmed by the cited sources and independent corroboration. The most significant defect is a one-year date error: the page states OpenAI's memo to Congress alleging DeepSeek distillation was submitted February 12, 2025, in both the prose (sections[4]) and the timeline, but the page's own cited FDD source and independent Bloomberg reporting show the memo was actually released February 12, 2026 -- a full year later. This appears to be a transcription error conflating the memo with the earlier (correctly dated) January 29, 2025 Bloomberg report on the Microsoft/OpenAI investigation. A secondary, minor issue is the Singapore fraud-charge date being recorded as the source article's publication date (Feb 28, 2025) rather than the actual charge date (Feb 27, 2025). No link rot was found among the sampled sources; the Khoury, Wiz, and V3 technical-report claims check out precisely against primary sources.","score_delta":0,"sequence_num":1,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}