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
- #3
- Score
- 2 → 0 (-12)
- Cluster
- mainnet-beta
- Slot
- 443516967
- Off-chain at
- 2026-08-25T19:40:53.661Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- EqFMnnsi9zRXwf8LVZs2Mh9AHUiDKWt3bybyCm4KHZ3P
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2215 chars)
{"actor":"judge","decided_at":"2026-08-25T19:40:53.458Z","decision":"review_revise","investigation_id":"5566a9ec-65a2-4c42-a2f4-af1d01a2beee","new_score":0,"page_slug":"fifa-world-cup-2026-crypto-phishing-and-typosquatting-infrastructure","prev_score":2,"reason":"Counting the reviewer's own claim_findings array (26 entries, not the 27 stated in its summary block) gives 17 confirmed, 3 partially_supported, 2 unverifiable, and 4 disputed, for a disputed_pct of (4+2)/26 = 23.1% under the spec's disputed-plus-unverifiable formula -- not the 22% the reviewer's summary reported. That places the page in the 10-30% band, warranting revision rather than approval or denial. The page's central facts hold up well: domain-count statistics, the FBI PSA, the GHOST STADIUM technical profile, victim/loss estimates, and the treatment of FIFA, AFC, and Al Nassr as victims rather than wrongdoers are all confirmed against primary sources (claim_findings[1], [2], [3], [4], [5], [6], [9], [12], [13], [24], [25]). However, three disputed claims involve real-seeming facts attributed to sources that do not contain them -- GHOST STADIUM's payment-channel details, the 'World Cup Coin DApp' kit, and the WCUP token (claim_findings[15], [21], [22]) -- which is a citation-integrity problem on a platform built around sourced evidence, even though the underlying facts appear to be true elsewhere. A fourth disputed claim (claim_findings[10]) asserts GHOST STADIUM was 'first observed' in November 2025, which contradicts the page's own timeline entry dating first observation to August 2025 and is not stated in either cited source. Two additional claims (registration-pace figures and a '14 hosting IP nodes' figure, claim_findings[7] and [11]) could not be verified in the cited reporting. The two high-priority coverage gaps are warranted on their merits since they map directly to these same citation-mismatch and date-inconsistency findings rather than raising new concerns, and the reviewer's own confidence (0.78) is high enough not to warrant softening the response further.","score_delta":-12,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}