The Flow team made a highly controversial decision on December 28th — to roll back all on-chain data. Once this news broke, no one in the ecosystem could stay calm.

Alex Smirnov, co-founder of a well-known bridging service provider, voiced three major issues on social media:

**The biggest point of contention is the lack of coordination.** The Flow team did not properly communicate with ecosystem partners (such as bridge providers, CEXs, DEXs) beforehand. As the main bridge operator for Flow, they were completely reactive, and the risk exposure was suddenly amplified.

**A deeper hidden danger is that economic losses could backfire.** Rushing to roll back the entire chain could cause economic shocks far beyond the initial attack. Those who acted properly during the impact period—bridges, custodians, users, and counterparties—suffered unjust losses. Trust in a chain is built with every transaction; a rollback erases it all.

**He issued a warning:** All Flow validators should hold off on acting for now. Until the compensation plan is implemented, all parties are coordinated, and the security team has completed a thorough assessment, do not validate new transactions on the chain. Now that the chain has been rolled back and new transactions have not yet resumed, every decision during this window will determine whether the entire ecosystem can stabilize.