New Discord Announcement from THORChain Devs #🚨thornode-mainnet # THORNODE ❗ MAINNET ❗ BASE daemon — v1.1.1 (fork) **NETWORK:** MAINNET **TYPE:** Non-coordinated **URGENCY:** ASAP base-daemon is updated to **v1.1.1**. If you self-host a BASE daemon, pull node-launcher and redeploy: ``` make pull make install ``` Base hardforked at L2 block **47806543** (~16:00 UTC today). Daemons not on v1.1.1 stall at that block and stop observing/signing BASE — update now to cross the fork. (Base release: github.com/base/node/releases/tag/v1.1.1) @everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## DISABLE BIFROST KEYVERIFY **NETWORK:** MAINNET **TYPE:** Non-coordinated **URGENCY:** ASAP ECDSA migration is complete — bifrost keyverify is no longer needed, and leaving it on only makes nodes periodically drop availability (~every 10 min) and risk extra slashing. Node-launcher now disables it by default; please pull the latest and redeploy to pick it up (restarts bifrost): ``` make pull make install ``` Restart-required, local-only — it does NOT halt signing/observing or affect keyverify elsewhere. (To keep keyverify on, set `BIFROST_SIGNER_KEYVERIFY_DISABLED: "false"`.) @everyone

✅ Heads up! Trading is resumed on the AVAX, BASE, BCH, BSC, BTC, DOGE, ETH, GAIA, LTC, SOL, TRON, XRP chains!

New Discord Announcement from THORChain Devs #🚨thornode-mainnet # THORNODE ❗ MAINNET ❗ MIMIR VOTE — UN-HALT SECURED + ENABLE TRADE ASSETS **NETWORK:** MAINNET **TYPE:** Coordinated (operational mimir vote) **URGENCY:** ASAP Recovery step — re-opening secured-asset and trade-asset trading. ``` make mimir ``` key: `HALTSECUREDGLOBAL` value: `0` key: `TRADEACCOUNTSENABLED` value: `1` Both are operational mimirs — ~3 active-node votes each (vote the same value; land them together, votes purge on churn). @everyone

ATTENTION NODE OPERATORS Check your SOL daemon

discord.com

New Discord Announcement from THORChain Devs #🚨thornode-mainnet # THORNODE ❗ MAINNET ❗ SUCESSFUL CHURN - NEED 1 MORE VOTE — HALT CHURNING We're at 2 of 3 operational votes to halt churning for the migration — need one more node to vote: > This is to avoid any clashing while we migrate and test the new TSS changes that have been made ``` make mimir ``` key `HALTCHURNING` value `1` @everyone

NODES Before voting, please refer to the conversation in dev discord. Further votes may not be necessary as we have already reached enough and would make it harder to reverse course if necessary

discord.com

Hey guys! We only need 45 more followers on Facebook and we can live stream there. Would you, the reader, take a second to follow the Facebook account? ♥️🙏

www.facebook.com

3.19.1 ! Attention all Nodes! Instructions given! LFG 🚀🚀🚀

discord.com

🚨Node Operators🚨 Please follow step 5 instructions:

discord.com

GM! We need 10 more votes for step 3, lets get it done Chads! 🔥🚀 Nodes, please vote :) BPs please ping your Node :D

rune.tools

UPGRADE IS GREENLIT Node Operators, please upgrade asap Bond Providers, please notify your Node Operators to upgrade. Lets get our girl back ♥️

discord.com

ATTENTION NODE OPERATORS 3.19.0 Upgrade Update is Live 🚨 # Mainnet 3.19.0 Upgrade: Changelog:

gitlab.com

Block: 26518000 Date: <t:1780968360:F> (June 9, 2026 01:26 UTC) -

runescan.io

Note: Block time is an estimate and may fluctuate. URGENCY: 3 days > Please note that this release is a private image containing a security patch. Any nodes that wish to review the patch can relay an age public key and one of the devs or THORSec will reply with an encrypted patch and instructions to verify the reproducible build hash. Release 3.19.0 ships our TSS patches which will be disclosed once we proceed through the chain recovery as well as the store migration that will conciliate the economical fallout of the hack for which you can see the details in

adr28.thorchain.org

