Flow blockchain chooses to roll back the ledger after a $3.9 million vulnerability sparks a trust crisis in decentralization and cross-chain settlement
(Previous update: Flow flash crash—Foundation confirms hacking of $3.9 million, network is restarting)
(Additional background: FLOW “Flash Crash” over 30%! Suspected major network security incident, Upbit temporarily suspends deposits and withdrawals)

Table of Contents

• Event Overview
• Key Technical Decisions
• Spillover Risks and Governance Controversies
• Market Reactions and Future Observations

On the night of December 28, 2025, the Flow blockchain pressed the pause button after a hacking attack and decided to roll back the mainnet data to a pre-incident state. This move aimed to recover approximately $3.9 million in losses but also put the core principle of “immutable on-chain records” in jeopardy, casting a shadow over the crypto market before the year-end.

Event Overview

The vulnerability on February 27 existed at the execution layer. Attackers bypassed authorization checks and transferred funds through cross-chain bridges such as Celer, deBridge, and Stargate. The Flow Foundation issued the “Mainnet 28” update within 24 hours, fixing the on-chain height at 137,385,824, and putting the network into read-only mode. In other words, the entire chain was like hitting the rewind button, suspending all subsequent transaction confirmations.

Key Technical Decisions

Rollback (reversion) provides a quick remedy for blockchain issues but comes at a heavy cost. Flow’s mechanism relies on validator consensus; when validators agree to rewrite history, it is equivalent to admitting the ledger’s contents are mutable. This directly conflicts with the industry’s longstanding principle of “code is law” and also weakens external applications’ trust in Flow’s settlement layer.

Rollback operations can trigger systemic risks. If users have transferred assets via cross-chain bridges during the rollback period, the original balances on Flow will be restored after the rollback. These double balances might ultimately be settled by the bridging contracts or liquidity providers.

This warning from deBridge co-founder Alex Smirnov highlights the hidden dangers: unilateral rollback tears apart the cross-chain settlement order and creates “ghost assets” that are not matched by actual assets. When the bridge contract has recorded the funds on the other end, but Flow deletes the source payment, it effectively leaves a bad debt to third parties.

Spillover Risks and Governance Controversies

Gabriel Shapiro, General Counsel at Delphi Labs, bluntly states that the Flow Foundation is creating “unsecured assets” to mask technical flaws. He points out that this reflects highly centralized governance capable of altering ledger history, which is far from the promises of decentralization. For creators and game developers, if on-chain records can be unilaterally revoked, the legal certainty of smart contract-driven business models is undermined.

Ahead of the U.S. government’s new administration transition, regulators are accelerating the drafting of crypto-related legislation. Flow’s move exposes the weaknesses of highly concentrated governance, providing policymakers with a real-time case to assess “similar risks.”

Market Reactions and Future Outlook

FLOW tokens dropped 42% within 24 hours of the announcement, shrinking to under $200 million in market cap. To recover the $3.9 million loss, the market effectively evaporated tens of millions of dollars in valuation. Early investors like a16z and Dapper Labs now face the risk of value erosion over many years of effort.

Moving forward, Flow needs to coordinate loss settlement with cross-chain bridges, publish comprehensive technical post-mortem analyses, and rebuild validator confidence. If transparent and verifiable improvement plans are not presented, trust deficits may be difficult to repair in the short term.

While Flow chose to “turn back time,” it also opened Pandora’s box in the blockchain world’s deepest layer. Immutability is the foundation of the social contract in blockchain; once exceptions are made, future failures may follow the same path. The friction cost is no longer a technical issue but a long-term test of whether trust can be restored.