Layer 1 network Flow abandoned plans to roll back its blockchain following a $3.9 million exploit, reversing course after pushback from ecosystem partners who warned that rewriting the chain’s history would harm decentralization and create operational risks.
Instead, the network issued a statement on December 29 saying it would restart from the last sealed block before trading stopped on December 27, thereby preserving all legitimate transaction history, according to a recovery plan shared with partners. The revised approach avoids a chain reorganization and instead targets fraudulent assets via account restrictions and token destruction.
The exploit and initial rollback proposal took a heavy toll on the FLOW token, which is down about 42% since the incident, according to CoinGecko data.
What happened
Over the weekend, Flow confirmed the attack on X, saying it exploited a vulnerability in its execution layer but did not compromise existing user balances, noting that all legitimate deposits remained intact.
To recover the funds and undo the exploit, Flow initially suggested the restore proposal via X on December 27. Under rollback recovery, accounts that received fraudulent tokens will be temporarily restricted while those assets are removed and burned, and affected decentralized exchange pools will be rebalanced using tokens held by the foundation.
Canceling transactions on a blockchain has already been discussed by the community as a potential way to return a network to a state prior to a specific event, in this case the attack. The rollback would effectively erase malicious transactions and restore lost funds. If this is about helping a hacked network, it raises questions about the foundation of crypto networks: decentralization. No centralized entity can modify the blockchain network, ensuring that it remains immutable and free from manipulation. However, if a rollback occurs, it effectively means that a centralized entity will be able to change the way the network operates.
Unsurprisingly, the Flow episode renewed this debate about the degree of network decentralization in crisis situations, as foundations and validators weigh intervention against immutability. In the case of Flow, there was strong criticism from developers and infrastructure providers, who warned that it could force days of reconciliation work for bridges and exchanges and introduce replay risks.
For example, Alex Smirnov, co-founder of deBridge, one of Flow’s main bridge suppliers, said on X that his company received “no communication or coordination” from Flow before the restoration plan was launched. It warned that a cancellation could have created unresolved liabilities for users who moved assets in or out during the affected window.
“I like their new plan”
Following the backlash, Flow said it revised its initial plan in response to feedback received from the community.
The new plan still relies on extraordinary governance measures, including a temporary software upgrade granting the network service account powers that do not exist during normal operation. Validators must approve the change, and Flow says permissions will be revoked once the fix is complete.
The decision not to implement the dismantling plan was applauded by some industry observers.
Blockchain analyst Matthew Jessup said that Flow’s new recovery plan is solid and, unlike the original recovery plan, has no decentralization implications. “I like their new plan. It relies on validators to comply and approve. Keeping the EVM chain read-only is a good move because it gives the team time to fix exploits.”
However, it remains unclear whether the $3.9 million recovered from the exploit can be recovered, as experts have cast doubt on the possibility.
Recovery of hacked funds largely depends on where they end up, Grant Blaisdell, co-founder of blockchain analytics firm Coinfirm and CEO and co-founder of Copernic Space, told CoinDesk. “The fact that the funds landed on a centralized exchange, how quickly the incident was reported and the willingness of the exchange to cooperate all play a role,” he said. “Once funds are removed from the market, recovery becomes a complex legal process in multiple jurisdictions. »
Jessup also said he doubted they could recover the assets, noting that the hacker moved them to the Bitcoin network, after the attackers primarily moved the assets off-network via bridges on the Ethereum network. This was confirmed in an X post from B-Block, an Arkham partner.
Read more: Arthur Hayes floats idea of rolling back Ethereum network to undo $1.4 billion Bybit hack, drawing community ire
