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 · four.meme
- Sequence
- #4
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 462183874
- Off-chain at
- 2026-10-27T19:10:03.583Z
- Anchored at
- 2026-10-27T19:10:09.000Z
- Block time
- 2026-10-27T19:10:09.000Z
Independent verification
- 1. Database (off-chain)
- HCbiPqgBmxSXFNwhxqaYCtstkbHcdDJSj6ZXgzazUMCx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1347 chars)
{"actor":"reviewer","artifact_identity":"cea653845121d25d77d2b5182291be42","decided_at":"2026-10-27T19:10:03.421Z","decision":"review","disputed_pct":0.375,"findings_hash":"22wYVPNCypzcW32fi3xxgn12VCWqJLTLZFjL8dFCb893","investigation_id":"1be02c1b-0438-4836-bcbb-18f74708862e","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"page_content_hash":"56e34dc6628c90e4ab45e5417672e528fd97f34d2f6f22a2f42fa7f2b9dfdf85","page_slug":"fourmeme","prev_score":53,"reason":"The core exploit facts (Feb 11 and Mar 18, 2025 incidents, loss ranges, SlowMist root cause, the Oct 2025 pollution attack and fee) are supported by the sources I fetched. Issues found: the FixedFloat role looks reversed (it was the attacker's funding source), the interval between exploits is five weeks rather than six, the resumption date may be off by a day, the ZachXBT flag is unsupported, and the compensation claim was not found in the cited article. I did not fetch every cited source. The subject appears to be still operating.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":4,"subject_status":"operating","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}