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 · THORChain
- Sequence
- #4
- Score
- 23 → 23 (0)
- Cluster
- mainnet-beta
- Slot
- 426514270
- Off-chain at
- 2026-06-14T23:15:47.556Z
- Anchored at
- —
- Block time
- —
Independent verification
- 1. Database (off-chain)
- GBZsut7Q4vPaChsPiooGn6YeCRsyfbiJcyXEYdaSF3ss
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2075 chars)
{"actor":"reviewer","decided_at":"2026-06-14T23:15:47.502Z","decision":"review","investigation_id":"a6babef8-9ac8-4d4f-a604-63d5d1c488a5","new_score":23,"page_slug":"thorchain","prev_score":23,"reason":"Blue-chip calibration review (Prompt A). Verdict: over-penalized. Page content is treated as accurate; the trust_score band is miscalibrated. THORChain is a legitimate, operating DeFi protocol that does not meet the definition of fraudulent, scam, Ponzi, or exit. The incidents driving the 28/WARNING score fall into three distinct categories: (1) security exploits suffered by the protocol (2021 hacks totaling ~$13M, 2026 GG20 hack at $10.7M) — these are harms done TO the entity; (2) genuine operational negligence in the ThorFi lending product, which created a $200M insolvency that required debt restructuring — this warrants a real deduction; and (3) third-party abuse by Lazarus Group and other hackers who used the protocol's permissionless design to launder stolen funds — THORChain earned fees from this activity but did not initiate or plan the hacks. The page's own timeline documents that developers attempted to block the Bybit laundering but were overruled by node vote, and that ADR-028 governance passed and recovery is underway post-2026 exploit. Under AVOID.NET's post-policy band semantics, WARNING (20-49) is reserved for elevated fraud/loss risk or unresolved severe incidents. The 2025 debt crisis was resolved via TCY restructuring; the 2026 exploit has a governance-approved recovery plan and security patch. The ongoing concern is the permissionless design that makes THORChain a preferred money laundering rail — a real, documented risk but not entity fraud. A score of 52 in CAUTIONARY (50-69) reflects a legitimate protocol with material, partially-resolved incidents and a serious ongoing illicit-use risk that a sophisticated user should understand before interacting with the protocol or its token.","score_delta":0,"sequence_num":4,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}