Governance & History
ADRs, Mimir context, milestones, incidents, and research. Vote percentages are shown only when source-backed.
Curated·Last verified 2026-07-13· 7 sources
retrieval details
+6 sources
retrieval details
retrieval details
retrieval details
retrieval details
retrieval details
retrieval details
Use this page for
- Source-backed ADR, Mimir, incident, milestone, and recovery-history context.
- Dated incident and governance records with explicit current-review labels.
Verify elsewhere before claiming
- Current node consensus, live Mimir values, active recovery status, or final governance outcome.
- That a historical incident record proves present-day network safety or solvency.
Continue From Here
Move from dated governance and incident records into current diagnostics, recovery review, or the historical recovery path before making present-tense claims.
Claim checks by type
Start with the claim type. Governance records are useful for dated decisions and history; live controls, incident root-cause wording, recovery status, and community interpretation need separate proof paths.
Operational Mimir claim
- Use For
- Whether trading, signing, LP actions, churning, TCY controls, or chain operations are active now.
- Verify
- Use Network diagnostics and current THORNode/Mimir evidence before using present-tense availability wording.
- Do Not Claim
- Do not infer live availability from a proposal, incident archive, milestone, or missing halt mention.
ADR or proposal status
- Use For
- What an ADR, proposal, milestone, or governance record said at the cited review point.
- Verify
- Use the record source, source-map guidance, and any linked live tracker before calling a design active.
- Do Not Claim
- Do not treat proposed, draft, needs-review, or historical records as final live protocol behavior.
Incident root-cause claim
- Use For
- Exploit cause, affected vault/chain scope, patch wording, migration context, and dated security lessons.
- Verify
- Use incident reports plus the Network Security path before summarizing safety or cryptographic details.
- Do Not Claim
- Do not convert a dated exploit report, restart, or patch into proof of present-day safety.
Recovery or solvency claim
- Use For
- Post-exploit recovery state, THORFi/TCY recovery framing, and records tagged for current review.
- Verify
- Use the current recovery tracker, TCY recovery timeline, dated upgrade notes, and live diagnostics together.
- Do Not Claim
- Do not claim final recovery, par redemption, current solvency, or product availability from one record.
Community sentiment claim
- Use For
- Debate topics, open questions, or how contributors described tradeoffs in community channels.
- Verify
- Use community sources only as context, then confirm protocol facts through official or live sources.
- Do Not Claim
- Do not present Discord chatter as canonical protocol proof or representative sentiment without sampling.
Current Incident & Recovery Tracker
Conservative tracker for records explicitly tagged as current or needing current recovery review. Historical unresolved records remain in the incident archive below unless they are re-verified for current tracking.
Show summary and claim-check detail
Tracked records
7
Current or needs-review records promoted from the full governance and incident archive.
Evidence path
Record + live check
Use the full dated record first, then current Network diagnostics before present-tense claims.
Check Before Claiming
Savers or Lending are available now
- Start with
- Archived feature sources
- Verify
- Official archived docs and any current interface/source claiming reactivation.
- Do not claim
- Do not describe archived mechanics as current deposit or borrowing instructions.
Check Before Claiming
A claimant can claim or stake TCY right now
- Start with
- TCY timeline plus live network diagnostics
- Verify
- TCY guide, official claim interface, and TCY Mimir controls such as TCYCLAIMINGHALT or TCYSTAKINGHALT.
- Do not claim
- Do not infer availability from historical TCY launch copy alone.
Check Before Claiming
TCY restored the original debt value
- Start with
- TCY source caveats
- Verify
- Market and distribution evidence outside this tracker; official developer docs say full recovery is not guaranteed.
- Do not claim
- Do not state par recovery, redemption value, or investment outcome as fact.
Check Before Claiming
Post-exploit recovery is complete
- Start with
- Current recovery tracker records
- Verify
- Dated exploit reports, upgrade notes, ADR/proposal status, and live network diagnostics.
- Do not claim
- Do not convert a restart, patch, or proposal into proof of final recovery completion.
Incident record
BTC Auto-Halt and Outbound Delays
Discord operator reporting describes an almost double-spent transaction and BTC auto-halt, not a successful double payment. September 29 reporting also identified outbound hashes not seen on Bitcoin.
Dated BTC interruption and delayed outbounds; resolution of every affected transaction was not established.
- Use This For
- Promoted recovery record that needs claim-specific review before present-tense wording.
- Verify Next
- - Open the dated record and source metadata.
- - Check current Network diagnostics and relevant product controls.
- - Look for newer official sources before claiming final recovery or user-action availability.
- Boundary
- Do not use tracker inclusion alone as proof of current safety, solvency, restitution, or product availability.
retrieval details
Incident record
GAIA Restart and Missed Observation
Operator reports describe the Cosmos Hub halt at 33086740, v28.3.0 restart, and an outbound settled on Gaia but not yet reflected in THORChain observation accounting.
Recovery required observation reconciliation; scanner healthy flags could conceal a frozen upstream daemon.
- Use This For
- Promoted recovery record that needs claim-specific review before present-tense wording.
- Verify Next
- - Open the dated record and source metadata.
- - Check current Network diagnostics and relevant product controls.
- - Look for newer official sources before claiming final recovery or user-action availability.
- Boundary
- Do not use tracker inclusion alone as proof of current safety, solvency, restitution, or product availability.
retrieval details
Incident record
App Layer Emergency Halt Request
A Discord operator request asked nodes to set HALTWASMGLOBAL=1 while investigating a potential App Layer issue. A separate signing-pause request was withdrawn later that day.
WASM halt requested; cause, loss amount and final unhalt were not established by this review.
- Use This For
- Promoted recovery record that needs claim-specific review before present-tense wording.
- Verify Next
- - Open the dated record and source metadata.
- - Check current Network diagnostics and relevant product controls.
- - Look for newer official sources before claiming final recovery or user-action availability.
- Boundary
- Do not use tracker inclusion alone as proof of current safety, solvency, restitution, or product availability.
retrieval details
Incident record
ZEC Readiness and Churn Blockers
After churning was enabled, operators reported inconsistent ZEC chain sets and keygen co-blaming preventing vault rotation.
Scanner enablement did not establish completed rotation or public ZEC trading availability.
- Use This For
- Promoted recovery record that needs claim-specific review before present-tense wording.
- Verify Next
- - Open the dated record and source metadata.
- - Check current Network diagnostics and relevant product controls.
- - Look for newer official sources before claiming final recovery or user-action availability.
- Boundary
- Do not use tracker inclusion alone as proof of current safety, solvency, restitution, or product availability.
retrieval details
Incident record
GG20 Vault Exploit
Exploit Report #2 describes a cryptographic GG20/TSS attack: a validator planted malformed Paillier key material and used repeated failed MTA rounds to leak key-share fragments before signing alone.
Approximately $10M-$10.7M drained from one vault; normal signing and fund movements resumed after v3.19.1 verification, while migration away from GG20 remains planned and current vault safety still needs live evidence.
- Use This For
- Dated official exploit, restart, patch, and migration context for the May 2026 GG20 vault incident.
- Verify Next
- - Network diagnostics for current halts, signing, route limits, and source warnings.
- - Security deep dives for the dated GG20/TSS attack scope and migration wording.
- - TCY controls only when the claim is about current claim, stake, distribution, unstake, or trade actions.
- Boundary
- Do not use the incident record, restart, or v3.19 notes as proof that recovery is complete, users are made whole, or present-day safety is guaranteed.
retrieval details
+4 sources
retrieval details
retrieval details
retrieval details
retrieval details
Incident record
Memoless Registration Pause — Historical Evidence Limits
The official 27 August episode recap reports that memo registrations were paused after a spam attempt. The v3.20.0 release separately lists memoless ERC-20 handler, refund-simulation and inbound-observation work. The original 21–26 August cohort dates are retained as an unverified authored range: exact halt/re-enable/re-halt transitions, MEMOLESSTXNCOST=200000, and HALTMEMOLESS=1 immediately after upgrade lack retained dated evidence.
The recap supports an attributed registration pause, not a verified five-day outage or uninterrupted ordinary swaps in the earlier windows. Those assertions are withdrawn pending historical receipts. Current availability needs a fresh source-qualified assessment. The 8 November 2026 readback still shows HALTMEMOLESS=1 and MEMOLESSTXNCOST=2000000; that is current state, not the missing historical sequence.
- Use This For
- August 2026 memoless halt, cost vote, spam re-halt, and v3.20.0-era feature work.
- Verify Next
- - Current HALTMEMOLESS and MEMOLESSTXNCOST values in Network diagnostics before any present-tense memoless claim.
- - The v3.20.0 release notes for dated handler, refund, and chain-client work.
- - Route quotes for concrete swaps; a memoless halt does not prove ordinary swap routes are blocked.
- Boundary
- This record proves a scoped availability cycle, not a global outage or a permanent fee level. Cost parameters can be re-voted after the incident window.
retrieval details
+1 source
retrieval details
Governance record
ADR-028 Recovery Path
ADR-028 is Accepted in the v3.19.0 source and specifies a one-time conciliation migration for exploit-created accounting gaps; that allocation decision is not proof that every loss was restored.
Accepted; implemented in v3.19.0
- Use This For
- Accepted ADR-028 decision and one-time v3.19.0 conciliation migration for the May 2026 exploit-created accounting gap.
- Verify Next
- - The immutable v3.19.0 ADR before describing its reserve, Saver, treasury, or stuck-swap allocation waterfall.
- - Current release and Network diagnostics before converting the historical migration into present protocol availability or safety.
- - TCY controls and official interface evidence before saying a user can claim, stake, trade, or receive distributions now.
- Boundary
- ADR-028 acceptance proves the conciliation decision and migration design, not that every loss was restored, recovery is complete, current vaults are safe, or any user action is enabled.
retrieval details
+3 sources
retrieval details
retrieval details
retrieval details
Dated Archive Map
Use the lane map before diving into the archive. Counts are navigation aids, not health scores, and every lane still needs the claim-specific checks above. Read each record or posture badge on its own terms before treating dated material as current protocol behavior.
Current recovery lane
Start here for records explicitly promoted from the archive into current recovery review.
- Archive mix
- promoted records
Governance records lane
Use for ADRs, operational parameters, recovery-path records, and historical unwind context.
- Archive mix
- 3 operational/current-only
Incident archive lane
Use for exploit root-cause, illicit-flow, and recovery-history records without flattening them into today.
- Archive mix
- 7 current/review, 2 historical-open
Research and milestones lane
Use for timeline context and third-party or ecosystem analysis before checking current evidence.
- Archive mix
- 10 milestones, 3 reports
Governance Records
Dated governance and operational records. The status badge describes the record evidence posture; use live diagnostics before turning it into a current action claim.
Edge Wallet and Symbiosis Dynamic Fee Enrollment
September 25 operator request to enroll ej and symbiosis through DYNAMICFEE-WHITELIST-EJ=1 and DYNAMICFEE-WHITELIST-SYMBIOSIS=1. The request does not prove activation; check current Mimir and pair records.
source retrieval details
THORFi Unwind
Deprecation and unwind process for Savers and Lending liabilities.
source retrieval details
+3 sources
retrieval details
retrieval details
retrieval details
ADR-028 Recovery Path
ADR-028 is Accepted in the v3.19.0 source and specifies a one-time conciliation migration for exploit-created accounting gaps; that allocation decision is not proof that every loss was restored.
source retrieval details
+3 sources
retrieval details
retrieval details
retrieval details
Operational Mimir Halts
Operational Mimir parameters such as HALTTRADING and HALTSIGNING can pause network activity and should be read from THORNode.
source retrieval details
+1 source
retrieval details
ADR-026 Dynamic L1 Fees
Implemented dynamic per-thorname and per-pair L1 minimum fee mechanism. Develop ADR status and merged August 12 documentation establish implementation history; current Mimir, affiliate eligibility, records, and revenue effects still require fresh evidence.
source retrieval details
+3 sources
retrieval details
retrieval details
retrieval details
ADR-030 Delegated Node Operator Permissions
Proposed per-node delegate registry for MAINT, LEAVE, bond-provider-whitelist, and set-fee permissions, with custody and delegation management retained by the operator. The v3.20 recap expected activation in v3.21. A September 28 Discord reminder reported 21 votes still needed and specified ADR030, not ADR30 or ADR-030; this dated tally does not prove current activation.
source retrieval details
+1 source
retrieval details
ADR-031 THORChain x Rujira Alignment
Official blog post reports that after the initial ADR-020 collaboration period expired, nodes voted on the future of the Rujira cooperation and selected Option 1, confirming and reinforcing it with an updated revenue split. Treat vote mechanics and any payout configuration as source-dated claims until protocol releases confirm them.
source retrieval details
Milestones
THORNode v3.21.1 to v3.21.3 Bifrost Patches
Bifrost-only patches followed the 3.21.0 upgrade. 3.21.1 and 3.21.2 shipped as private binaries with BTC, gossip, solvency, GAIA, XRP and EVM fixes; 3.21.3 added BASE 200ms block handling and a SOL durable-nonce fix. BASE trading stayed halted pending the coordinated 3.22.0 release because the scanning fix changes swap quotes.
retrieval details
+2 sources
retrieval details
retrieval details
THORNode v3.21.0 Upgrade
Operator notice placed the coordinated upgrade at block 28,366,100 and paused SOL, TRON and ZEC signing for a chain migration that must run with signing halted. After the first post-upgrade churn, BSC was to move to Router V6.1 (0x00dc6100103BC402d490aEE3F9a5560cBd91f1d4), with ETH following. This is a release notice, not fleet-adoption or current-router proof.
retrieval details
THORNode v3.20.3 Bifrost Patch Announcement
Operator announcement reports SOL v1 transaction support, blockhash re-signing, signing-height TSS policy, scanner recovery and whitelist startup fixes. Bifrost-only patch: consensus network version remains 3.20.0, with no upgrade height. Announcement is not fleet deployment proof.
retrieval details
Base Cobalt Operator Preparation Notice
Operator notice specifies Base node v1.4.2 for the September 30, 18:00 UTC Cobalt hardfork deadline. This dated notice does not confirm fleet upgrade completion or fork outcome.
retrieval details
THORChain Founded
A pseudonymous core team founded THORChain in 2018.
retrieval details
Multichain Chaosnet Launch
Multichain Chaosnet launches with native cross-chain swaps across five networks while safeguards remain in place on the path to mainnet.
retrieval details
THORNode v3.0.0 Release
THORNode v3.0.0 upgrades to Cosmos SDK v0.50 and lays groundwork for future App Layer functionality.
retrieval details
+1 source
retrieval details
Savers and Lending Deprecated
Official archived pages say Savers and Lending were permanently deprecated on January 4, 2025, are no longer available, and remain documented only for historical reference.
retrieval details
+1 source
retrieval details
GG20 Vault Exploit and Emergency Halt
Official reports say attackers drained roughly $10M from one vault after an upstream GG20/TSS cryptographic attack. v3.19.0 supplied emergency restart controls, v3.19.1 patched the incident class, and migration away from GG20 remained planned.
retrieval details
+3 sources
retrieval details
retrieval details
retrieval details
THORNode v3.20.0 Upgrade
The official v3.20.0 tag notes a proposed block of 27,580,000 on 25-Aug-2026, a private binary with security patches, the ADR-028 residual migration (Migrate17to18), TSS/Bifrost hardening, memoless ERC-20 work, and XMR/ZEC chain-client updates. The blog recap adds churn resumption prep, operational POL System Income and Asset Whitelist Mimirs, and an experimental Stable Reserve shipping disabled.
retrieval details
Security Incidents
Showing 11 of 11 incident records. Filter by posture before turning a dated incident into a current recovery or safety claim.
Ethereum Reorg Double Payout and Global Pause
ResolvedA one-block Ethereum reorg left a 10 ETH deposit observed and finalised even though it was not on the canonical chain. The quorum errata never formed, the automatic solvency halt fired and then lifted because the queued refund covered the gap, and the vault refunded both the unrecognised deposit and the real one. Core paused all chains as a precaution, then moved to chain-level halts. Vault ...dx7767 was briefly 10 ETH short; the recipient returned the funds in full the same day. The incident report said Bifrost and THORNode fixes would ship in the next release, and 3.21.1 followed on November 3. No signing-key compromise was reported.
Dated resolved incident record; still use current diagnostics for present-tense safety claims.
source retrieval details
+1 source
retrieval details
BTC Auto-Halt and Outbound Delays
Current trackerDiscord operator reporting describes an almost double-spent transaction and BTC auto-halt, not a successful double payment. September 29 reporting also identified outbound hashes not seen on Bitcoin. Dated BTC interruption and delayed outbounds; resolution of every affected transaction was not established.
Promoted to the current recovery tracker above; pair this dated record with live diagnostics.
source retrieval details
GAIA Restart and Missed Observation
Current trackerOperator reports describe the Cosmos Hub halt at 33086740, v28.3.0 restart, and an outbound settled on Gaia but not yet reflected in THORChain observation accounting. Recovery required observation reconciliation; scanner healthy flags could conceal a frozen upstream daemon.
Promoted to the current recovery tracker above; pair this dated record with live diagnostics.
source retrieval details
App Layer Emergency Halt Request
Current trackerA Discord operator request asked nodes to set HALTWASMGLOBAL=1 while investigating a potential App Layer issue. A separate signing-pause request was withdrawn later that day. WASM halt requested; cause, loss amount and final unhalt were not established by this review.
Promoted to the current recovery tracker above; pair this dated record with live diagnostics.
source retrieval details
ZEC Readiness and Churn Blockers
Current trackerAfter churning was enabled, operators reported inconsistent ZEC chain sets and keygen co-blaming preventing vault rotation. Scanner enablement did not establish completed rotation or public ZEC trading availability.
Promoted to the current recovery tracker above; pair this dated record with live diagnostics.
source retrieval details
ETH Router Exploit #1
ResolvedETH router/Bifrost exploit where an attack contract in front of the router caused fake ETH deposits to be read as real deposits. Approximately $8M impact; the post-mortem says no other chains or assets were affected.
Dated resolved incident record; still use current diagnostics for present-tense safety claims.
source retrieval details
ETH Router Exploit #2
ResolvedSecond ETH router exploit where a fake router and malicious deposit event path caused real ERC-20 refunds from the system. Approximately $8M across economically significant ERC-20 assets, followed by a broader recovery and audit plan.
Dated resolved incident record; still use current diagnostics for present-tense safety claims.
source retrieval details
THORFi Unwind
Historical open recordSavers and Lending were deprecated and moved to archived documentation after THORFi liability concerns. Deprecated Savers and Lending products; Proposal 6 and current TCY docs establish the recovery-token mechanics, but do not prove par recovery or that every claimant was made whole.
Kept in the archive as unresolved historical context; not promoted to current recovery status without re-review.
source retrieval details
+3 sources
retrieval details
retrieval details
retrieval details
Post-Bybit Laundering Flow
Historical open recordTHORChain saw controversial post-exchange-hack flow; this was not a THORChain protocol exploit. High-volume illicit-flow and interface-policy debate rather than a protocol drain.
Kept in the archive as unresolved historical context; not promoted to current recovery status without re-review.
source retrieval details
GG20 Vault Exploit
Current trackerExploit Report #2 describes a cryptographic GG20/TSS attack: a validator planted malformed Paillier key material and used repeated failed MTA rounds to leak key-share fragments before signing alone. Approximately $10M-$10.7M drained from one vault; normal signing and fund movements resumed after v3.19.1 verification, while migration away from GG20 remains planned and current vault safety still needs live evidence.
Promoted to the current recovery tracker above; pair this dated record with live diagnostics.
source retrieval details
+4 sources
retrieval details
retrieval details
retrieval details
retrieval details
Memoless Registration Pause — Historical Evidence Limits
Current trackerThe official 27 August episode recap reports that memo registrations were paused after a spam attempt. The v3.20.0 release separately lists memoless ERC-20 handler, refund-simulation and inbound-observation work. The original 21–26 August cohort dates are retained as an unverified authored range: exact halt/re-enable/re-halt transitions, MEMOLESSTXNCOST=200000, and HALTMEMOLESS=1 immediately after upgrade lack retained dated evidence. The recap supports an attributed registration pause, not a verified five-day outage or uninterrupted ordinary swaps in the earlier windows. Those assertions are withdrawn pending historical receipts. Current availability needs a fresh source-qualified assessment. The 8 November 2026 readback still shows HALTMEMOLESS=1 and MEMOLESSTXNCOST=2000000; that is current state, not the missing historical sequence.
Promoted to the current recovery tracker above; pair this dated record with live diagnostics.
source retrieval details
+1 source
retrieval details
Claim evidence (3)
The earlier August halt/re-enable/re-halt account remains unverified and is withdrawn as established chronology.
historical · needs-review · Authored August 2026 cohort; not current operations
Observed 2026-08-26; claim reviewed 2026-11-08; review due 2026-12-08.
THORNode v3.20.0 Release Notes (GitLab)The original observation and review dates identify the authored account, not verified transitions. The 7 October publication disposition withdraws its exact sequence, cost vote, duration and ordinary-swap availability assertions; retained dated evidence is still missing. The release list does not certify that history.
The v3.20.0 release lists memoless ERC20 handler, refund-simulation and inbound-observation changes.
historical · supported · THORNode v3.20.0
Observed 2026-10-03; claim reviewed 2026-11-08; review due 2026-12-08.
THORNode v3.20.0 Release Notes (GitLab)Support is for the listed release work only. Release creation, proposed upgrade date, implementation and successful current execution are separate facts.
Present memoless availability requires a fresh, source-qualified operational assessment.
current-only · needs-live-evidence · Current provider result must be obtained separately
Observed 2026-11-08; claim reviewed 2026-11-08; review due 2026-12-08.
Liquify THORNode Mimir endpointSupersedes for this question: memoless-august-cycle
Supersedes using the August claim to answer a present-tense question; it does not erase the historical record. The 8 November 2026 readback returned HALTMEMOLESS=1, MEMOLESSTXNCOST=2000000 and MEMOLESSTXNCOSTSLOPEBPS=10000; no successful memoless route is asserted.
Research
Dated analysis and roadmap context. Treat these as period framing until current protocol, route, or recovery sources agree.
2025-04-24 · Messari · Drexel Bakker
THORChain Q1 2025 Brief
Quarterly analysis covering affiliate volume, TVL, RUNE price performance, swap activity, and THORFi liabilities.
retrieval details
2025-07-09 · Nine Realms · Nine Realms
THORChain Q2 2025 Ecosystem Report & Q3 Roadmap
Ecosystem report with Q3 roadmap priorities and development updates.
retrieval details
2024-10-07 · Nine Realms · Nine Realms
THORChain Q3 2024 Ecosystem Report
Quarterly ecosystem report covering protocol performance, development milestones, and community initiatives.