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 · Raydium AMM
- Sequence
- #2
- Score
- 45 → 45 (0)
- Cluster
- mainnet-beta
- Slot
- 426514636
- Off-chain at
- 2026-06-14T23:16:06.264Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AQYFBujkhH9GK5RszRUSWpAF2u2HZYahp7UtbXGBef9r
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1938 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:16:06.214Z","decision":"review","investigation_id":"3bdbd8f5-9034-4441-abcc-78a0ea81e843","new_score":45,"page_slug":"raydium-amm","prev_score":45,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. Raydium is a legitimate, multi-year-operating DeFi protocol — the largest AMM on Solana by volume — that suffered an external hack in December 2022 when a trojan virus compromised an admin private key on a virtual machine. The incident was caused by an outside attacker, not by protocol fraud or insider misconduct. Raydium responded within hours (multisig migration December 17), executed full LP compensation (claim portal January–May 2023), upgraded the AMM program to remove the vulnerable admin parameters, and maintained a live Immunefi bug bounty program that successfully caught a critical CLMM vulnerability in January 2024 with no funds lost. As of Q2 2025 the protocol holds $1.8B+ TVL and $51.9B quarterly volume. The current WARNING band (score 45) is inconsistent with the page's own text, which documents thorough remediation and continued legitimate operation. Under post-policy semantics, WARNING is reserved for entities with elevated fraud/loss risk or unresolved severe incidents; here the December 2022 incident is fully resolved with compensation paid and security architecture improved. The appropriate band is CAUTIONARY (50–69), acknowledging the historical hack, pseudonymous team structure, and a newly-emerged June 2026 legacy V3 exploit ($1.34M, covered by treasury) as material but non-fraudulent caveats. A score of 62 reflects legitimate operation with documented historical incidents that are substantially resolved.","score_delta":0,"sequence_num":2,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}