Alex Smirnov, co-founder of deBridge, posted on the X platform that he has noticed the news regarding Flow's decision to roll back the blockchain state and expressed concern about the manner in which this decision was implemented. Alex pointed out that although Flow officially stated it was in a synchronization window with key ecosystem partners such as bridges, CEXs, and DEXs, deBridge, as one of Flow's main cross-chain bridges, has not received any communication or coordination from the Flow team. Alex stated that the economic losses caused by a hasty rollback of the chain state may far exceed the initial security incident itself and could trigger systemic problems, affecting cross-chain bridges, custodians, users, and counterparties operating normally within the relevant time window. He highlighted the potential for balances to double and assets to become unrecoverable during cross-chain operations, noting that several large cross-chain and custodial transactions had already been completed during the rollback window, including USDC-related transactions custodied by LayerZero. Alex further compared this to similar past incidents, such as BNB Chain, which primarily focused on isolating attackers rather than rolling back the entire state. He called on Flow validators to suspend verification of the rollback chain until a clear remedial plan is in place, ecosystem coordination is completed, and security organizations are involved, in order to avoid irreversible consequences. He also emphasized that the current situation requires transparency, collaboration, and restraint, rather than radical actions implemented quickly.