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

🚨 X Space is live but NOT ON THR MAIN ACCOUNT

Click here to join Kenton’s Soace with THORWallet 👇

https://x.com/kentonc137/status/1997316862598693249?s=46

⚡️ Weekly Ecosystem Recap

For everything cooking in the eco that you might have missed but shouldn't have: here's the TL;DR

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

🔥 Chad's Hangout w/ Chad Barraford Live Now

Join in for all the latest updates and alpha on THORChain

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

⚡️Your Weekly THORChain Ecosystem Recap

The Intern's keeping you fully informed and updated, rapid-style👇

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

New Discord Announcement from THORChain Devs #🚨thornode-mainnet

## Stuck BTC Outbounds

There are 2 BTC outbounds currently stuck due to a race fixed by https://gitlab.com/thorchain/thornode/-/merge_requests/4392. 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

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

🚨 X Space w/ RUJIRA Live Now

Finishing off 2025 with a banger, we're histing our final X Space and it's a special one for both THORChain and RUJIRA communities

Click here to join right now👇

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

🔥 WEEKLY ECO RECAP

There's no time to rest for those who want to end 2025 crushing it.

ICYMI here's the TLDR of the latest updates in the THORChain eco 👇

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