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
443516984
Off-chain at
2026-08-25T19:46:01.392Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
F4PeTQuqR7ddKKNaj3kz6G6yxUmHJB3put6PEQFYxtJG
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1828 chars)
{"actor":"judge","decided_at":"2026-08-25T19:46:01.051Z","decision":"review_approve","investigation_id":"03c192ed-953c-4829-b6f7-e199e2fd5783","new_score":2,"page_slug":"oramama-x-war-panic-scam-network","prev_score":2,"reason":"Of 24 claims checked, 20 were independently confirmed, 3 were partially supported, 1 was unverifiable, and none were disputed, putting the disputed-plus-unverifiable rate at about 4% — well inside the approval range. Core facts (the size and mechanics of the account network, the Feb 22, 2026 $ORAMAMA promotion and abandonment pattern, the on-chain PumpSwap pool address, exact engagement figures, and verbatim ZachXBT quotes) were each corroborated across multiple independent outlets or on-chain data (claim_findings[0], [9]-[11], [21]). The 'coordinated network' framing was found to reflect ZachXBT's own stated conclusion rather than the page's own characterization (claim_findings[3]). The weaker points are narrow and non-central: an overly specific description of how the 'Wang Laurent' profile photo was produced (claim_findings[6]), an editorial four-step label for the account playbook that isn't a direct quote from any source (claim_findings[8]), an unattributed 'security researchers say' framing that no cited article actually supports (claim_findings[13]), and a claim that X's 'product leadership' responded to this specific case when the underlying source only offers generic background about platform policy (claim_findings[15]) — the last of these is also self-hedged in the same sentence. No citations showed link rot or staleness, and no coverage gap was flagged high priority, so none of these push the page out of the approve range.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}