deBridge says Flow's rollback lacked coordination, risking bigger losses

Flow's team decided to roll back the blockchain on December 28 and said it is operating within a forced synchronization window with key ecosystem partners, including bridges as well as centralized and decentralized exchanges, deBridge co-founder Alex Smirnov said in a post on X cited by BlockBeats. deBridge, one of Flow's primary bridge providers, reported it received no communication or coordination from the Flow team and warned of significant risk; Smirnov urged all Flow validators to stop validating transactions on the rolled-back chain until compensation plans, partner coordination and security team involvement are clarified. Smirnov said a hasty rollback could cause economic losses that exceed the impact of the original attack and introduce systemic issues affecting bridges, custodians, users and counterparties that acted honestly during the affected window; RPC responses currently indicate Flow's state has been rolled back but the network is not yet accepting new transactions.