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 · Terraform Labs
- Sequence
- #5
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 423938171
- Off-chain at
- 2026-06-03T02:41:14.633Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 9Uc226kS9EqzctWj3hm425RhoQSwFJK64q9KYUmeBoFc
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1197 chars)
{"actor":"judge","decided_at":"2026-06-03T02:41:14.419Z","decision":"review_approve","investigation_id":"8578f585-9eb9-4844-b65d-f2b641b160e3","new_score":0,"page_slug":"terraform-labs","prev_score":0,"reason":"The reviewer examined 28 discrete claims across all page sections and found zero disputed or unverifiable findings. Twenty-two claims were fully confirmed by primary and secondary sources; the remaining five received 'partially_supported' verdicts that reflect minor characterization differences — notably claim_findings[25] omits 'securities fraud' from the guilty plea conspiracy count, and claim_findings[10] describes the Tai Mo Shan enforcement as a generic 'U.S. regulatory investigation' rather than an SEC action specifically. Neither constitutes a factual error. No link rot was detected; two sources returned 403 errors but all underlying facts were independently confirmed via Tier 1 sources including SEC.gov, Bloomberg, DOJ, and TechCrunch. Coverage gaps are all medium or low priority and suggest expansion rather than correction.","score_delta":0,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}