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 · Axiom
- Sequence
- #4
- Score
- 17 → 17 (0)
- Cluster
- mainnet-beta
- Slot
- 426514776
- Off-chain at
- 2026-06-14T23:16:13.646Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- 2bckqUr5NbyqyL2K7PC6aRD4tRTg4FHaxHT5tFTAd9Xp
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2012 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:13.586Z","decision":"review","investigation_id":"7f4d6a96-ca13-4a3b-b7d2-a1e568a9f840","new_score":17,"page_slug":"axiom","prev_score":17,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Axiom (axiom.trade) is a legitimate, operational, Y Combinator-backed non-custodial Solana trading platform that does not meet the CRITICAL band's threshold of 'evidence of fraud/scam.' The scoring error is a mis-attribution of employee misconduct to the entity itself. The confirmed facts are: (1) an employee named Broox Bauer allegedly abused internal 'God mode' dashboard access to surveil user wallets over approximately 10 months; (2) ZachXBT published allegations on February 26, 2026; (3) Axiom removed the tools and initiated an investigation; (4) the platform remained fully operational through June 2026. Critically, ZachXBT himself acknowledged difficulty establishing high-confidence proof of actual profitable trades without internal logs — the documented wrongdoing is data access abuse by one employee, not company-directed fraud. The phishing domains cited as evidence are third-party attacks on Axiom's brand, not Axiom's own activity. The Polymarket anomaly involved wallets that knew the ZachXBT target in advance, which implicates insiders or leaks but does not constitute proof that Axiom's corporate leadership directed fraud. Under the post-policy band semantics, WARNING (20-49) correctly describes a legitimate operator with an unresolved material incident — inadequate access controls, one employee's verified data abuse, and unresolved trust questions. A score of 32 reflects the seriousness of the governance failure and unresolved status while correctly placing Axiom above the fraud/scam threshold.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}