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 · DEUS Finance
- Sequence
- #3
- Score
- 53 → 53 (0)
- Cluster
- mainnet-beta
- Slot
- 462183223
- Off-chain at
- 2026-10-27T19:07:23.552Z
- Anchored at
- 2026-10-27T19:07:48.000Z
- Block time
- 2026-10-27T19:07:48.000Z
Independent verification
- 1. Database (off-chain)
- 13qzVYV6kQvGJvELwcSurPZauxpLZ2LhrLP7NDYtQtGm
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1330 chars)
{"actor":"reviewer","artifact_identity":"a79da3618a234ed17768e28a0a53a419","decided_at":"2026-10-27T19:07:23.438Z","decision":"review","disputed_pct":0.1667,"findings_hash":"9kz41fQtid48YQJwS2pZ5SKr3pPyDttdnynnWzykCCVJ","investigation_id":"8d65bcd5-e167-485e-a817-609b36d70291","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":53,"omissions":{"material":0,"total":1},"page_content_hash":"e0c811ffaf35d6a23adc06f0ec690edd90a73488bfe110d49ee5a0608c67d5b3","page_slug":"deus-finance","prev_score":53,"reason":"The core exploit narrative (March 2022 ~$3M, April 2022 ~$13.4M, May 2023 ~$6.5M burnFrom bug, Tornado Cash laundering, CertiK audit scope) matches the sources I fetched. Details I could not confirm from fetched sources include the 800 ETH Tornado funding, the per-chain May 2023 split, the OFAC/SEC/CFTC cross-check and the recovery multisig. The current-status section is stale (TVL is now $0). The prose has leftover editorial references to a 'survivor page' and 'merged page'.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":3,"subject_status":"unknown","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}