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
- Sequence
- #2
- Score
- 0 → 0 (0)
- Cluster
- mainnet-beta
- Slot
- 443561252
- Off-chain at
- 2026-09-02T00:36:45.324Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EsibPPB773eSQRtCPKVr9UwWF1UQCLCVJtzZf4ExKGxU
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1334 chars)
{"actor":"reviewer","artifact_identity":"69cd18d6fc7a4248c829da7a484208a1","decided_at":"2026-09-02T00:36:45.243Z","decision":"review","disputed_pct":0,"investigation_id":"5b4fd7aa-6d72-461c-85a1-2f6ba4c78a25","new_score":0,"page_slug":"superior-browser-extension-campaign-wallet-drainer","prev_score":0,"reason":"The page's claims are extensively and independently corroborated by the Socket Security primary research post and at least six independent secondary outlets, including verbatim confirmation of highly specific technical details (declarativeNetRequest CSP stripping, AES-GCM/SHA-256 key derivation, named C2 domains, and Cloudflare Worker endpoints). The only softness found was in the completeness of the 14-item 'created clean' extension name list, where several names could only be indirectly corroborated via matching C2 domain-naming patterns rather than direct secondary-source confirmation of every individual name. No contradictions, stale claims, or dead links were found among the sources checked, though one lower-tier source (cyberpress.org) could not be rendered by the fetch tool despite being confirmed to exist and match the page's claims via search-index content.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}