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
2 → 2 (0)
Cluster
mainnet-beta
Slot
443521881
Off-chain at
2026-08-26T18:06:05.500Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
Ewp4GMa9JvxWd7EQJ7BPHE43R7Zi7Weba9X66Zb5bAZE
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2445 chars)
{"actor":"judge","decided_at":"2026-08-26T18:06:05.166Z","decision":"review_approve","investigation_id":"d53822ee-03b7-4da0-b084-f276cf7f263d","new_score":2,"page_slug":"wojtek-kulisz-merry-sim-swap-crypto-theft-ring","prev_score":2,"reason":"Of 27 extracted claims, the reviewer confirmed 25 and found 2 partially_supported, with zero disputed and zero unverifiable — a disputed_pct of 0%, computed per the reviewer's own (disputed + unverifiable) / total formula, which places this page squarely in the approve band with no room for a negative score adjustment. On the highest-risk element of the page — naming a living, unconvicted person — the review confirms the page consistently attributes the identification to ZachXBT rather than authorities (claim_findings[0]), does not upgrade 'charges presented' into an indictment (claim_findings[12], with the reviewer independently checking that no akt oskarżenia exists), grounds the 'organized group' framing in an actual formal charge (claim_findings[10]), and explicitly states no prior criminal history has been surfaced for the individual (claim_findings[20]) — the reviewer flags this as the opposite of, and more defensible than, a companion AVOID.NET page. The two partially_supported findings are minor: the page's summary compresses the charge description and drops the 'theft' element that its own body section states correctly (claim_findings[4]), and a general claim about ZachXBT's track record, while true, isn't backed by the specific citations attached to it (claim_findings[21]). One citation (mexc.com) returns HTTP 410 but is redundant to two other live sources on the same claim (claim_findings[18]), so it does not affect claim support and was correctly excluded from the link_rot tally. The review's most significant finding — a high-priority coverage gap describing an unrelated, unlinked sibling page about the same person that itself asserts an unsupported prior-criminal-history claim and an un-hedged loss figure — is a defect in that other page's content, not in this one; nothing in this page's own claims is disputed by it, and the judge output schema has no mechanism to merge, cross-link, or otherwise act on a different page's record, so it is preserved below for human follow-up rather than used to penalize this page.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}