THORChain Weekly Dev Update for Week 71, 24–30Nov; Multiple outbounds, Finalisation Parameter, Node Improvements, Gauntlet Report, Community Tool Improvements.
Summary
The team worked on multi-chain improvements. Chaosnet is stable, so all the changes are destined to the next net, but some changes may be cherry-picked into Chaosnet to improvement and validate assumptions. Gauntlet released the CLP report which was favourable to THORChain’s model and community developers continue to ship updates.
THORNode
Multiple Outbounds
A notable change to one aspect of THORNode this week is now the ability for the state machine to delegate one or more vaults to fulfil a member’s withdrawal. This is because funds can be scattered across multiple vaults and a single transaction cannot service the full amount (such as a large LP in a small pool doing a large withdrawal). The state machine will try to minimise the outbounds, but now there can be multiple. To date, there have been several LPs in some of the smaller pools who have not been able to withdraw (they would get error message “You cannot withdraw more than 10% of the pool”) — this should fix this.
Finalisation Parameter to Observations
For probabilistically final blockchains such as Bitcoin and Ethereum1.x, large transactions are not economically final until the chain has produced enough income to make it unfeasible to be re-orged. THORChain does not do “6 confs” (arbitrary threshold on whether or not a transaction is final, as opposed to economically final), instead it counts confirmations — (any Bitcoin transaction is safe to spend 1-conf as long as less than ~6.25 is received by THORChain in a block). To do this it measures the coinbase reward (subsidy + fees) and counts the total received block value against this. To date the logic has been in the Bifrost, so THORChain is never aware of large transactions. This change now adds a finalisation=uint so that the state machine (and thus Midgard) is immediately aware of an inbound transaction, AND it is told of how many confs are to be waited, like finalisation=3. Now clients can inform the user of the ETA of a swap. The Bifröst will then follow up 3 confs later and tell the state machine it is safe to process the transactions.
Note: Even if a user performed a small swap, like 0.1 BTC, but did it unknowingly in the same block as a user doing a large swap, like 20 BTC, both users will have to wait 4 confs, but this is still better than making all users wait 6 confs. 6 confs is not a magic limit that makes transactions safe — a 1000 BTC transaction is categorically unsafe at 6 confs, there can still be an actor with the financial resources to pull off a re-org at that level. Indeed, Binance considered a 100-block re-org of the Bitcoin chain to reverse a 7000 Bitcoin theft, but abandoned that when they realised they would enter a fee-race with the attacker. THORChain has no ability to stop or censor transactions and is completely permissionless, thus it must function purely on economic terms, and not rely on any altruism or social contracts.
Node Improvements
Two other notable improvements to THORNodes involve now (after much community discussion on possible chain bloat) emitting slash events to help THORNodes understand why they are getting slashed:
Missing an observation, 2 points, (is the chain-daemon running?)
Missing a key-sign, 2 points, (is Bifröst running?)
Missing a key-gen, 720 points, (is Bifröst running?)
As well as a better grace period to new nodes to stop them being churned out as soon as they enter. They now get a full churn cycle grace period, as well as a 100 slash point minimum, before being considered bad. New nodes are more likely to get churned out, because the “bad” metric is the inverse of blocksActive/slashPoints.
- Resolve “[FIX] migration bug and TSS metrics bug”
- get the total tx value and subsidy from coinbase
- remove TotalReserve from Network type
- [feature] allow breaking up a single outbound transaction into multiple parts
- Resolve “ADD: Finalisation parameter to Observations”
- add slash point events
- Node Bad Behaviour Tweaks
- Resolve “[FIX] Tx that doesn’t trigger outbound has not been marked as done when it get processed”
- Resolve “[FIX] Fix a BTC gas issue cause insolvency”
Midgard
Fixes and improvements to the /stats and /tx endpoints. Also a historical endpoint for stats to show growth of the network over time.
- Update coins index
- Resolve “Wrong block time inserted to database when syncing in batch mode”
- Update master to v0.7.1
- Merge branch ‘301-wrong-block-time-inserted-to-database-when-syncing-in-batch-mode’ into ‘develop’
- Resolve “ADD: cache to /v1/stats”
- Resolve “Optimize sql query behind /v1/txs”
- Resolve “Implement historical endpoint for stats”
- Resolve “Optimize processEvents in /v1/txs”
Devops
Continual improvements.
Clients
BEPSwap Client
Numerous UI/UX tweaks based on community feedback
ASGARDEX Client
Work continues to prepare the client for Multichain Chaosnet.
Community Work
The following tools receive regular updates:
Telegram Bot
Twitter Bot
Delphi Defi Dashboard
https://defi.delphidigital.io/thorchain/chaosnet/network
THORChain Network Explorer
Continual Improvements
THORChain Official Block Explorer
https://viewblock.io/thorchain
RUNEData
Completely re-written, the new tool should be bookmarked:
RUNEBalance
View current arbitrage opportunities in the pools
https://www.runebalance.com/#/pools
RUNEStake
Always receiving improvements, this week a new landing page:
Trading Leaderboard
View the current leaderboard for traders on THORChain
https://leaderboard.thornode.org/
Audits
The gauntlet report on the CLP mechanism was released:
The key takeaways validate THORChain’s position on the CLP method:
Next Milestones
Multi-chain Testnet 2 (with Native Rune) is expected sometime within the week.
Community
To keep up to date, please monitor community channels, particularly Telegram and Twitter:
- Twitter: https://twitter.com/thorchain_org
- Telegram Community: https://t.me/thorchain_org
- Telegram Announcements: https://t.me/thorchain
- Reddit: https://reddit.com/r/thorchain
- Github: https://github.com/thorchain
- Medium: https://medium.com/thorchain
Related articles
![]()
May. 14, 2026
Explanation of the 6 Preset Strategies to Help Create Your CCL Strategy
![]()
May. 13, 2026
The Casino Problem: When Crypto Forgets What It Was Built For
![]()
May. 12, 2026
THORChain Protocol Upgrade v3.18
![]()
May. 11, 2026
Dash is coming to THORChain
![]()
May. 8, 2026
Monero Merged, Reserve Burn, Marketing Update | Podcast #196
![]()
May. 7, 2026
Marketing Update: Feb - March 2026
![]()
May. 5, 2026
RUJI Staking Rewards Are Live, Earn Real Protocol Revenue on Rujira
![]()
May. 4, 2026
Bior Labs Cards Are Imminent: Bill Pay, $10K Virtual Cards and a Stablecoin Alpha
![]()
May. 2, 2026
Live from Bitcoin Vegas: 2 bps Stable Swaps, v3.18 Next Week and the Affiliate Revshare Plan
![]()
Apr. 30, 2026
THORChain Quarterly report - Q1 2026
![]()
Apr. 29, 2026
bRUNE Staking Cap Increased to 2 Million, How to Stake, and Earn THORChain Yield
![]()
Apr. 28, 2026
Protocol Upgrade - v3.17.0
![]()
Apr. 27, 2026
Unstoppable: The Best Privacy Wallet – THORChain Mobile Interface
![]()
Apr. 24, 2026
THORChain Stands for a Permissionless and Decentralized Ethos
![]()
Apr. 23, 2026
Custom Concentrated Liquidity: Where Liquidity Becomes Strategy
