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 · Superior Browser Extension Campaign — Wallet Drainer
- Sequence
- #6
- Score
- 2 → 0 (-8)
- Cluster
- mainnet-beta
- Slot
- 461980841
- Off-chain at
- 2026-10-27T07:10:17.657Z
- Anchored at
- 2026-10-27T07:10:30.000Z
- Block time
- 2026-10-27T07:10:30.000Z
Independent verification
- 1. Database (off-chain)
- 7gcNodfhrnhM7ig6VGibPSBEwhqqZJTqDVq63Nj4c6cB
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1386 chars)
{"actor":"judge","artifact_identity":"c378715fa62f4e70f32059a0196d4753","band_override":null,"decided_at":"2026-10-27T07:10:17.181Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.125,"investigation_id":"5b4fd7aa-6d72-461c-85a1-2f6ba4c78a25","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":0,"page_slug":"superior-browser-extension-campaign-wallet-drainer","prev_score":2,"reason":"The core claims hold up against Socket's primary report (claim_findings[0-3]: 19 extensions, 14/5 split, about 80,000 users, 16 modules, command-and-control infrastructure). Counting from the claim findings, 1 of 8 (12.5%) could not be verified: the six-month publication window and the 2024 DomainTools date (claim_findings[7]). Separately, the page overstates Chrome removals: Socket states only the flagship Chrome extension was removed, not all of them (claim_findings[4] and [5]). The 'remained active' wording is now dated (claim_findings[6]), and the reviewer flagged a high-priority gap on the current store status of all 19 extensions. No omissions or contradictory subject status were reported.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":-8,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}