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 · Thorchain DEX
- Sequence
- #5
- Score
- 14 → 28 (+14)
- Cluster
- mainnet-beta
- Slot
- 426514840
- Off-chain at
- 2026-06-14T23:16:16.743Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- AvHVjo3h2FdDKQUVDk7TxMCJ7pvBSmFuq894UzTHZFzY
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (1610 chars)
{"actor":"judge","decided_at":"2026-06-14T23:16:16.640Z","decision":"review_approve","investigation_id":"05cd7768-ea55-47f0-a1ae-da562e54f3a7","new_score":28,"page_slug":"thorchain-dex","prev_score":14,"reason":"All six claim findings in the review are supported with zero disputed claims (claim_findings[0]–[5]). The review establishes that THORChain is a legitimately operating DeFi protocol with $68M+ TVL and $118B in cumulative volume, and that the current CRITICAL band score of 14 is miscalibrated: the 2021 ETH Router exploits were external attacks suffered by the protocol (claim_findings[1]); the $1.2B Lazarus laundering was third-party criminal abuse of an open permissionless system, albeit with a governance negligence component (claim_findings[2]); the THORFi $200M insolvency reflects design-flaw mismanagement characterized even by sophisticated observers as a restructuring rather than an exit scam (claim_findings[3]); and the May 2026 $10.8M vault breach was caused by a malicious external validator (claim_findings[4]). The CRITICAL band requires evidence of fraud or scam mechanics by the entity itself (claim_findings[5]), which is absent here. The page content is accurate and must remain published. A score of 28 (WARNING band) correctly reflects elevated risk from recurring security incidents, governance failures, ongoing legal action, and OFAC exposure — without conflating suffered incidents and third-party abuse with first-party fraud.","score_delta":14,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}