Version history
Every immutable snapshot of THORChain. A new version is saved each time the page changes, with the reason it changed. Pick two versions to see exactly what changed.
- v8currentTrust score: 362026-10-30 11:43:58Z
Community evidenceA moderator accepted a piece of community-submitted evidence: crypto.news (Sept 28, 2026) reports THORChain declined Bitget's request to block addresses tied to the ~$387.5M hack, citing its halt mechanism, with GoPlus disputing the stance. Matches the note. Trust score now 36.
hash: FnHk5MPam9Y7…changes from v7 - v7Trust score: 392026-10-30 07:44:53Z
Community evidenceA moderator accepted a piece of community-submitted evidence: CoinDesk confirms THORChain declined Bitget's request to block hacker addresses while the attacker swapped ~$6.3M of ETH for BTC through it, matching the note. Trust score now 39.
hash: 6dULhfeLe6zU…changes from v6 - v6Trust score: 412026-10-27 07:00:04Z
Fact-check reviewFact-check review (verdict: revise): the reviewer checked the page's claims against its sources; the trust score did not change.
hash: 02d33c2d789a…changes from v5 - v5Trust score: 412026-10-26 18:35:54Z
Re-researchedRe-researched in full by the investigator agent; the text was rewritten from new research.
hash: 02d33c2d789a…changes from v4 - v4Trust score: 412026-10-26 18:35:54Z
Before rewriteThe page as it stood just before it was rewritten; the next version says why.
hash: 50a270b16d9a…changes from v3 - v3Trust score: 412026-10-16 16:29:15Z
Community evidenceA moderator accepted a piece of community-submitted evidence: TRM Labs confirms ~$175M in KelpDAO-stolen ETH was swapped to BTC mostly via THORChain as part of a pattern of North Korean heists routing through the protocol, and quotes THORChain's FAQ refusing to freeze transactions from known illicit actors. Trust score now 41.
hash: 5h7AubCYRrJr…changes from v2 - v2Trust score: 422026-10-10 18:50:41Z
Score recalculatedRescored under Scoring v2, the published formula (avoid.net/scoring): 52 → 42. Problems weighed by who is responsible: incidents the subject suffered −20, concerns that are not fraud −19.2, problems around the subject, caused by others −0.3; legitimacy credit long-running +10; the penalty for incidents it suffered is capped at 20; a recent unresolved incident −4.3; fact-check adjustments (+24) now shown as page reliability, not in the score.
hash: 697439a29025…changes from v1 - v1Trust score: 522026-10-10 18:50:41Z
Before rewriteThe page as it stood just before its Scoring v2 rescore; the next version says why.
hash: 80b0a242b518…