
$RUNE news
Every $RUNE story, instantly, with how the price moved after each one.
Top stories
- THORChain, which handled ~$1B of stolen Bybit funds in 2025 for $12M+ in fees, began moving the Binance loot despite FBI pleas, saying it can't stop transfers (Wall Street Journal) (Visit Techmeme dot com for the link and full context!) Techmeme
- BINANCE ATTACKER STOLE $6.28 BILLION ACROSS 8 BLOCKCHAINS IN COORDINATED EXPLOIT On-chain analysis shows the attacker spent a day preparing, tested EIP-7702 wallet delegation and deployed automated sweeping contracts before striking. Over $6 billion was drained in just 55 minutes, including 18,270 BTC. Roughly $2.8 billion has since been frozen, while $3.27 billion remains movable. Expert breakdown below. Bitcoin News
- On October 31, THORChain halted trading on several blockchains. An Ethereum block reorg caused THORChain to pay out 10 ETH that a vault never received. The automatic solvency checker caught the shortfall and halted ETH swaps. Within approximately two minutes, node operators halted ETH transaction signing, so no further ETH could leave the vaults. Node operators then halted all chains as a precaution so core developers could investigate. The 10 ETH has been returned by the user to make the vault solvent again. Breakdown of what happened and next steps: At 11:34 UTC Oct 31, Ethereum had a one-block reorg. A 10 ETH deposit to one of the vaults sat in the dropped block and never landed on the canonical chain. THORChain had already observed and credited that deposit. The swap missed its price limit and was refunded, so the vault paid out 10 ETH it never received. The sender's real deposit was refunded as well. Every node detected the reorg. But the re-check that should have removed the deposit could not get a clear answer in time, so it was finalized. The solvency checker halted ETH swapping automatically, then three node votes halted all ETH outbound payments. All chains were then halted by three node votes as a precaution. Now that this is public knowledge, every time there is a block re-org on an external chain, a malicious actor could perform a new transaction with the same nonce and would be paid funds by the THORChain vaults. Note: Three node votes can trigger emergency halts to protect network solvency. However, that action can be reversed by four counter node votes, then five node votes can reverse the reversal, and so on, maintaining a balance between decentralization and rapid emergency intervention. Halting a chain does not give those nodes control of the assets. Core developers have been working on the necessary fixes. Nodes will decide to re-enable chains as they are deemed safe. Trading blockchains: AVAX, BASE, RUNE, XRPL Halted blockchains: ATOM, BCH, BSC, BTC, DOGE, ETH, LTC, SOL, TRON, ZEC THORChain
- BREAKING: THORChain restarts most swaps after analyst said operators would expect North Korea to launder Unchained
- 🚨 Binance Hacked Funds Update The @binance Hot Wallet Exploiter has successfully used @THORChain to swap 1,690.45 $ETH (about $3.05 million) into $BTC (bc1qlerxe6pmlktf043wnagdjgf0ed0cdfhj5gjzch) since 4:12 am on Nov. 18 (HKT). It transferred the swapped $BTC to multiple addresses and then split the funds into small amounts and distributes them to hundreds of addresses. Beosin 🛡 Web3 Security & Compliance
- Relay's compliance and team are so bad that DPRK manage to bridged $38M (still bridging) in just 7 hours through the @RelayProtocol Bridge, and they couldn't stop it despite claiming to have an active KYT system. DPRK couldn't laundered that amount within such a short timeframe through THORChain, but Relay opened the door. so bad for you guys.... Address: TNhpfKq83wufEKGjBhQFnT7jnxYmyBzH6F Stay Relay. Specter
Latest
- THORNODE ❗ MAINNET ❗ MIMIR VOTE: ALLOWNOVAULT BTC/BCH/ZEC UNTIL 28,729,650 NETWORK: MAINNET TYPE: Coordinated (mimir vote) URGENCY: ASAP The churn migration is stuck on the 6 retiring vaults. Each vault's book is slightly above its on-chain BTC, BCH and ZEC balance (about $56 across 14 vault/chain pairs), so Bifrost refuses the migrates before TSS, and the reschedules keep the same sizing. We'll top up the gaps with NOOP:NOVAULT deposits, which only work while ALLOWNOVAULT-<CHAIN> is set. The value is a block height, so the gate closes on its own at 28,729,650 (approx. 20:40–20:50 UTC Wed). While it's open, a NOVAULT deposit can only debit the depositor's own coins, so no vault funds are at risk. for c in BTC BCH ZEC; do MIMIR_KEY=ALLOWNOVAULT-$c MIMIR_VALUE=28729650 make mimir; done key: ALLOWNOVAULT-BTC value: 28729650 key: ALLOWNOVAULT-BCH value: 28729650 key: ALLOWNOVAULT-ZEC value: 28729650 Operational mimir: takes effect with 3 matching node votes. THORChain
- The Binance hacker has moved another 78,415 $ETH ($142M) for laundering, continuing to swap the $ETH for $BTC via #THORChain. Lookonchain
- 📢 Reminder: GAIA v29.1.0 + BSC 1.8.2 ❗️VALIDATORS ONLY NETWORK: MAINNET TYPE: Non-coordinated URGENCY: hard deadline — GAIA upgrade height 33,935,300, ~Wed 2026-11-18 12:30–12:45 UTC (~3h) Reminder to update as gaia upgrades in 3h and unhealthy gaia scanners will block the churn migration. make pull make install 🔴 GAIA — v29.1.0 REQUIRED At height 33,935,300 the gaia daemon halts. A node without the new version stays stuck and your GAIA scanner stops. Image !1804 + Chart !1805 — gaia-daemon v29.0.1 → v29.1.0, digest-pinned sha256:e0f8d53f…c8f8b78e. Deploy BEFORE the upgrade height. The node switches images on its own when it halts. No resync, no config changes. 🟢 BSC — 1.7.8 → 1.8.2 Image !1792 + Chart !1793 — routine bump, digest-pinned sha256:39acb0a0…2ff5629b, no resync. Please check your scanner health after the update. THORChain
- What Is a Liquidity Pool? How Liquidity Pools Work in Crypto RUNE
- THORNODE ❗ MAINNET ❗ MIMIR VOTE: UNHALT CHURNING FOR ONE CHURN NETWORK: MAINNET TYPE: Coordinated (mimir vote) URGENCY: ASAP Churning is halted and the last churn was at block 28,203,871, well past the 43,200-block interval, so a churn starts as soon as this vote takes effect. We're unhalting for ONE churn on 3.21.5. Once that churn's migration completes, we'll post a vote to set HALTCHURNING back to 1 and keep churning halted through the 3.22.0 upgrade, because the 3.22.0 migration must run with no retiring vault at the upgrade height. make mimir key: HALTCHURNING value: 0 Operational mimir: takes effect with 3 matching node votes. THORChain
- THORNODE ❗ MAINNET ❗ MIMIR VOTE: MAXOUTBOUNDATTEMPTS BACK TO 0 NETWORK: MAINNET TYPE: Coordinated (mimir vote) URGENCY: Low The stuck XRP outbound (EE959E9A…3306) was retired through the treasury recovery path at block 28698880, so MAXOUTBOUNDATTEMPTS has done its job. Set it back to 0 (disabled, the default) so no other outbound gets retired automatically. If you voted 200, please vote 0. make mimir key: MAXOUTBOUNDATTEMPTS value: 0 Operational mimir: takes effect with 3 matching node votes. THORChain
- THORNODE ❗ MAINNET ❗ MIMIR VOTE — DISABLE TSS SIGNER FILTERING NETWORK: MAINNET TYPE: Coordinated (mimir vote) URGENCY: ASAP Outbounds are stalling on several vaults: jails shrink keysign parties to the bare minimum, so one slow member fails every round. Voting 1 makes keysign use the full vault membership (jailed nodes can be blamed again). Temporary until the bifrost fix ships; we'll post the vote back to 0 before churning resumes. Operational key: 32 nodes already vote 1 and none 0, so a fresh vote of 1 sets it. make mimir key: DISABLETSSSIGNERFILTERING value: 1 THORChain
- 📢 GAIA v29.1.0 + BSC 1.8.2 ❗️VALIDATORS ONLY NETWORK: MAINNET TYPE: Non-coordinated URGENCY: hard deadline — GAIA upgrade height 33,935,300, ~Wed 2026-11-18 12:45–13:00 UTC (~22h) make pull make install 🔴 GAIA — v29.1.0 REQUIRED At height 33,935,300 the gaia daemon halts. A node without the new version stays stuck and your GAIA scanner stops. Image !1804 + Chart !1805 — gaia-daemon v29.0.1 → v29.1.0, digest-pinned sha256:e0f8d53f…c8f8b78e. Deploy BEFORE the upgrade height. The node switches images on its own when it halts. No resync, no config changes. 🟢 BSC — 1.7.8 → 1.8.2 Image !1792 + Chart !1793 — routine bump, digest-pinned sha256:39acb0a0…2ff5629b, no resync. Please check your scanner health after the update. THORChain
- The Binance hacker has started laundering the 602,402 $ETH ($1.09B) he holds! Over the past 3 hours, he has transferred out 74,880 $ETH ($136.8M) and is now swapping it for $BTC via #THORChain. Lookonchain
- 📢 Stuck VVV refund: BASE vault members, please check your BASE RPC One of the last churn blockers is a stuck refund. The refund REFUND:AA2A1D0FBC48AE8D9B3B01FCCCCC9AECDC16492F9FAB9F7A13FE242873664E5F (321.06 VVV on BASE) has been failing keysign every ~900 blocks since 11-14. It alternates between two vaults, and most members never enter TSS for it, so it can't reach threshold (13/19). If your node is listed below, please point bifrost's BASE RPC temporarily at an archival node or Devels BASE RPC, then restart bifrost and verify that your BASE scanner keeps up. yaml thornode: bifrost: env: BIFROST_CHAINS_BASE_RPC_HOST: # or your own archive node Vault …p5l8msupg2wf8 (6/19 participating) 3cxw 68pn 9yap f2x9 fsex g8rf kwex m2p7 rsyj s65a skf6 t90c tacs Vault …pw7fajaan99h (3/19 participating) 07ns 0rde 280h 40qp 450x 6uuk dcr4 hyt3 j53w l3k7 mdmn nerd nfzq nk4j nvm8 nz4v zhk6 joined TSS after switching (02:08 UTC today), so it does make a difference. BASE Trading has been disabled to prevent further refund issues until a fix is deployed Your Bifrost logs this if impacted: 2026-11-17 12:41:02.951 {"level":"warn","service":"bifrost","module":"signer","error":"refund funding: BASE deposit AA2A1D0FBC48AE8D9B3B01FCCCCC9AECDC16492F9FAB9F7A13FE242873664E5F: funding receipt unavailable: not found; block receipts fallback: funding block 57492283 receipts: funding block receipts RPC is unavailable: not found","time":"2026-11-17T06:41:02Z","caller":"eQqo8Oig.go:1","message":"holding refund before signing"} Fixed BASE Refund The following refund has been processed successfully and vault members can switch back to their own/non-archive base RPC. Vault: ..dx7767 Refund: REFUND 7A9843DD…FAB6E4 (14.88 BASE.ETH) Members: 0k68 44p8 5u33 63d0 9tcy a8py ahem enp5 fzzy h5d6 hcs3 kvg4 ne9y nee4 rtpq uhvu ux5h z4lt THORChain
- Raynalytics: Your Hub for THORChain Analytics RUNE
- Zcash Update: current=v7.1.0-alpha.0 latest=v7.1.0 THORChain
- THORNODE ❗ MAINNET ❗ MIMIR VOTE: MAXOUTBOUNDATTEMPTS NETWORK: MAINNET TYPE: Coordinated (mimir vote) URGENCY: ASAP One XRP outbound (EE959E9A…3306, 149.758826 XRP) has been rescheduled since block 28632569 (over 66,000 blocks). Its destination requires an XRP destination tag and the memo has none, so no vault can sign it. Setting MAXOUTBOUNDATTEMPTS to 200 (200 x 300 = 60,000 blocks) lets the network retire it through the built-in treasury recovery path. Every other queued outbound is under 1,000 blocks old, so nothing else is affected. The user will be paid out manually. make mimir key: MAXOUTBOUNDATTEMPTS value: 200 Operational mimir: takes effect with 3 matching node votes. THORChain
- THORChain Needs a Churn for $XMR and Base Limit Orders Could Cut Slippage by Up to 20 bps RUNE
- Block Production Recovered Average Block Time: 6.1s over last 50 blocks Latest Height: 28681386 THORChain
- Block Production Stalled Average Block Time: 6.1s over last 50 blocks Slowest Block: 7.8s Latest Height: 28680221 (5728s ago) THORChain
- THORNODE ❗ MAINNET ❗ VERSION UPDATE 3.21.5 NETWORK: MAINNET TYPE: Non-coordinated URGENCY: ASAP Bifrost-only patch on 3.21.4, no consensus change. It speeds up EVM and UTXO scanning so BASE keeps up near the tip. Please upgrade soon rather than trickling in: while a vault mixes 3.21.4 and 3.21.5, the 3.21.5 nodes try to sign outbounds that 3.21.4 can't (see the last UTXO line below), so they can take short leader jails until most of the vault is upgraded. Included: * EVM: faster scanning near the tip, with compact and batched header reads on ETH, BASE and POL and the receipts check moved into the pipelined prefetch * EVM: receipts are no longer skipped for failed outbounds or direct token deposits * EVM: a deposit in a replaced block is no longer missed after a restart * EVM: optional per-chain finalized-tag skip, off by default (BIFROST_CHAINS_<CHAIN>_BLOCK_SCANNER_TRUST_FINALIZED_TAG) * UTXO: parallel prefetch and batched input reads * UTXO: outbounds whose OUT:<Solana signature> memo was cut short by an old scheduling bug can be signed again make update Image digest: sha256:2bc45fffb2a1f51f2b56c4e038ad3712d767bc3cf2411d1fc230f97851080039 THORChain
- Hey operators 👋 some nodes have fixed their BASE scanners with eRPC and we're only missing two more for the stuck BASE refund (REFUND:7A9843DD…, 14.88 BASE.ETH) 🙌 If your node's on this list, its Base RPC can't serve the receipts for Base block 53561521 (usually a pruned or snap-synced node): thor12su6q3yrs7lq60z79n4pt75vxtuntaem8xuhvu thor1xskml0m3c6z2p3r5cmfwzn72zdgxtc898lfzzy thor1rp6ll4p2qrj5k9mfelzmwv7ht0gv26pqxka8py thor1szdm49h0pq74jjc8adgk3evnkmsrwd5rtx0k68 thor1nw2jdqn5u8xsx4j0n4e8cmndapxqj47z8zhcs3 thor1m99a3vr6ckafl3wm842zx4k7nq5cempxnx44p8 thor159kkv6wf74teuxkm0vd4ude8eu9sucjytl63d0 thor10tsu3gfzgywyzuuyvmjmlpehdupdcrczemne9y Easy check, you want 35 receipts back, not null: curl -s -X POST <your-base-rpc> -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockReceipts","params":["0x33148b1"]}' | head -c 300 Fix with eRPC from node-launcher master (git pull first). Its primary needs to be an RPC that has the old receipts, your own Base RPC goes in as the failover: kubectl -n <namespace> create secret generic base-rpc2 --from-literal=url='<your-base-rpc>' cat > erpc.yaml <<'X' erpc: enabled: true config: primary: endpoint: failover: enabled: true secretName: base-rpc2 secretKey: url thornode: bifrost: erpc: enabled: true X EXTRA_ARGS="-f erpc.yaml" NET=mainnet NAME=<namespace> TYPE=validator make install Or quickest: point BIFROST_CHAINS_BASE_RPC_HOST at Devel's cat > base-rpc.yaml <<'X' thornode: bifrost: env: BIFROST_CHAINS_BASE_RPC_HOST: X EXTRA_ARGS="-f base-rpc.yaml" NET=mainnet NAME=<namespace> TYPE=validator make install It retries every 300 blocks, so as soon as 2 of you fix it, it goes through. Thanks! 🙏 THORChain
- Vault High TSS Keysign Failure Rate at block 28676995 ( Vault: 58h5 Failures (window): 70 Expected Rate (Avg + Nσ): 69 Rounds: unknown: 53 SignRound2Message: 13 SignRound1Message2: 3 SignRound3Message: 1 Blame: a9ey: 16 9gsj: 15 zga0: 7 pfj7: 6 wlnk: 5 …and 13 more THORChain
- Vault High TSS Keysign Failure Rate at block 28676982 ( Vault: 58h5 Failures (window): 70 Expected Rate (Avg + Nσ): 69 Rounds: unknown: 52 SignRound2Message: 14 SignRound1Message2: 3 SignRound3Message: 1 Blame: a9ey: 17 9gsj: 16 zga0: 7 pfj7: 6 wlnk: 5 …and 13 more THORChain
Loading the $RUNE page…