This version also includes a new method to handle compromised vaults through the operational mimir CompromisedVault-<pubkey> which avoids scheduling, signing and overall transaction processing — while still observing the actual transactions — for the vault specified in the mimir pubkey. The full network recovery plan is as follows: 1. Vote to approve release 3.19.0. 2. Upgrade the network on Monday. 3. Enable the CompromisedVault-thorpub1addwnpepqvpnhwzqkd2zqkxsj272faf4ezsngwh773wjdfkus8m4f860u3g5ka22v28 mimir to quarantine the compromised vault. 4. Validate the ADR-028 store migration (Maya team). 5. Verify the integrity of every node's keyshares via the new temporary keyverify protocol (Maya team). 6. Unhalt signing. 7. Initiate the churn. 8. Wait for churn to finish 9. Unhalt Secured and Trade assets 10. Unhalt LP actions 11. Unhalt trading Please approve via make upgrade-vote: Select: mainnet Enter THORNode name: <thornode namespace> Enter THORNode upgrade proposal name: 3.19.0 Select THORNode upgrade proposal vote: yes

discord.com

New Discord Announcement from THORChain Devs #🚨thornode-mainnet THORNODE ❗️MAINNET❗️UPDATE 3.18.2

gitlab.com

NETWORK: MAINNET TYPE: Non-coordianted URGENCY: ASAP This is a Bifrost-only patch containing a fix to repair dead unhealthy-scanner solvency guard and adding per-chain floor block height for bifrost scanner + remove dead block-status ledger. ``` make update ``` @everyone

True, sorry for the delay. Yes, the network is getting close to pushing 3.19.0. It is on stagenet being tested furiously. The devs are attacking it head on. We just want to make sure everything checks out because a lot of math is involved (especially with accounting. Shout out to Hans for helping out with that!) If all goes well, 3.19.0 could be pushed very soon. Within days.

New Discord Announcement from THORChain Devs #🚨thornode-mainnet THORNODE ❗️MAINNET❗️ BAN NODE NETWORK: MAINNET TYPE: Coordinated URGENCY: ASAP Vote to ban this node (⅔ supermajority required — 63 of 93 active nodes): ``` make pull make ban # at the prompt enter: thor16ucjv3v695mq283me7esh0wdhajjalengcn84q # the script will confirm: # address : thor16ucjv...cn84q # ip : 64.95.10.143 # slash : 195222 # operator : thor16ucjv...cn84q (self-bonded) # confirm y → broadcast ``` @everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## THORNODE ❗️MAINNET❗️ HALT SECURED + TRADE ASSETS NETWORK: MAINNET TYPE: Coordinated (3 votes only) URGENCY: ASAP Close the secured asset and trade asset surfaces while the tss-lib patch lands. Complements the existing *HALTTRADING* / *HALTSIGNING* / *STOPSOLVENCYCHECK* halts already in effect. Operational mimirs — only 3 votes needed each to set. Note: HALTSECUREDGLOBAL is currently unset; TRADEACCOUNTSENABLED is currently 1 (flip to 0 to halt). ``` MIMIR_KEY=HALTSECUREDGLOBAL MIMIR_VALUE=1 make mimir MIMIR_KEY=TRADEACCOUNTSENABLED MIMIR_VALUE=0 make mimir ``` @everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet THORNODE ❗️MAINNET❗️UPDATE 3.18.1

gitlab.com

NETWORK: MAINNET TYPE: Non-coordianted URGENCY: ASAP This is a Bifrost-only patch containing a fix to ensure bifrost-internal signing flows honour the HALTSIGNING / HaltSigning switches. ``` make scale-up -> bifrost make pull make install ``` @everyone

THORChain just got hit with an insolvency due to a 0-day exploit. The hole is around 10 million dollars. Many believe we should not be burning any capital right now and we should be applying max effort to our new POL add mechanism to reclaim our pool depth. What do you think?

