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
#3
Score
10 → 10 (0)
Cluster
mainnet-beta
Slot
443519048
Off-chain at
2026-08-26T05:03:44.279Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
65oX7yRLeux5CN5mJh6SLAAUpAG2vz5HiQ47WLyvptNM
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1732 chars)
{"actor":"judge","decided_at":"2026-08-26T05:03:43.952Z","decision":"review_approve","investigation_id":"2a2f5726-bb6d-4493-bff8-e494673c7456","new_score":10,"page_slug":"nobitex-june-2025-hack-predatory-sparrow","prev_score":10,"reason":"An independent fact-check examined all 33 verifiable claims on this page and found 27 confirmed, 3 partially supported, 1 disputed, and 2 unverifiable. Counting only disputed and unverifiable claims against the total (per the review methodology), the disputed share comes to about 9%, just under the 10% threshold that would trigger required revisions. The single confirmed defect is narrow in scope: a vanity address the page labels as being on 'an EVM chain' is identified in other reporting as a Dogecoin address (claim_findings[11]) — a specific but low-stakes labeling error that does not touch the page's core allegations. The two unverifiable items concern peripheral geopolitical color (an unattributed Iranian government characterization and a Central Bank directive, claim_findings[16] and claim_findings[29]) rather than claims about the exchange's own conduct, and the reviewer could not locate a source either way. The page's central claims -- the June 18, 2025 hack date, the $90 million in destroyed funds, the hedged attribution of the hack to Predatory Sparrow and of that group to Israeli operatives, and the June 2026 OFAC sanctions -- are all independently confirmed by tier-1 and tier-2 sources, and the review found no evidence of overstated attribution or dropped source hedging of the kind flagged on related pages in this run.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}