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 · Fake Crypto AML Checker Drainer Campaign
- Sequence
- #2
- Score
- 1 → 0 (-10)
- Cluster
- mainnet-beta
- Slot
- 462038095
- Off-chain at
- 2026-10-27T10:32:51.847Z
- Anchored at
- 2026-10-27T10:33:26.000Z
- Block time
- 2026-10-27T10:33:26.000Z
Independent verification
- 1. Database (off-chain)
- A1s85yFpGVnmeWTwH828je4fpTiPpETYYNJVesn5Rugw
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1727 chars)
{"actor":"judge","artifact_identity":"29e19ff2cb6d0efa82f31b172aac2705","band_override":null,"decided_at":"2026-10-27T10:32:51.590Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.2222,"investigation_id":"9f5d2533-95d6-4c30-8d08-0746bf78b79a","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"fake-crypto-aml-checker-drainer-campaign","prev_score":1,"reason":"Of 9 claims checked, 2 were disputed (22%): claim_findings[2] and [3] misstate the PCRisk guide's dates. The guide was last updated June 2, 2026, not first published then, and it was not updated through December 2026, which is in the future. The Malwarebytes report, its date, the listed domains, the Security Boulevard quotes and the recovery advice all matched their sources. The review also found that the guide contains 2025 samples, which weakens the page's 'since August 2026' framing, and that on-chain tracing is missing (high-priority gap). These are correctable, so the page needs revision rather than a larger penalty.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-10,"sequence_num":2,"severity_override":{"applied":false,"band":null,"from_band":"minor","reason":"The material omission (2025 AMLBot-impersonation samples predating the August 2026 report) comes from the same PCRisk dating error already counted in claim_findings[2] and [3], and it can be fixed with one text edit. The core claims about the Malwarebytes report, domains, mechanics and guidance are confirmed, so the percentage band is kept."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}