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
- #6
- Score
- 21 → 21 (0)
- Cluster
- mainnet-beta
- Slot
- 459468395
- Off-chain at
- 2026-10-21T02:49:34.005Z
- Anchored at
- 2026-10-21T02:49:59.539Z
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EDSS3Pohkt6xtcW6MeBT1nefg1KLp1Jcq3xdZggphhWq
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1934 chars)
{"actor":"reviewer","artifact_identity":"ac64073b2c75651bb22c77351a202c3a","decided_at":"2026-10-21T02:49:33.775Z","decision":"review","disputed_pct":0.1429,"findings_hash":"CqSbfWjapRSFY8T1NDHFdqUZ6eEafKRn1kQETbaURk5H","investigation_id":"f0b8d42e-a7c3-4496-9ac1-4b897646124e","mode":"findings_only","new_score":21,"page_content_hash":"341542a6cf59ba3951058bc0029fbf7c8fe267c9d3bc20b0e99fb565482eb20b","page_slug":"predatory-sparrow-gonjeshke-darande","prev_score":21,"reason":"The page's central claims about Predatory Sparrow's documented operations — the 2021 railway and fuel attacks, the 2022 steel mill attacks, the December 2023 gas-station attack, and especially the June 2025 Bank Sepah and Nobitex crypto operations (the $90M figure, vanity-address burn mechanism, Elliptic/Chainalysis/Crystal sanctions-exposure estimates, and the June 2026 OFAC designation of Nobitex plus three other exchanges) — all check out against the page's own cited primary sources and independent reporting. Two concrete defects were found: a technical detail (Meteor wiper's config file parameter count, stated as 23 but actually 22 per the cited SentinelLabs report) is disputed, and one timeline-adjacent source record (the Times of Israel steel-plants archive_url) points to an unrelated, mismatched Wayback snapshot and should be replaced. One claim (the CCDCOE 'Scenario 12/18' attribution) could not be verified because the cited site was unreachable throughout this review. The attribution-to-Israel claims are consistently and appropriately hedged throughout as unconfirmed/widely-assessed rather than stated as fact, which matches the state of public reporting. The single accepted community submission is a redundant URL to an already-cited, verified source and contains no injection attempt.","score_delta":0,"sequence_num":6,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}