New Discord Announcement from THORChain Devs #🚨thornode-mainnet Hello Thorchads! We ask all active validators to please scale down their bifrost pods, **from now until 3.18.1 patch is live**. We request this in an abundance of caution while vulnerabilities are identified and patched. ``` make pull make scale-down # choose bifrost ``` > If you have trouble scaling down your bifrost pod, please reach out to devs via make relay or on discord. Thank you for your cooperation! @everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet Hello THORChads, The developers and thorsec teams have been hard at work throughout the weekend continuing the investigation to fully understand the events that took place, while also planning the road to recovery. I wanted to provide an update to keep the community informed as we move forward. It is important to note that the investigation is still ongoing, and details may change in the coming days as we continue to gather information and adjust plans accordingly. At this time, the team has a strong understanding of what occurred and how the attack was executed, though we are not yet in a position to publicly discuss the technical details. What we can say is that the attack vector does not appear to be related to any currently known GG20 exploits, and at this stage we are still assessing whether other GG20 implementations could also be at risk. The team will continue investigating this possibility and will coordinate with other affected teams as appropriate. We would also like to thank the many cryptographers and security researchers who assisted throughout this process, including members of the team that originally developed GG20. The team currently expects to release version 3.18.1 tomorrow for node operators to adopt. We ask that all node operators upgrade to this release as soon as possible. There is also an open question regarding the best approach for handling the lost funds within the network. This will need to be discussed and ultimately decided by the community through governance. To facilitate this discussion, I have created the channel <#1505953830796263424> . Before the network can return to a fully healthy state, we will need broad consensus on this ADR, after which the selected approach will be implemented as part of the 3.19 release. THORChads are encouraged to share well-structured and thoughtful proposals for the community to support or challenge. In the coming days, we will organize a vote highlighting the most widely supported approaches for node operators to actively vote on. Regarding the future direction of the cryptographic systems used to secure the vaults, that discussion is still ongoing and requires additional research before any long-term decisions are made. For the immediate future, the team is currently leaning toward remaining on GG20 in order to restore network health and stability as quickly and safely as possible. Longer-term discussions around the future of THORChain’s cryptographic security model will continue once the network has stabilized. As always, I am proud of how both the team and the community have handled this situation. We will get everything running again as soon as we can, but we are not going to rush the process. THORChain has a strong roadmap ahead, and I am excited for us to return our focus to continuing to push the envelope of what this project can achieve. Onwards to Valhalla

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## 🔓 v3.18.0 Source Disclosure

gitlab.com

The two security patches that shipped in the v3.18.0 private image are now public. **Disclosure tag**: `v3.18.0-disclosed` → commit `af46db22bd` **Diff vs public release**:

gitlab.com

**Deployed image digest**: `sha256:6ed0c6c5d87dbdd0fe1e51b69050fa68cac20ef67803c757efcfcbb6fe133f5f` Operators who want to verify the running binary against the disclosed source: ``` git fetch git checkout v3.18.0-disclosed BRANCH=mainnet BUILDTAG=mainnet make docker-gitlab-build docker inspect --format '' registry.gitlab.com/thorchain/thornode:mainnet ``` Anyone who previously requested the encrypted patch via age can now disregard — the same source is publicly available at the tag above. @everyone

Node Operators and BPs, ADR 26 is officially for vote. Please deliberate and vote

discordapp.com

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## THORNODE ❗️ MAINNET ❗️ UPDATE 3.18.0

gitlab.com

