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_revise · THORChain
- Sequence
- #10
- Score
- 41 → 41 (0)
- Cluster
- mainnet-beta
- Slot
- 461977926
- Off-chain at
- 2026-10-27T07:00:04.668Z
- Anchored at
- 2026-10-27T07:00:10.000Z
- Block time
- 2026-10-27T07:00:10.000Z
Independent verification
- 1. Database (off-chain)
- 62DDZrCXWspdfCTErRhD3zszMkfafoyDbySkFAswjcRS
- 2. Recomputed (your browser)
- computing…
- 3. On-chain (Solana memo)
- fetching…
Canonical bytes hashed (2026 chars)
{"actor":"judge","artifact_identity":"d7dc6e455f7c944421db5af60c1ee128","band_override":null,"blocked_count":1,"decided_at":"2026-10-27T07:00:04.226Z","decision":"review_revise","delist_requested":false,"disputed_pct":0.1667,"investigation_id":"a6babef8-9ac8-4d4f-a604-63d5d1c488a5","judge_def_hash":"8800307026131ea9d5da939d32b9a1f1884b2b84a5de33c8e87931d36f38d0f8","new_score":41,"page_slug":"thorchain","prev_score":41,"reason":"Of 7 claim findings, 1 was excluded as source_blocked (live RUNE market data, claim_findings[5]). Of the remaining 6, 1 is unverifiable (claim_findings[6]), which gives a disputed share of about 17%. Two further findings are only partially supported: the $292M rsETH figure is the total exploit size, not the amount laundered through THORChain (claim_findings[0]), and the nine-chain count conflicts with CoinDesk and The Defiant, which report four (claim_findings[1]). The core account of the May 2026 exploit, the Bybit laundering and the Pluto resignation matched Tier 1 sources (claim_findings[2], [3]). The page also stops at the May 27 restart authorization and omits that trading resumed around June 23, 2026 (omission_findings[0]). That omission is why the penalty sits toward the upper end of the minor band.","reviewer_def_hash":"bc11388ce4bc4deea1b064fea362663ae06e3f4f687f99604769044d6ffba770","score_delta":0,"scored_claims":6,"sequence_num":10,"severity_override":{"applied":false,"band":null,"from_band":"minor","reason":"The material omission (trading resumed about June 23, 2026) is an outdated ending rather than a false statement. The page says only that a restart was authorized, which is accurate, and it does not claim the network is still halted. The reviewer's confidence is also moderate (0.55) and only a sample of sources was checked. The omission is handled by a larger penalty within the minor band and a request to add the outcome, not by a harsher band."},"submission_content_hash":null,"submission_id":null,"submission_kind":null,"submission_valence":null,"v":1}