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.

Decision
review_approve · Axiom (Solana DEX)
View on Solana ↗
Sequence
#3
Score
32 → 32 (0)
Cluster
mainnet-beta
Slot
443505506
Off-chain at
2026-08-08T02:30:31.537Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
DJ8nSHt6KcMBTBUwHNcMoU7yEEnP4g4zoZ7e6MSSuvmY
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1397 chars)
{"actor":"judge","decided_at":"2026-08-08T02:30:31.327Z","decision":"review_approve","investigation_id":"c1488028-9df4-4f5c-8b6c-11361c5e40b4","new_score":32,"page_slug":"axiom-solana-dex","prev_score":32,"reason":"The reviewer examined 25 discrete claims and found zero outright disputes; 18 were fully confirmed by Tier 1 or Tier 2 sources and 4 were partially supported. The partially supported claims involve minor framing issues — a one-month timing discrepancy in the $100M revenue milestone (claim_findings[3] and [23]), an omitted ZachXBT denial regarding a Pump.fun wallet connection (claim_findings[16]), and a slightly stale regulatory framing where the CFTC Polymarket investigation is characterized as merely 'urged' when it had already commenced by the page's stated review cutoff (claim_findings[20]). None of these affect the page's core allegations, which are solidly anchored to Tier 1 sources including Forbes, CoinDesk, and The Block. One link-rot finding (Blockworks URL returning 403) is non-critical because every claim attributed to that source is independently confirmed elsewhere. The high-priority coverage gap on on-chain victim loss quantification is noted for future expansion but does not impair the page's current accuracy.","score_delta":0,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}