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 · Ledger
- Sequence
- #4
- Score
- 58 → 58 (0)
- Cluster
- mainnet-beta
- Slot
- 462048319
- Off-chain at
- 2026-10-27T11:09:34.371Z
- Anchored at
- 2026-10-27T11:09:39.000Z
- Block time
- 2026-10-27T11:09:39.000Z
Independent verification
- 1. Database (off-chain)
- Gfsw6RQZYwFdgsNhuc88dJWHffH3gkKZufAyxzhHNiBy
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1275 chars)
{"actor":"reviewer","artifact_identity":"53f7cc1de4bb4212f6609544412b3ef0","decided_at":"2026-10-27T11:09:34.040Z","decision":"review","disputed_pct":0.2857,"findings_hash":"CwxFWgFRtBNunj5fFLH5yRVyL53CPLFmRwYaL7kARAcK","investigation_id":"03d5d83f-6247-4200-998e-048db3536286","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":58,"omissions":{"material":0,"total":2},"page_content_hash":"fad9536d098265d50083bd8c00272748fde11d697b599e31c46d4f9b59b99e03","page_slug":"ledger","prev_score":58,"reason":"The incident chronology (2020 breach, Connect Kit, fake App Store app, Global-e) is well sourced, hedged and matches the sources I read. The main defect is staleness: the page says Ledger is preparing a US IPO, but May 2026 reporting says it paused. The timeline and summary also attribute the 270,000-address figure to Ledger's own notice, which says about 9,500. Many claims were not verified in depth, so confidence is limited.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"operating","subject_status_contradicts_page":true,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}