According to ChainCatcher, Alex Smirnov, co-founder of deBridge, posted on the X platform that he has noticed the news about Flow's decision to roll back the blockchain state and expressed concern about the way the 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, had not received any communication or coordination from the Flow team. Alex stated that the economic losses that could be caused by hastily rolling back the chain status might far exceed the initial security incident itself, and could trigger systemic problems, affecting cross-chain bridges, custodians, users, and counterparties that were operating normally within the relevant time window.
He highlighted potential issues such as doubling of balances and irrecoverable assets during cross-chain transactions, noting that several large cross-chain and escrow transactions had already been completed during the rollback window, including USDC-related transactions escrowed by LayerZero. Alex further compared this to previous similar 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 emphasized that the current situation requires transparency, collaboration, and restraint, rather than radical actions implemented quickly.
