2025-12-29 12:20:32

The rollback controversy on the Flow chain has been causing a lot of buzz these days. The official claims to be coordinating mandatory synchronization with key ecosystem partners such as bridges, CEX, DEX, etc. However, the main bridge service provider DeBridge publicly complained — they never received any communication or notice.

This is quite awkward. If a rollback is executed impulsively, the involved financial risk is approximately 65%. Poor internal communication within the ecosystem and lack of transparency in decision-making and execution can easily trigger a trust crisis in Web3. If key links like bridging, exchanges, and DEX are not aligned in advance, the security and liquidity of on-chain assets will be impacted.

FLOW-2,5%

View Original

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.

19 Likes

Reward
19
6
Repost
Share

Comment

0/400

CryptoMom

· 12h ago

Flow's official move is really outrageous. They started rolling back without even notifying DeBridge. Are they playing with fire? This is a classic case of one hand informing while the other acts, and Web3 fears this kind of thing the most. 65% of the risk is on the table. Who dares to move? Ecosystem partners are all kept in the dark. Where is the promised decentralization? It’s more authoritarian than centralized systems. DeBridge's comment is spot on. The official's face has been swollen from the blow. This time, you can really see which chain has integrity. Flow truly let everyone down this time. They haven't even coordinated the ecosystem properly but still dared to roll back—are they betting on luck? I just want to know how many people are worried about their assets right now... This transparency issue in decision-making is more deadly than technical bugs.

View OriginalReply0

MetaNomad

· 12-29 21:49

Flow official is doing this again? deBridge was completely kept in the dark, the transparency is truly remarkable. What's funny is that they still have the nerve to talk about coordination, but in reality, they didn't even receive the message. Isn't this shooting themselves in the foot? Who will bear the 65% risk? Such operations can easily ruin the ecosystem. Web3 is all about transparency and trust. But what about now? Working behind closed doors and forcing implementation—no wonder problems keep arising. If funds are lost this time, Flow's reputation will be completely ruined.

View OriginalReply0

GateUser-7b078580

· 12-29 12:51

Data shows a 65% risk of this rollback, but the issue isn't the number itself—it's that the communication mechanism has completely broken down. DeBridge didn't even receive a notification? Nevertheless, such incidents keep happening repeatedly on the chain...

View OriginalReply0

FreeMinter

· 12-29 12:41

Even the officials themselves haven't figured out what they're doing, how could DeBridge possibly receive notifications... Isn't this just the old trick in Web3? The promised decentralization still ends up a mess.

View OriginalReply0

RugResistant

· 12-29 12:24

Flow's rollback this time is really funny, the officials are just acting out a play themselves? DeBridge didn't even notify us before forcing a rollback, isn't this just the prelude to a rug pull? 65% risk? I think 99% of people are going to get cut. The official talks about ecosystem coordination, but the bridging parties look completely confused. This transparency is just too touching. Is this what Web3 is? If they can't even communicate, what decentralization are they talking about? Feels like someone is about to lose everything again.

View OriginalReply0

FlatTax

· 12-29 12:22

Flow official operation is really amazing, forcing synchronization without even notifying DeBridge? Isn't this inviting a trust crisis? DeBridge was kept in the dark and still has to take the blame, who will bear the 65% risk? Another "internal coordination" farce, this is how Web3 gets messed up. The official speaks for itself, ecosystem partners are all confused... if this bridging fails, the entire ecosystem will suffer. Is communication this difficult? Don't you need on-chain notifications? A single rollback can ruin Flow's reputation so badly, it's hilarious.

View OriginalReply0