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.
- Sequence
- #6
- Score
- 3 → 3 (0)
- Cluster
- mainnet-beta
- Slot
- 463281135
- Off-chain at
- 2026-10-30T12:13:59.544Z
- Anchored at
- 2026-10-30T12:14:01.000Z
- Block time
- 2026-10-30T12:14:01.000Z
Independent verification
- 1. Database (off-chain)
- DrzAv9vK48zL3sPKZQkZ8mvs4CuBm3JFkjQ9ehRKFnK5
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1578 chars)
{"actor":"reviewer","artifact_identity":"faad91f08feb447772954a8919bdc177","decided_at":"2026-10-30T12:13:59.443Z","decision":"review","disputed_pct":0.0769,"findings_hash":"2uxKF5GKZfzN24qk64FF7iKsiBHTKh7TbYTmCuErqGWt","investigation_id":"643728b0-3635-4fe2-98f3-9b1adc3107f5","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":3,"omissions":{"material":0,"total":1},"page_content_hash":"7f9c6286b2443197ede5d7801ad7270438015442ff8089ae6477ebed1f2a1e1f","page_slug":"cryptojs-ill-bloom-weak-rng-multi-wallet-drain-cve-2026-71851","prev_score":3,"reason":"The core facts are well supported by The Hacker News, CVEReports and illbloom.org: the $5.69M lower-bound losses, 2,114 addresses, the May 27 and second-wave figures, the five wallets with patch status, and the CVSS 9.0 score. The one real discrepancy is the crypto-js 4.0.0 release date. The page says May 2020 and attributes it to The Hacker News, which says February 2020, while CVEReports says May 1, 2020. A few claims are thinly sourced: the Solana chain listing, the claim that new vulnerable wallets were still being created, and the Coinspect blog page cited for details it does not contain. I found no critical omissions. The review rests mainly on secondary reporting.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"sequence_num":6,"subject_status":"exploited","subject_status_contradicts_page":false,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}