NETWORK: MAINNET TYPE: Coordinated URGENCY: 48h The upgrade proposal has passed. Please install to schedule the upgrade at the proposed height. Nodes will automatically update to the new image at the scheduled height, and the node version for active validators will be automatically set at that time. All non-active validators must run `make set-version` after the upgrade height to be eligible for the subsequent churn. > Remember this upgrade includes a private docker image that includes security fixes which active nodes can request a patch by `make relay` an [age](https://github.com/filosottile/age) public key ``` make pull make install ``` @everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet THORNODE ❗️MAINNET❗️UPDATE 3.17.0

gitlab.com

NETWORK: MAINNET TYPE: Non-coordinated URGENCY: 20h The upgrade proposal has passed. Please install to schedule the upgrade at the proposed height. Nodes will automatically update to the new image at the scheduled height, and the node version for active validators will be automatically set at that time. All non-active validators must run make set-version after the upgrade height to be eligible for the subsequent churn. ```make pull make install``` @everyone

Weekly update:

x.com

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ### Stuck Churn There is stuck Solana outbound that was successfully broadcast, but later dropped from mempool and now blocking churn completion. There will be a patch in a future version to handle this circumstance. Nodes in the culprit vault `thorpub1addwnpepqdrf73rpn0ew26ds2v544dtdg782m3a0uvhaxdaxzdjd7k2ylt932n3pqvu` are requested to clear their Solana signer cache to allow the outbound to be re-attempted. ``` thor1yak0z56elhcfqw7xn7wjmp43ndnnxgfcmwkwex thor1vvmt4q6h7w4gckcjh22z6ltjcppjz3laydnfzq thor1ug5gy49ges0umfna70gpccj3rae4n0px2qmv82 thor100m5hh9qayap0edmvl9h8er4z6uesnfazjmefg thor1krwlgcs3q7duapyxwxzpra5779fgh5gzh6gfaq thor1agftrgu74z84hef6dt6ykhe7cmjf3f8dcpkfun thor1kj56aupxnkhhy0rpdcp2gjncm4y78nnhjv496v thor1h4kjq4xrxsm7ajpkstqgp9jcwxlc8khyfpwkfr thor18h4xkczkd7g765n647t8clzp58cqet44n9s69g thor1raynyffujzs7wqujwtnyp9ryludjvpe0s9tacs thor1hjpct8pd9d48vyqltaqunltwx9twm57l3qmaya thor19uyg2vvsja9cfpejdj0c6pm7exfk87envj5s5h thor15qcqwmwu002gfu4ynwee5nhqy62j268e3dmw0q thor1va3av7xeq57jyy5jr3wumw3ezg6vs6ldy9geqf thor12espg8k5fxqmclx9vyte7cducmmvrtxll40q7z thor1d7rerzkzus2t6v2yv9wuw9xg8a8aqse8p6nvm8 thor1sh72x9rac8ahkya76zljql3mw7t96ywsjlzw0n thor15x0q6r84n2ac38gdlrct5ncchj5d4cr76jfaaf thor1fuw5nemuww2gclznelfrdzpj6eml0fnmhgphew ``` If you are a node in the set above, please perform the following: ``` make debug # select cosmosfullnode # select thornode # select bifrost rm -rf /var/data/bifrost/observer/SOL/ # exit shell and ensure bifrost starts back up ``` Once a quorum of the vault have cleared their signer cache and the outbound can be sent and churn can complete. @here

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## GAIA 27.2.0❗️VALIDATORS ONLY NETWORK: MAINNET TYPE: Non-coordianted URGENCY: 24h This install includes a required upgrade for Gaia `27.2.0` scheduled tomorrow at

www.mintscan.io

``` make pull make install ``` @everyone

Excerpt: Chads' enthusiastic exchange - XMR (and TAO) coming to a DEX near you - and what it took to get there...

New Discord Announcement from THORChain Devs #🚨thornode-mainnet **Nine Realms Transition Announcement** After several years contributing to THORChain's development and operations, over the next six weeks, Nine Realms will be gradually stepping back from our active roles in the ecosystem. There is a thread on this topic, please follow here for more info/discussion.

discord.com

Are you going to Bitcoin Las Vegas in April? Come to the THORChain meetup/side event! RSVP here:

invite.social

Weekly Recap is up!

x.com

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## THORNODE ❗️MAINNET❗️UPDATE 3.16.1❗️VALIDATORS ONLY

gitlab.com

NETWORK: MAINNET TYPE: Non-coordinated URGENCY: ASAP This is a Bifrost patch release containing a fix for EVM chain scanners preventing aggregator swap-ins. ``` make update ``` Then verify your node version is properly set to `3.16.1` and `make set-version` if the automatic version set did not apply. Once a quorum of the network has updated it is safe to resume EVM chain trading. @everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## THORNODE ❗️MAINNET❗️UPDATE 3.15.3 (Bifrost Only)❗️ENABLE SOLANA

gitlab.com

NETWORK: MAINNET TYPE: Non-coordianted URGENCY: 24h This is a Bifrost-only patch release containing a final Solana fix and enabling the scanner by default. Please `make pull`, set the Bifrost environment variable `BIFROST_CHAINS_SOL_RPC_HOST` to your RPC provider, then `make install` to apply. We will wait 24 hours from the time of this message. Then once a quorum of all vaults are scanning Solana at tip, we will unhalt churning and proceed to keygen Solana vaults. @everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## XRP Config There is an update required to the XRP config to continue syncing blocks. If you have not already done so, please `make pull` and `make install` to apply. Once the XRP daemon is in ready state, it is likely you will need to force the scanner height forward past the pruned heights by setting `BIFROST_CHAINS_XRP_BLOCK_SCANNER_START_BLOCK_HEIGHT=101672000` (or a later block depending on when you apply) in your Bifrost environment. Once 80% of the network is back to tip it should be safe to resume XRP. @everyone

⚡️ LIVE NOW ON X WITH THORWallet Join in for an everthing conversation with the THORWallet team, where we'll be diving into everything we can expect from them this year, and beyond. Click here to jump into our Saturday vibes 👇

x.com

Recording of the space THORSday - Largest DeFi Swap In History - Huggin AI - Updates & Alpha. (converted to mono, some longer pauses shortened, compressed to reduce differences in volume of different speakers, missing Yee-haw added)

LP & Churn Paused Devs have received a responsible disclosure as part of the ongoing bug bounty program. While this potential issue is verified and reproduced, nodes have proactively paused: - Limit Orders - LP Actions (Add / Withdraw) - Churn 3.15 will be released to mainnet next week (21 Jan 2026). If a patch is necessary, the above will remain paused and a fix will be included in the 3.15 release. @everyone

Kenton Ralph Toews - Introduction to Thorchain (excerpt from the space)

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## Daemon Updates There are upcoming forks for Gaia (next Monday) and BSC (next Wednesday). Please `make pull` and `make install` to prepare for these upgrades. Note that there may be a couple hours of slight degradation on BSC performance due to reindexing when this upgrade is applied - it did not cause issues for 9R when we applied to our instances. @everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## XRP 3.0.0 The XRP `3.0.0` update was not marked required in their release notes, but we have observed nodes running `2.6.2` being stuck in an unready state. If you are not on the latest please `make pull` and `make install` to update. @everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## Stuck BTC Outbounds There are 2 BTC outbounds currently stuck due to a race fixed by

gitlab.com

There will likely be a Bifrost patch release later this week to prevent this moving forward, but rectifying the current stuck outbounds (and unblocking the next churn) will require a quorum of nodes in the culprit vault to clear their signer cache and allow the outbounds to be re-attempted. ``` node_address vault status operator kryt Active 3dyy thor10ezxhe7elledmsm823pg3ynn28k6azudc429kf 5jlv thor1m99a3vr6ckafl3wm842zx4k7nq5cempxnx44p8 5n2m thor1fkmdrdtyxcfteewwsuqagekq46ag5s0vulq7qk 9ax9 thor1wed8wsu98kvphxx39hgjnqtzw0s69u85ckuh40 9zfl thor1s6xz88ell5c6erd7hspfjw8syce89mgn32z6gr c4er thor1dqlmsm67h363nuxpd68esg54kt2t7xw2xewqml j7dg thor1mhfws050cefng955ejqugajvxn9z67840tkh6y k6jt thor10czf2s89h79fsjmqqck85cdqeq536hw5ngz4lt m54s thor12jrhy6mqxtff6utq4kkavtvmqz4qxtztxxnk4j m62d thor1raynyffujzs7wqujwtnyp9ryludjvpe0s9tacs pgtt thor1sn88hq7n85a5ju4x9pjghzgqu070h2epnyj53w s7en thor10ma7lf07ld98wcm3nvt7uptase4mhrt82rkvg4 tf9u thor15q5tacqnysa76jc8cr4h5g42rmlupt2lf4z5cj yqu0 thor16cm2usv42a9da3hd76glwxq8fdc9tkj8wa0653 zarc thor1a7vpyxt4wkyl9fdd7mumnt8s6v4akq8ucx450x zarc thor1l4djft73rqrg7xtmmhdnqf0adejl2dp3rpe624 Standby yv6p thor1vp29289yyvfar0ektscjk08r0tufvl24tn6xf9 ``` If you are a node in the set above, please perform the following: ``` make debug # select cosmosfullnode # select thornode # select bifrost rm -rf /var/data/bifrost/observer/BTC/ # exit shell and ensure bifrost starts back up ``` @everyone

🔥 Chad's Hangout w/ Chad Barraford Live Now Join in for all the latest updates and alpha on THORChain

x.com

⚡️ Weekly Ecsystem Recap For everythibng cookibg in the eco that you ight have missed but shouldn't have, here's the TLDR

x.com

Recording of the space THORChain Community Lounge with THORWallet. (converted to mono, longer pauses shortened, compressed to reduce differences in volume of different speakers)

🚨 X Space is live but NOT ON THR MAIN ACCOUNT Click here to join Kenton’s Soace with THORWallet 👇

x.com

V3.14.0 is tight, technical, and powerful. Seven PRs that cut delays, clean vaults, fix the quirks, and make THORChain smoother than ever. Here's everything you need to know👇

x.com

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ## Base 0.14.2 All nodes that have not installed from latest `node-launcher` since last week including the latest Base update please do so as soon as possible - the update is required to continue sync. @everyone

Recording of the space Community Lounge with Vultisig. (converted to mono, longer pauses shortened, compressed to reduce differences in volume between different speakers)

New Discord Announcement from THORChain Devs #🚨thornode-mainnet ### Mainnet 3.14.0 Upgrade Proposal - Validators Only **Changelog**:

gitlab.com

**Block**: `23969500` **Date**: 05-Dec-2025 @ ~1:00pm EST -

runescan.io

**Note**: Block time is presently fluctuating - this time is an estimate, but may fluctuate by hours. This release delivers safety and reliability improvements by retiring outdated vault-recovery logic, adding deterministic quote queries, and enabling automatic retries for retired-vault refunds. It also fixes several streaming-swap calculation issues and ensures all built outbounds are consistently checkpointed. Please approve via `make upgrade-vote`: Select: `mainnet` Enter THORNode name: <thornode namespace> Enter THORNode upgrade proposal name: `3.14.0` Select THORNode upgrade proposal vote: `yes` @everyone