PANews December 28 News, deBridge co-founder Alex Smirno posted on 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 Flow’s main bridging providers, deBridge has not received any communication or coordination from the Flow team, which may pose significant risks. Alex Smirnov stated that the economic losses caused by a hasty chain rollback could far exceed the impact of the original attack, and that a rollback could introduce systemic issues, affecting bridges, custodians, users, and counterparties who act honestly during the affected window. Alex Smirnov urges all Flow validators to stop validating transactions on the rollback chain until relevant compensation plans are clarified, ecosystem partner coordination is completed, and security team intervention occurs. Currently, RPC responses indicate that the Flow status has been rolled back, but new transactions have not yet been accepted.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
Opinion: Flow's rollback of the blockchain poses significant risks due to lack of communication with major bridging partners
PANews December 28 News, deBridge co-founder Alex Smirno posted on 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 Flow’s main bridging providers, deBridge has not received any communication or coordination from the Flow team, which may pose significant risks. Alex Smirnov stated that the economic losses caused by a hasty chain rollback could far exceed the impact of the original attack, and that a rollback could introduce systemic issues, affecting bridges, custodians, users, and counterparties who act honestly during the affected window. Alex Smirnov urges all Flow validators to stop validating transactions on the rollback chain until relevant compensation plans are clarified, ecosystem partner coordination is completed, and security team intervention occurs. Currently, RPC responses indicate that the Flow status has been rolled back, but new transactions have not yet been accepted.