Skip to main content
Sign in
← 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 · Raydium AMM
View on Solana ↗
Sequence
#3
Score
45 → 62 (+17)
Cluster
mainnet-beta
Slot
426514638
Off-chain at
2026-06-14T23:16:06.317Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
CHNyVEdU6SBrfFLnKaPmYfbj5QTAb4wUDunYvEHNBnfF
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1560 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:06.214Z","decision":"review_approve","investigation_id":"3bdbd8f5-9034-4441-abcc-78a0ea81e843","new_score":62,"page_slug":"raydium-amm","prev_score":45,"reason":"This is a severity-calibration review, not a factual dispute review. All six claim findings (claim_findings[0]–[5]) are supported; disputed_pct is 0%. The reviewer (confidence 0.88) confirms Raydium is a legitimate, multi-year-operating DeFi protocol — the largest AMM on Solana — that suffered an external hack in December 2022 caused by third-party malware compromising an admin VM key, not by protocol fraud or insider misconduct. The protocol responded with a multisig migration the following day, executed full LP compensation through a DAO governance vote by May 2023, removed the vulnerable admin parameters from AMM V4, and has maintained an active Immunefi bug bounty program that caught a critical vulnerability in January 2024 with zero funds lost. The current WARNING band (score 45) is inconsistent with this documented remediation and continued legitimate operation at $1.8B+ TVL. A positive score delta of +17 is warranted to move the score to 62 (CAUTIONARY), which appropriately acknowledges the historical hack, pseudonymous team structure, and a recently-emerged legacy V3 exploit as material but resolved or non-fraudulent factors. The page content is accurate and must remain published.","score_delta":17,"sequence_num":3,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}