Opinion: Flow's rollback of the blockchain was decided without communication with major bridging partners, and the potential economic loss may far exceed the vulnerability itself.

On December 28, deBridge co-founder Alex Smirno posted on the X platform stating that the Flow team has decided to roll back the blockchain and claims to be in a forced synchronization window with key ecosystem partners (bridges, centralized exchanges, decentralized exchanges). As one of the main bridge providers for Flow, deBridge has not received any communication or coordination from the Flow team, which may pose significant risks. Alex Smirnov stated that a hasty chain rollback could cause economic losses far exceeding the impact of the original attack. The rollback could introduce systemic issues, affecting bridges, custodians, users, and trading partners who acted honestly during the affected window. Alex Smirnov urges all Flow validators to stop validating transactions on the rollback chain until a clear compensation plan, ecosystem partner coordination, and security team intervention are in place. Currently, RPC responses indicate that the Flow status has been rolled back, but new transactions have not yet been accepted.