First-tier network Flow canceled plans to roll back its blockchain following a $3.9 million attack, reversing course after ecosystem partners warned that rewriting chain history would undermine decentralization and create operational risks.
Instead, the network issued a statement on December 29 saying that according to a recovery plan shared with partners, it would restart from the last sealed block before transactions were halted on December 27, retaining all legitimate transaction history. The revised approach avoids chain reorganizations and instead combats fraudulent assets through account restrictions and token destruction.
CoinGecko data shows that the exploit and the initial rollback proposal had a severe impact on the FLOW token, which is down approximately 42% since the incident.
what happened
Over the weekend, Flow confirmed the attack on X, saying it exploited a vulnerability in the execution layer but did not compromise existing user balances, noting that all legitimate deposits were intact.
In an effort to recover funds and reverse the vulnerability, Flow initially proposed a rollback via X on December 27. Under the rollback recovery framework, accounts that received fraudulent tokens will be temporarily restricted while these assets will be withdrawn and destroyed, and the affected decentralized exchange pools will be rebalanced using tokens held by the foundation.
Rolling back transactions on the blockchain has previously been debated by the community as a potential way to restore the network to the state it had before a specific event, in this case an attack. Rollback will effectively eliminate malicious transactions and restore lost funds. While the idea is to help hacked networks, it raises questions about the fundamentals of encrypted networks: decentralization. No centralized entity can alter the blockchain network, ensuring it remains immutable and free from manipulation. However, if a rollback occurs, this effectively means that a centralized entity will be able to change the way the network operates.
Unsurprisingly, the Flow incident has reignited the debate over the degree of network decentralization in crisis situations, as foundations and validators weigh intervention versus immutability. Flow, for its part, has been sharply criticized by developers and infrastructure providers, who warn it could force days of coordination work on bridges and exchanges and create replay risks.
For example, Alex Smirnov, co-founder of deBridge, one of Flow’s main bridge providers, said on X that his company received “zero communication or coordination” from Flow before the rollback plan was proposed. He warned that the rollback could create unresolved liabilities for users who bridged assets in and out during the affected window.
“I like their new plan”
After facing backlash, Flow said it had revised its original plans based on community feedback.
The new plan still relies on unconventional governance measures, including temporary software upgrades that grant network service accounts powers that do not exist under normal operations. Validators must approve the changes, and Flow says permissions will be revoked once the fix is complete.
Some industry observers applauded the decision not to implement the rollback plan.
Blockchain analyst Matthew Jessup said Flow’s new recovery plan is reasonable and, unlike the original rollback plan, has no decentralization implications. “I like their new plan. It relies on validator compliance and approval. Keeping the EVM chain read-only is a good decision as it gives the team time to fix vulnerabilities.”
However, it is unclear whether the $3.9 million stolen in the breach can be recovered, as experts have expressed doubts about the possibility.
Grant Blaisdell, co-founder of blockchain analytics firm Coinfirm and CEO and co-founder of Copernic Space, told CoinDesk that recovering hacked funds largely depends on where the funds go. “Whether the funds land on a centralized exchange, the speed with which incidents are reported, and the exchange’s willingness to cooperate all play a role,” he said. “Once funds have been transferred, recovery becomes a complex legal process across multiple jurisdictions.”
Jessup also said he doubted they would be able to recover the assets, noting that the hackers had moved the assets into the Bitcoin network after the attackers moved them off-network, mostly through bridges in the Ethereum network. Arkham partner B-Block confirmed this in an X post.
Read more: Arthur Hayes raises community outrage as he floats idea of rolling back Ethereum network to stop $1.4B Bybit hack
