Flow Network Revises Recovery Strategy After Backlash
The Layer 1 blockchain network, Flow, has decided against rolling back its blockchain following a significant exploit that resulted in a loss of $3.9 million. This decision was influenced by pushback from partners within its ecosystem who argued that altering the chain’s history would threaten decentralization and introduce operational risks.
In a newly issued statement, Flow outlined a recovery strategy shared with its partners. On December 29, the network announced that trading would restart from the last confirmed block prior to the suspension on December 27, thereby preserving all legitimate transaction records. This updated approach aims to avoid chain rewriting and instead focuses on addressing the misuse of assets through account restrictions and token destruction.
According to CoinGecko, the initial exploit and the rollback proposal have resulted in a severe drop in the FLOW token’s value, which has decreased by about 42% since the event.
Details of the Incident
Over the weekend, a vulnerability in the execution layer of Flow led to confirmed attacks. It was reported that user balances remained unaffected, with all legitimate deposits intact.
To reclaim lost funds, a proposal was made through Flow to utilize its rollback recovery framework. This plan included temporarily restricting accounts that received the fraudulent tokens until those assets were burned. Additionally, affected decentralized exchange pools would be rebalanced using tokens held by the Foundation.
The concept of rolling back transactions has been debated within the community as a potential means of returning the network to its prior state after an incident, like an attack. While this might effectively erase harmful transactions and restore lost funds, it raises essential questions about the integrity of decentralization, a core principle of blockchain technology. While a centralized entity shouldn’t be able to manipulate the blockchain’s immutability, a rollback suggests possible intervention.
This situation reignited discussions about how decentralized networks respond during crises, as various stakeholders consider intervention versus maintaining immutability. Flow faced considerable criticism from developers and infrastructure providers, who highlighted that a rollback could lead to necessary adjustments for bridges and exchanges and could create future risks.
For instance, Alex Smirnov, co-founder of deBridge, expressed concern over the lack of communication from Flow regarding the rollback plan. He warned that it could create unresolved liabilities for users during the affected timeframe.
Response to Feedback
In light of the backlash, Flow opted to modify its initial plans based on community feedback.
The revamped strategy will still involve specific governance protocols, including temporary upgrades to the software that grant service account privileges not typically available. Verifiers must approve these changes, and Flow assures that these privileges will be revoked once the corrections are carried out.
Some within the industry have commended Flow for not moving forward with the rollback plan.
Blockchain analyst Matthew Jessup suggested that the new recovery plan is sound, emphasizing it does not compromise decentralization. He noted that compliance and approvals depend on validators, and maintaining the EVM chain in a read-only state provides the team with necessary time to address the exploit.
However, experts remain skeptical about the recovery of the lost $3.9 million. Grant Blaisdell, co-founder of CoinFarm and CEO of Copernic Space, pointed out that recovering hacked funds is complicated and largely depends on their eventual destination. Factors like whether the funds went to a centralized exchange and how swiftly the incident was reported come into play, complicating the legal recovery processes.
Jessup also remarked on how the attackers primarily shifted assets from Flow to the Ethereum network before transitioning to Bitcoin, raising doubts about whether recovery is feasible. This movement was confirmed by an X Post from Arkham Partner B-Block.
