New Discord Announcement from THORChain Devs #🚨thornode-mainnet

**Mimir Change for Advanced Swap Queue Bug Fix**

There is a bug in the advanced swap queue calculating the maximum quantity where we're applying the derived asset depths, rather than the native asset depths. This effectively makes trades slower & calculate the optimal number of sub-swaps incorrectly. Derived depths are unused, so this mimir change is safe. The devs will issue a patch in a future version, but this mimir will effectively fix the problem in the meantime. @everyone

`make mimir DERIVEDDEPTHBASISPTS => 10000`
`make mimir DERIVEDMINDEPTH => 10000`

🚨 Live on X Right Now

Today we're joined for an all privacy, self-custody and integrations discussion with BiorLabs

Click here to join in 👇
https://x.com/THORChain/status/1989363113561362883?s=20

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

<a:orange_alert:857289677010370580> UTXO Trading and Signing Paused <a:orange_alert:857289677010370580>

A community member has responsibly disclosed a potential exploit in the way bifrost signs UTXO chains. These chains have been temporarily paused out of an abundance of caution until devs can evaluate the issue, make a patch, and release it for network adoption.

We ask all node operators to stay tuned if a patch is released for a quick adoption.

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

THORNODE ❗️MAINNET❗️UPDATE 3.12.2

https://gitlab.com/thorchain/thornode/-/releases/3.12.2

NETWORK: MAINNET
TYPE: Non-coordianted
URGENCY: ASAP

This is a non-consensus breaking release fix TSS signature pairing vulnerability to prevent double-spend attacks.

make update


Then verify your node version is properly set to 3.12.2 and make set-version if the automatic version set did not apply.

@everyone

WEEKLY ECOSYSTEM RECAP ⚡️

Builders keep shipping, protocols are evolving, Memeloss transactions gain traction, and automation on the App Layer looks sweet for users.

Spotlighting:
- Maya Protocol
- LeoDEX
- Vultisig
- AutoRujira
- RUNEBondApp

Click here for the rapid insights 👇

https://x.com/THORChain/status/1990558826697834906?s=20

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## THORNODE ❗️MAINNET❗️UPDATE 3.13.0
https://gitlab.com/thorchain/thornode/-/releases/v3.13.0

NETWORK: MAINNET
TYPE: Non-coordianted
URGENCY: 24h

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
```

Please note that this release is a private image including a medium severity security patch. Any nodes that wish to review the patch can `make 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.

@everyone

🚨 THORChain v3.13.0 IS Going Live🚨

One of the biggest stability power-ups in months just dropped. Over 20+ upgrades making swaps faster, quotes sharper, migrations safer, and outbounds basically unkillable.

This release is straight-up protocol hardening. If you use THORChain, build on it, or run a node, you need to understand what changed.

Top Highlights:
🔥 82× faster Quote API – quotes back to instant speed
🔥 Scheduled Migrations – safer upgrades, zero chaos
🔥 Intelligent Outbound Recovery – funds can’t get stuck anymore
🔥 Limit Order Quotes – infra upgrade for UIs & app-layer devs

Check out the full breakdown 👇

https://x.com/THORChain/status/1991225698099302582?s=20

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

There was an issue with the upgrade, devs are investigating.

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

Devs believe we have a fix for this issue and will be releasing it ASAP. Special thanks to @Andrew and @jacobgadikian for assisting on this issue.

@here any node operators should be online/available to push the release once its available

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## THORNODE ❗️MAINNET❗️UPDATE 3.13.0 (fix)

NETWORK: MAINNET
TYPE: Non-coordianted
URGENCY: ASAP

There was a Cosmos store upgrade added to `3.12` for the `x/scheduler` module to be used by app layer, which did not get removed in the `3.13` release and caused panic at the upgrade height. This replaces the `3.13.0` image with one that devs believe should resolve the issue and allow block production to continue.

```
make pull
make install
```

All non-active validators must run make set-version after the upgrade height to be eligible for the subsequent churn.

@everyone

🔥 Founder Spotlight - MOCA app

This week, it's Zey from Mexico, the founder of MOCA app and in this interview we dive into the real-world problems that inspired MOCA and show how the team is rebuilding the entire experience around human behavior, not just the chains.

