Skip to main content
AVOID.NET
← avoid.net

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

  1. 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.
  2. 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.
  3. 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.

Sequence
#4
Score
0 → 0 (0)
Cluster
mainnet-beta
Slot
457732155
Off-chain at
2026-10-16T18:09:37.505Z
Anchored at
2026-10-16T18:09:53.221Z
Block time
—

Independent verification

1. Database (off-chain)
3YZUnQvEBtcoxnshL7HUEv8Rj5Rq4hCoqNSsGx6EASzv
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2140 chars)
{"actor":"reviewer","artifact_identity":"3d0f448da33f8dd1e21aa1d812bdb0d2","decided_at":"2026-10-16T18:09:37.192Z","decision":"review","disputed_pct":0.2,"findings_hash":"5vH4nHF9FUY6d71A5ndub9s2q4btDv1WhxM7Q7FPhNu8","investigation_id":"5566a9ec-65a2-4c42-a2f4-af1d01a2beee","mode":"findings_only","new_score":0,"page_content_hash":"fa5dd6507042dbe55edb3710207cf42f9066d1ff9e45d208f417ef240310fc21","page_slug":"fifa-world-cup-2026-crypto-phishing-and-typosquatting-infrastructure","prev_score":0,"reason":"The page's core statistics — domain counts (13,000+/19,000), the GHOST STADIUM cluster's scale, infrastructure fingerprints (SSO client_id, Meta Pixel IDs, registrars, registration waves), the FBI PSA, the Android trojans, infostealer volumes, and most of the crypto/memecoin narrative — are well supported by the cited vendor and news reporting and mostly check out against the primary sources directly. Three defects stand out: (1) a clear internal contradiction between the timeline (GHOST STADIUM 'first observed' August 2025) and the GHOST STADIUM section itself (November 2025, which is the figure independently corroborated); (2) a cluster of highly specific GHOST STADIUM payment-channel identifiers (an order ID format, a named Cash App handle, a Nequi phone number, an Alchemy Pay conversion rate) that appear in none of the four cited sources or in other adjacent reporting checked, raising a real fabrication concern; and (3) the Arctic Wolf AiTM claim, which broadens a narrow finding (corporate Google Workspace credential theft via fake FIFA hiring sites) into a sweeping claim about defeating 'all FIFA account MFA methods' including a fabricated Microsoft Authenticator detail, repeated in both prose and timeline. The WCUP memecoin claim is substantively accurate per independent reporting but is attached to sources that never mention it. Victim-count and breach-size figures in two places present Group-IB/other extrapolations as firmer than the underlying reports claim.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}