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
- 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. - 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.
- 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
- Sequence
- #5
- Score
- 17 → 32 (+15)
- Cluster
- mainnet-beta
- Slot
- 426514785
- Off-chain at
- 2026-06-14T23:16:13.701Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- A6fgzmQ3wp4vUq4L2zkLHfLkrtzPrBJta6qBsNKLhuWh
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1573 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:13.586Z","decision":"review_approve","investigation_id":"7f4d6a96-ca13-4a3b-b7d2-a1e568a9f840","new_score":32,"page_slug":"axiom","prev_score":17,"reason":"This was a severity-calibration review with 0% disputed content — all six claim findings (claim_findings[0] through claim_findings[5]) were confirmed supported. The current score of 17 (CRITICAL band) is miscalibrated because it conflates third-party phishing attacks on Axiom's brand (claim_findings[4]) with Axiom's own conduct, and because it treats ZachXBT's explicitly-qualified allegations — which ZachXBT himself acknowledged could not be proven to a high-confidence standard without internal logs (claim_findings[2]) — as equivalent to confirmed company-directed fraud. The documented incident is employee misconduct by one named individual (Broox Bauer), not a corporate fraud operation. Axiom responded as a victim, removed the implicated tools, and remained fully operational through June 2026 with $73M–$427M daily volume (claim_findings[3]). No regulatory enforcement, criminal charges, or company-directed fraud has been established (claim_findings[5]). A WARNING score of 32 correctly reflects the seriousness of the governance failure and unresolved trust questions without misclassifying a legitimate YC-backed operator as a fraud or scam. A positive delta of +15 is warranted to move the score from 17 to 32.","score_delta":15,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}