Also, how THORChain’s native, trustless infrastructure is powering a future where crypto payments finally “just work” for everyone.

Let's learn more about the Foubder fo MOCA👇
https://x.com/THORChain/status/1991955570836885604?s=20

🚨 Live In 10 Mins

Join our weekly Community Lounge as we do the deep dive on LeoDEX

Listen in, join up on stage to ask your questions, or just stay for the good Saturday vibes👇

https://x.com/THORChain/status/1991974552570573291?s=20

⚡️ Weekll Eco Recap Rapid Fire

We love to celebrate our ecosystem integrations and how they're pushing forward to BUILD. SHIP. SCALE.

Here's the overview ICYMI 👇

https://x.com/THORChain/status/1993095419812102459?s=20

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

**Mimir Change Proposal: Improving Swap Queue Throughput**

I am proposing a community vote to update an older, rarely-touched mimir parameter: MinSwapsPerBlock. This setting—together with others—governs how many swaps are processed per block. It is important to outline the current behavior so all node operators understand the impact clearly.

**Background**

The protocol enforces a cap on the number of swaps executed per block to prevent malicious actors from flooding the system with an excessive volume of transactions. Without this cap, a spam campaign involving tens of thousands of swaps could significantly delay block production. Since genesis, this upper limit has been set to 100 swaps per block.

The system was originally designed to process roughly half of the swap queue each block, subject to a minimum threshold defined by `MinSwapsPerBlock`, which has remained at 10. In practice:
• If the queue holds 30 swaps, the system processes 15 (typically ordered from largest to smallest, though the algorithm includes additional nuances).
• If the queue holds 14 swaps, the system processes 10—the enforced minimum—rather than 7.

This design parallels Bitcoin’s fee-based prioritization model: higher-value transactions naturally move ahead of smaller ones. Likewise, THORChain’s architecture biases toward larger swaps (which produce more fees), thereby encouraging arbitrageurs to increase their trade sizes and accept tighter margins to outrun competitors).

**Why This Matters Now**

This mechanism was conceived before streaming swaps existed. Historically, swaps executed in a single block, but under the current model swaps often persist across many blocks (due to streaming). As a result, smaller swaps can experience substantial delays when the queue becomes congested.

**Proposed Adjustment**

Raising `MinSwapsPerBlock` from 10 → 50 should meaningfully accelerate how quickly the protocol clears the swap queue. This change increases per-block throughput and reduces the likelihood that small swaps remain stuck behind larger flows.

There is a possibility that block times may rise modestly, though the magnitude is uncertain and may be negligible.

**Request to Node Operators**

I am asking all node operators to review this proposal and vote accordingly:
`make mimir MinSwapsPerBlock => 50`

@everyone

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

### Mainnet 3.14.0 Upgrade Proposal - Validators Only

**Changelog**: https://gitlab.com/thorchain/thornode/-/releases/v3.14.0
**Block**: `23969500`
**Date**: 05-Dec-2025 @ ~1:00pm EST - https://runescan.io/block/23969500
**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

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## THORNODE ❗️MAINNET❗️UPDATE 3.14.0
https://gitlab.com/thorchain/thornode/-/releases/v3.14.0

NETWORK: MAINNET
TYPE: Non-coordianted
URGENCY: 72h

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

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

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## Base Sync Failures

There is an intermittent issue with Base getting stuck in an unrecoverable loop due to lack of blob data on the L1 beacon. This appears to have occurred on a majority of nodes following the Fusaka fork. If you are affected, please `make pull` and `make install` to add a flag to the Ethereum beacon, which should hopefully mitigate this moving forward, then reset your Base daemon.

We will keep Base paused until scanning has caught back up to tip.

@everyone

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👇

https://x.com/THORChain/status/1996222931467219270?s=20

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## Ethereum Restarts

There was a bug in the beacon following the Fusaka upgrade causing performance issues and lag, which resulted in frequent pod restarts. This is addressed by an additional flag as a hotfix. Please `make pull` and `make install` to apply the flag addition. We will unpause Ethereum once we see scanning stability.

@everyone

🚨 WE ARE LIVE ON X_SPACE w/ Chard Barraford

Click here to join for the latest updates and alpha on THORChain

https://x.com/THORChain/status/1996317136302620997?s=20