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_revise · Acme Crypto
- Sequence
- #3
- Score
- 50 → 42 (-8)
- Cluster
- mainnet-beta
- Slot
- 462171209
- Off-chain at
- 2026-10-27T18:25:01.743Z
- Anchored at
- 2026-10-27T18:25:22.000Z
- Block time
- 2026-10-27T18:25:22.000Z
Independent verification
- 1. Database (off-chain)
- 7G3ZY1hJkKszRJksqXceRAT165BtRKx6u6VevJcxsUst
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1869 chars)
{"actor":"judge","artifact_identity":"ad7adbccfd495e49b5a6d5a6ab58c95a","band_override":null,"decided_at":"2026-10-27T18:25:01.429Z","decision":"review_revise","delist_requested":false,"disputed_pct":0,"investigation_id":"0a40ef46-ef6c-4f3a-ae35-52a0df8976ac","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":42,"page_slug":"acme-crypto","prev_score":50,"reason":"The page's factual claims largely hold: the Medium self-description (claim_findings[0]) and the 2018 pump-and-dump study (claim_findings[1]) were confirmed. However, claim_findings[2] is only partially supported, because the page says no crypto entity called Acme has regulatory or complaint records, while Thai reporting covers a fraud case involving an individual nicknamed 'Acme' (omission_findings[0], material). The reviewer found no link between that case and the Medium group, so the penalty is limited to a minor adjustment. The primary source also could not be read directly (coverage gap, high priority), which supports a revision to add the namesake note and archive the source.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"sequence_num":3,"severity_override":{"applied":true,"band":"minor","from_band":"approve","reason":"Claim findings give 0% disputed (2 confirmed, 1 partially supported, none disputed or unverifiable), but omission_findings[0] is rated material: Thai reporting on a fraud case involving a person nicknamed 'Acme' is not mentioned, and the page's statement that no crypto entity called Acme has complaint records is too broad. Escalated to the minor band only, because no link to the Medium group was found and subject_status does not contradict the page."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}