THORChain halted block processing on October 31 due to a software bug triggered by an Ethereum block reorganization

Overview Debates Related claims Topics

Attackers initially swapped 234 million stolen USDT for TRX on SunSwap, using approximately 7,700 TRON network addresses before moving funds off TRON.

In the first four days following the Binance hack, attackers utilized roughly 12,000 temporary wallets across 11 blockchains and conducted over 40,000 transactions to obscure funds.

Blockchain network THORChain halted trading on 10 of its 13 chains over the weekend of October 31 to November 1, 2026, after being used by the Binance attacker to route funds.

Morpho secured a position among the 20 leading blockchain protocols overall by user-paid fees in 2026, according to a report by 1kx.

Over a 51-hour period ending November 1, 2026 at 05:33 UTC, approximately $147 million left the TRON network via 1,113 transfers, primarily migrating to Ethereum as ETH.

A Polygon Improvement Proposal was submitted to execute a blockchain rollback deleting stolen POL tokens from hacker-controlled wallets

Polygon validators froze approximately $6.5 million worth of POL tokens associated with the 2026 Binance and Polymarket exploits

Ripple froze $40 million worth of assets connected to the 2026 Binance hack

Issuers and blockchain networks froze $2.85 billion of the cryptocurrency stolen in the 2026 Binance hack

Hyperliquid co-founder Jeff Yan recalled that a year prior he jokingly told Sprecher that success meant Intercontinental Exchange building on Hyperliquid technology

THORChain node operators voted to restart the network using updated node software and subsequently processed transactions originating from FBI-identified hacker addresses

A proposed Polygon hard fork to recover stolen Binance and Polymarket funds is supply-neutral and would not change the total supply of POL tokens by minting or burning coins

If approved by Polygon governance, hard fork client development and validation on Polygon's Amoy testnet are expected to take approximately two weeks before mainnet deployment

The Polygon community scheduled the hard fork proposal to recover stolen Binance and Polymarket funds for discussion on the Protocol Governance Call on November 5, 2026, at 14:30 UTC

ZIP 2003 states that the Zcash NU7 network upgrade at block height 3,543,405 will disable version 4 transactions, rendering unmigrated funds in the Sprout privacy pool unspendable

A proposed Polygon hard fork to recover stolen Binance and Polymarket funds would zero out five attacker-controlled addresses and transfer matching amounts to verified recovery accounts controlled by Binance and Polymarket at a predetermined block number

ZIP 2003 defines Zcash's NU7 upgrade specification that rejects version 4 transactions, leaving open the possibility of restoring access to Zcash's Sprout privacy pool in a future upgrade while warning spending may never resume

Zcash developers scheduled the NU7 upgrade to eliminate Sprout's older transaction format to reduce software complexity and security risks in payment-verification code

Public blockchain immutability relies on confirmed transactions remaining unalterable to maintain trust across decentralized ledgers

Zcash block height stood at 3,542,391 at 05:24 UTC on November 5, 2026, leaving roughly 21 hours until Zcash's NU7 activation at the 75-second target block time