Futures
Access hundreds of perpetual contracts
CFD
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Pre-IPOs
Unlock full access to global stock IPOs
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Promotions
AI
Gate AI
Your all-in-one conversational AI partner
Gate AI Bot
Use Gate AI directly in your social App
GateClaw
Gate Blue Lobster, ready to go
Gate for AI Agent
AI infrastructure, Gate MCP, Skills, and CLI
Gate Skills Hub
10K+ Skills
From office tasks to trading, the all-in-one skill hub makes AI even more useful.
GateRouter
Smartly choose from 40+ AI models, with 0% extra fees
Flow Chain Rollback Controversy: deBridge Founder Warns of Systemic Risks
[BlockBeats] The Flow team made a controversial decision on December 28th — to roll back the blockchain. This move immediately drew widespread attention and concern within the ecosystem.
deBridge co-founder Alex Smirnov spoke out on social media, highlighting several core issues with this rollback. First, the Flow team did not sufficiently communicate and coordinate in advance with key ecosystem partners—including bridge service providers, centralized exchanges, and decentralized exchanges. As one of Flow’s main bridge providers, deBridge expressed concern—lack of coordination could entail significant risks.
Smirnov emphasized a deeper issue: rushing to roll back the chain could cause economic losses that far exceed the impact of the original attack itself. This is not just a numerical problem but involves systemic risk. Bridges, custodians, users, and trading counterparts who adhered to rules and acted honestly during the affected window could all suffer losses. The rollback would break the trust foundation on the chain.
In light of these risks, Smirnov urged all Flow validators to exercise caution: until a clear compensation plan is established, ecosystem partner coordination is completed, and the security team is fully involved, validation of transactions on the rollback chain should be paused.
Currently, on-chain data shows that Flow’s state has been rolled back, but new transactions have not yet been enabled. Every decision during this window could impact the stability of the entire ecosystem.
Flow is playing with fire; the economic loss could be even greater.
Partners were caught off guard by the sale; how can they trust?
Systemic risk is indeed severe, and there are more pitfalls to watch out for.
I'm just worried that other chains will follow suit, and then the entire ecosystem will get chaotic.
Messing up and dragging down ecosystem partners? deBridge must be furious.
The risk of rollback is actually greater than the attack itself, this logic is truly brilliant.
Flow team's communication skills are really concerning. Who would dare to integrate if this continues?
Unilateral operation without prior notice, isn't this just courting disaster?
The term "systemic risk" is used well, definitely something to be cautious about.
---
Is a rollback more damaging than an attack? That logic is quite interesting.
---
Once again proving the cost of centralized decision-making, are ecosystem partners just decorations?
---
The term systemic risk is being heard more and more; it feels like the entire chain ecosystem is walking a tightrope.
---
deBridge dares to speak frankly, I respect that, better than some projects.
---
Uncoordinated rollbacks just cause trouble, isn't that inviting problems?
---
The economic loss has surpassed the original attack, how rushed must that have been?
---
It seems that Flow's move was not very smart.
---
Wow, is it really so difficult to notify the ecosystem before an incident?
---
We must take systemic risk seriously; otherwise, it will be even more troublesome later.
This is the current state of Web3. Where is the promised decentralization?
The loss from the rollback is even greater than the original attack. Isn't this shooting oneself in the foot?
There was no communication with bridging providers like deBridge at all. Are they really trying to kill the ecosystem?
They talk about systemic risk well, but I'm afraid other chains will also follow Flow's approach.
Rollback is indeed harsh, but lack of communication is even harsher.
It's the same old story: "We're doing this for the good of the ecosystem," but in the end, it ends up harming everyone involved.
Systemic risk is a good way to describe the consequences of a lack of coordination.
So, such major actions must be announced in advance; otherwise, a trust crisis is the real disaster.