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 · Chris Larsen
- Sequence
- #3
- Score
- 59 → 59 (0)
- Cluster
- mainnet-beta
- Slot
- 464298394
- Off-chain at
- 2026-11-02T00:45:06.757Z
- Anchored at
- 2026-11-02T00:45:15.000Z
- Block time
- 2026-11-02T00:45:15.000Z
Independent verification
- 1. Database (off-chain)
- 4TSs8cJWFwZMH4bKuL3SQ3ry3CBX7StpgoyDYamiM7C7
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1401 chars)
{"actor":"reviewer","artifact_identity":"a74edbbc17afcd317438dc0e008f64ab","decided_at":"2026-11-02T00:45:06.692Z","decision":"review","disputed_pct":0.5,"findings_hash":"Akah8Mrk8hctSLn7WEWz1NfPD1Wj2hN2tXn3UgnZdZos","investigation_id":"e5734f78-2101-4c4a-84d8-963676a26bd8","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":59,"omissions":{"material":1,"total":1},"page_content_hash":"dc3a6bf30bb65b533deca8710d26419907e1a6211b9fdffb205d884e514eeb17","page_slug":"chris-larsen","prev_score":59,"reason":"The hack, LastPass link and DOJ forfeiture narrative are broadly consistent with widely reported facts, but the SEC resolution is materially wrong: the page states a $125M settlement returning $75M of $150M, dates it March 2025, and elsewhere says Ripple paid $50M. In fact the $50M deal was rejected, and appeals were dismissed in August 2025 leaving the $125M penalty and injunction. CEO step-down date (2016-01) is also wrong (effective Jan 2017). Timeline contains duplicated entries and the 'largest individual theft of 2024' claim is unsupported.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}