{ "id": 57964, "date": "2025-12-29T09:33:32", "date_gmt": "2025-12-29T02:33:32", "guid": { "rendered": "https:\/\/hbbgroup.net\/flow-validators-urged-to-halt-work-after-divisive-blockchain-rollback\/" }, "modified": "2025-12-29T09:33:32", "modified_gmt": "2025-12-29T02:33:32", "slug": "flow-validators-urged-to-halt-work-after-divisive-blockchain-rollback", "status": "publish", "type": "post", "link": "https:\/\/hbbgroup.net\/en_us\/flow-validators-urged-to-halt-work-after-divisive-blockchain-rollback\/", "title": { "rendered": "Flow validators urged to halt work after divisive blockchain rollback" }, "content": { "rendered": "
\n

deBridge founder Alex Smirnov has urged validators on the Flow blockchain to stop processing transactions until the Flow Foundation devises a remediation plan for users impacted by its controversial rollback of the chain.<\/p>\n

The rollback was in response to the theft of $3.9 million<\/a> on Dec. 27 when an attacker exploited a flaw in Flow\u2019s execution layer and siphoned funds off the chain via multiple cross-chain bridges.<\/p>\n

deBridge is one of Flow\u2019s main bridge providers and Smirnov called<\/a> on Flow to clarify plans to address doubled balances for users who bridged out during the rollback window.<\/p>\n

Flow validators haven\u2019t been able to heed Smirnov\u2019s call just yet, as data<\/a> from Flowscan shows that the Flow blockchain remains stuck at block height 137,385,824, where it has been since 11:24 pm UTC on Saturday.<\/p>\n

Around the same time, the Flow Foundation said<\/a> the blockchain was expected to restart within the next four to six hours. The exploit and Flow\u2019s rollback have driven the FLOW token down 42% since the attack, CoinGecko data<\/a> shows.<\/p>\n

Rollback sparks debate<\/h2>\n

Chain rollbacks are controversial because they undo confirmed transactions, creating uncertainty over user account balances while undermining confidence in the network\u2019s decentralization<\/a> and security.<\/p>\n

Smirnov slammed the \u201crushed decision,\u201d claiming that Flow failed to notify ecosystem partners that it would rollback the chain,<\/a> and argued that the chain rollback would cause even more financial damage than the original exploit:<\/p>\n

\u201cA rollback introduces systemic issues that affect bridges, custodians, users, and counterparties who acted honestly during the affected window.\u201d<\/p><\/blockquote>\n

That includes crypto exchanges listing the Flow (FLOW<\/a>) token, which Smirnov noted<\/a> could have put them in a difficult position regarding how to handle deposits and withdrawals during the rollback window.<\/p>\n