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 · THORChain
View on Solana ↗
Sequence
#5
Score
23 → 52 (+29)
Cluster
mainnet-beta
Slot
426514272
Off-chain at
2026-06-14T23:15:47.612Z
Anchored at
—
Block time
—

Independent verification

1. Database (off-chain)
3f6EYhnAYdKHMNVwFFzWeY1F11mqfvzR9nKMeFh9DPSo
2. Recomputed (your browser)
computing…
3. On-chain (Solana memo)
fetching…
Canonical bytes hashed (1742 chars)
{"actor":"judge","decided_at":"2026-06-14T23:15:47.502Z","decision":"review_approve","investigation_id":"a6babef8-9ac8-4d4f-a604-63d5d1c488a5","new_score":52,"page_slug":"thorchain","prev_score":23,"reason":"The calibration review (reviewer confidence 0.82) found 0% disputed claims across all six claim_findings — every factual assertion on the page is supported by credible sources including CoinDesk, TRM Labs, Halborn, SlowMist, Blockworks, and MIT Technology Review. The current score of 23 (WARNING band) was over-penalized because the scoring model attributed third-party harms — Lazarus Group's $1.4B Bybit laundering through THORChain (claim_findings[3]) and KelpDAO routing (modifier_flags[1]) — directly to the entity rather than recognizing them as permissionless-infrastructure abuse; the page itself documents that developers attempted to block Lazarus flows but were overruled by node vote. The deepfake incident (modifier_flags[2]) was suffered by the co-founder personally and does not reflect entity negligence. The one area of genuine entity culpability — the ThorFi $200M insolvency (claim_findings[2]) — was resolved via TCY debt-to-equity restructuring (Feb 2 2025), and the 2026 GG20 exploit (claim_findings[4]) has an ADR-028 recovery plan approved May 27 2026 with v3.19.0 patch deployed. THORChain is a live, operating protocol, not a fraud or exit; a CAUTIONARY score of 52 correctly reflects material historical incidents and ongoing illicit-use exposure without conflating third-party abuse with entity fraud. Page content stands; only the trust-score band is corrected.","score_delta":29,"sequence_num":5,"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}