2025-12-28 12:31:30

The Flow ecosystem recently experienced some unpleasant incidents. deBridge co-founder Alex Smirnov pointed out that Flow decided to perform a blockchain rollback without sufficient communication and coordination with key ecosystem parties such as bridging protocols and exchanges. This move could pose a greater risk than the original security vulnerability.

To be honest, as one of the main cross-chain bridging providers for Flow, deBridge did not receive any prior notice. This has triggered a series of chain reactions—assets of cross-chain users may face duplication issues, and deposits may not match the records.

Alex Smirnov subsequently called on Flow to adopt a more cautious coordination approach, highlighting that there is still significant room for improvement in communication mechanisms among different participants in the current cross-chain ecosystem. For users relying on multi-chain deployments, this incident serves as a reminder to pay more attention to the maturity of ecosystem coordination when choosing cross-chain solutions.

FLOW-12,1%

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.

11 Likes

Reward
11
4
Repost
Share

Comment

0/400

ZkProofPudding

· 11h ago

Flow's operation is really top-notch, they don't notify in advance even for rollbacks, deBridge is just stunned Speaking of which, cross-chain has really become a big mistake these days, it's outrageous when assets don't match accounts Flow's coordination ability is worrying, are ecosystem partners all invisible? Rollback is riskier than a vulnerability, I really can't understand this logic Choosing a cross-chain solution now depends on which ecosystem's coordination is reliable, otherwise, expect a crash deBridge being exploited like this, multi-chain users will have to pay the price What does this show? Even big projects need to learn what "collective effort" means If Flow keeps going like this, ecosystem partners will all run away

View OriginalReply0

YieldWhisperer

· 12h ago

Flow's operation is really outrageous, not even informing the ecosystem about the rollback? It's probably more painful than the vulnerability itself. deBridge's guy is right, choosing the wrong cross-chain solution can really lead to heavy losses. Damn, when the assets don't match the accounts, anyone would get annoyed. Flow needs to reflect seriously, the ecosystem coordination is too weak. That's why I now have to be very careful when choosing a cross-chain solution, can't just play around. The rollback was announced in advance, how did it happen, it's a bit outrageous. Cross-chain ecosystems still need more transparency, otherwise this kind of thing will definitely happen again. They moved without even notifying anyone, Flow is a bit too self-righteous. The issue of duplicate assets, how annoying is that... Poor ecosystem coordination, even the best solutions are useless.

View OriginalReply0

AirdropCollector

· 12h ago

Flow this time is really outrageous, not even notifying the bridging party when rolling back themselves. Who can handle this? It's just outrageous. If the assets don't match the accounts, can't you at least ask the ecosystem partners first? Flow's approach makes cross-chain users feel so exhausted. When choosing a solution, you also have to see who is more reliable. No rollback notifications? This coordination ability is really worrying. Friends deploying across multiple chains, be careful. You need to choose ecosystems with good coordination. That's why many people are still on the sidelines; the ecosystem is not mature, and the risks are too high.

View OriginalReply0

GasFeeCryBaby

· 12h ago

Flow's operation is truly outrageous, not even sending a single notification before rolling back. Isn't this digging a hole? deBridge got played, cross-chain users are even worse, mismatched assets are really the worst. The ecosystem coordination is indeed a disaster, who would still dare to trust cross-chain here? The Flow team's move is a textbook example of a negative role model. What are the exchanges thinking? Who will bear this risk? If the ecosystem isn't mature, don't make reckless moves. Every time, they cause chaos. Partners are kept in the dark, what trust can there be? This is a true reflection of the chaotic coordination in Web3, there's nothing we can do. There should have been a unified notification mechanism long ago. It's too outrageous. Making such a basic mistake as asset mismatch is just mind-blowing.

View OriginalReply0