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
- 30 → 30 (0)
- Cluster
- mainnet-beta
- Slot
- 443519304
- Off-chain at
- 2026-08-26T05:06:01.269Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- E6ownsDX7Rv4sSoQ4p5aUx5Fs3HPXsaM2tRdt9Qy17vT
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1207 chars)
{"actor":"reviewer","decided_at":"2026-08-26T05:06:01.065Z","decision":"review","investigation_id":"f0b8d42e-a7c3-4496-9ac1-4b897646124e","new_score":30,"page_slug":"predatory-sparrow-gonjeshke-darande","prev_score":30,"reason":"The page is substantially well-sourced and its central factual claims about Predatory Sparrow's operational history and the 2025 Nobitex/Bank Sepah attacks were independently corroborated. Its treatment of the contested Israel-state-sponsorship question is notably careful -- it correctly preserves the hedged, unsubstantiated status of the Unit 8200 link rather than upgrading it to a confident attribution, unlike comparable pages reviewed in this batch. The main weaknesses found are a flat, uncaveated presentation of the self-claimed but technically unproven January 2022 IRIB attack (its cited source does not actually support the claim), a minor numeric slip in the Meteor wiper's configuration-parameter count, and the absence of any pointer to AVOID.NET's own more detailed related pages on the Nobitex hack and OFAC sanctions.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}