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
14 → 8 (-6)
Cluster
mainnet-beta
Slot
443514260
Off-chain at
2026-08-25T13:15:41.720Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
C4MkLQRyr2AV1pV78gPms6Y6sA8vaaDr2wnG8MfUZeFm
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (2293 chars)
{"actor":"judge","decided_at":"2026-08-25T13:15:41.365Z","decision":"review_revise","investigation_id":"0424f0a7-d6b7-4f61-b3cd-ce14b46eda1c","new_score":8,"page_slug":"axiom-dex-insider-trading-broox-bauer","prev_score":14,"reason":"Recomputing disputed_pct from the reviewer's authoritative claim_findings array (33 entries: 27 confirmed, 5 partially_supported, 1 unverifiable, 0 disputed) gives (0 unverifiable/disputed-adjacent... actually (0 disputed + 1 unverifiable)/33 = 3.0%, placing this page well within the approve band on accuracy alone: no claim was contradicted, and the core allegation, timeline, named individuals, and on-chain figures are consistently corroborated across independent outlets (claim_findings[0]-[19]). However, one high-priority coverage gap is a genuine framing defect rather than a mere omission: claim_findings[22] finds the page's statement that the founders 'were not alleged to have had prior knowledge' reads as more exculpatory than ZachXBT's own agnostic language ('regardless of whether Cal or Mist were aware...'). This is a sourcing failure comparable in kind to overstating an accusation, and it should be corrected by attributing or hedging the framing rather than presenting it as settled. The second high-priority gap -- an unconfirmed, single-outlet, self-hedged on-chain trace linking Bauer's wallet cluster to the top Polymarket winner (claim_findings[28], coverage_gaps) -- is not treated as a defect: the source is low-credibility and explicitly disclaims confirmed ownership, and omitting a thinly-sourced self-dealing implication against an uncharged individual is editorial restraint consistent with this page's overall careful handling of unproven allegations, not a gap the page needed to fill. The page consistently labels the underlying claims as allegations, preserves ZachXBT's own caveat about lacking high-confidence front-running examples, and states plainly that no charges exist -- exactly the discipline expected of an accusation page about an uncharged person. That record, combined with a single correctable framing issue, warrants a light revise rather than approval or denial.","score_delta":-6,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}