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
- 10 → 10 (0)
- Cluster
- mainnet-beta
- Slot
- 443519021
- Off-chain at
- 2026-08-26T05:03:44.167Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- A3frtDtppwfTL1W2nn7mv3QrJgPxjNmJkLL9x6ohStLx
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1234 chars)
{"actor":"reviewer","decided_at":"2026-08-26T05:03:43.952Z","decision":"review","investigation_id":"2a2f5726-bb6d-4493-bff8-e494673c7456","new_score":10,"page_slug":"nobitex-june-2025-hack-predatory-sparrow","prev_score":10,"reason":"The page's core narrative -- date, dollar figures, vanity-address burn mechanism, source code leak, attacker attribution hedging, prior illicit-finance allegations, and the June 2026 OFAC sanctions -- is well supported by the cited tier-1/tier-2 sources and independently corroborated. The most significant defect found is a specific factual error mislabeling a Dogecoin vanity address as belonging to 'an EVM chain.' Attribution of the hack to Predatory Sparrow, and of Predatory Sparrow to Israeli state operatives, is appropriately hedged rather than asserted as fact, and the June 18, 2025 date matches the weight of contemporaneous reporting. A handful of secondary claims (ZachXBT's exact chain scope, an Iranian government quote, a Central Bank directive, and one named terror-group affiliation) could not be independently traced to the cited sources.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}