温馨提示：本站仅提供公开网络链接索引服务，不存储、不篡改任何第三方内容，所有内容版权归原作者所有
AI智能索引来源：http://www.bee.com/zh/63487.html
点击访问原文链接

A hacker attack caused Flow to be cut short, and the rollback plan sparked an internal conflict within the ecosystem. | Bee Network

进入原网站 导航首页
A hacker attack caused Flow to be cut short, and the rollback plan sparked an internal conflict within the ecosystem. | Bee Network Login 熱門新聞 Meme Launchpad AI 代理商 DeSci 熱門鏈瀏覽器 新人必讀 衝百倍幣 蜜蜂遊戲 必備網站 必備APP 必關大神 DePIN 新人必備 教我避坑 基本工具 深度網站 交易所 NFT 工具 你好， 登出 Web3宇宙 遊戲 DApp 蜂巢 增長平台 生態 搜尋 英語 Coins儲值 登入 下載 Web3大學 遊戲 DApp 蜂巢 生態 家•分析•正文 A hacker attack caused Flow to be cut short, and the rollback plan sparked an internal conflict within the ecosystem.分析2 个月前更新懷亞特 18,394 17 作者 |亞瑟（ @Asher_0210 )

Last Saturday afternoon, a sudden hacker attack threw the Flow network into chaos. This Layer 1 network, built by the Dapper Labs team and designed for next-generation applications, games, and digital assets, watched helplessly as $3.9 million in assets were transferred off-chain due to an exploited execution-layer vulnerability. Following the attack, its token, FLOW, plummeted by half in a short period , from $0.173 to $0.079, and has since rebounded slightly to around $0.107.

FLOW K-line chart

Below, Odaily Planet Daily summarizes the Flow theft incident, the official response, and why it triggered strong questions from Flow partners and the community.

Flow issued an urgent response: isolating the network and announcing a rollback plan. Following the attack, the Flow Foundation responded swiftly and confirmed the details of the incident. The attackers exploited an execution-layer vulnerability to transfer approximately $3.9 million in assets. The incident did not affect users’ existing balances, and user deposits remain safe. The attacking addresses have been flagged, and the money laundering route is being continuously traced. The Foundation has submitted asset freeze requests to Circle, Tether, and several major exchanges.

To clean up illegitimate transactions on the blockchain and fix the vulnerability, the Flow Foundation isolated the network and released Mainnet 28, the mainnet vulnerability fix. The Foundation’s initial solution was to roll back the network state to a checkpoint before the attack , specifically Cadence block height 137363395, thus deleting all transactions generated within approximately six hours. Regardless of the transaction’s legitimacy, all transactions were cleared, and users needed to resubmit them after the node restarted. The Foundation believes this solution is the safest path to restore network integrity and has repeatedly emphasized that user funds will not be affected throughout the process, while promising to provide updates on the event’s progress every two hours.

This rollback decision, though seemingly decisive, quickly ignited a firestorm within the ecosystem—because the hacker’s funds had already been bridged off-chain, the rollback had no impact on the attackers, only affecting honest users and partners.

Cross-chain bridge partners and community users strongly opposed the rollback plan, which was met with fierce criticism. Following the announcement of the rollback plan, cross-chain bridge partners and community users within the Flow ecosystem quickly faced collective criticism. Alex Smirnov, co-founder of deBridge, Flow’s main cross-chain bridge partner, publicly criticized the decision 在X平台上 , stating it was too hasty and lacked prior communication with key bridging partners. As a crucial asset channel within the Flow ecosystem, deBridge received no advance notice of the rollback.

Smirnov pointed out that the potential damage from a rollback could far exceed the initial hack itself. Because cross-chain assets have already circulated across multiple systems, a forced rollback would trigger serious problems such as asset duplication and inconsistent custody status. Ultimately, the bridges, users, and counterparties operating normally during the window period would suffer the consequences. He disclosed that approximately $200,000 and $50,000 in deposits on deBridge fell within the rollback window . Once the rollback is executed, it could lead to the disappearance of funds on one side or, in extreme cases, the duplication of assets.

Based on the aforementioned risks, Smirnov called on Flow validators to suspend block production and validation until the compensation plan, partner coordination mechanism, and independent security team intervention plan are all clearly 德菲ned. Similar issues are not isolated cases. As the primary cross-chain custodian of USDC on the Flow network, LayerZero also faces the risk of approximately $220,000 and $180,000 in cross-chain transactions falling within the rollback window.

Beyond the cross-chain bridge partners within the Flow ecosystem, on the X platform, users began expressing widespread concerns about fund security, while developers questioned the network’s reliability and governance mechanisms under extreme conditions. Investor sentiment simultaneously turned cautious, intensifying selling pressure. Numerous voices pointed to the rollback itself exposing the reality of centralized control on-chain, rapidly escalating what began as a technical incident into a crisis of trust.

Some community opinions have further targeted the core principles of blockchain. Some argue that rollback directly undermines transaction finality and immutability, making Flow more like a consortium blockchain susceptible to administrative intervention at critical moments. Others compare historical security incidents with other public blockchains, pointing out that similar situations are typically handled by isolating attacker addresses and freezing fund flows, rather than performing a global rollback of the entire network state.

Crypto KOL Wazz ( @WazzCrypto ) stated on the X platform that Flow’s rollback decision was one of the worst handling methods he had ever seen. In his view, the attackers had already transferred approximately $4 million in assets off-chain, and would hardly be affected by the rollback. The real cost would be borne by innocent users who were using the network normally through the cross-chain bridge.

Flow officials changed their stance: abandoning rollback and adopting a new isolation recovery solution. Faced with strong opposition from partners and the community, the Flow team ultimately decided to abandon the network rollback and instead opt for the “Isolation Recovery Plan.” This plan was developed through direct negotiations with cross-chain bridges, exchanges, and infrastructure partners, and its key points include:

No rollback/reorganization, all legitimate user activity is preserved; No need for partners to replay transactions; Over 99.9% of accounts were unaffected and will resume normal operation immediately after restarting; Upon restart, accounts receiving illegally minted tokens will be temporarily restricted. In addition, the network will be restored in phases:

In the first phase, the Cadence environment was launched, and EVM was temporarily restricted. The second phase, Cadence repair (approximately 24 to 48 hours); In the third phase, the EVM was repaired and restarted. In the fourth phase, cross-chain bridges/exchanges will resume operation. The specific resumption time will be determined by the operator after confirming stability based on the actual situation. In addition, Dapper Labs, the team behind Flow, expressed its support for this solution 在X平台上 , stating that it “preserves legitimate activity and provides a clear path to recovery.”

This “abandoning rollback” stance has eased tensions in the short term and prevented the spread of systemic risks that a rollback might have triggered. As of now, the network is still in a phased coordination and recovery process, and officials have stated that user funds remain safe.

In the highly uncertain environment of the 加密貨幣 market, this crisis may become a major watershed in Flow’s development path, and its long-term impact remains to be seen.

本文源自網路： A hacker attack caused Flow to be cut short, and the rollback plan sparked an internal conflict within the ecosystem.

Related: Has Bitcoin’s four-year cycle failed? Original article edited by: Denise, a core contributor to Biteye From the halving in April 2024 to reaching a new high of $120,000 in October 2025, Bitcoin took nearly 18 months. Looking at this path alone, it seems to still be operating according to a cyclical pattern: a bottom after the halving, a peak within a year, and then a correction. But what really puzzled the market was not whether it rose or not, but that it didn’t rise as usual. There were no consecutive surges like in 2017, nor the nationwide frenzy of 2021. This round of market activity appears slow, sluggish, and with reduced volatility. ETFs have seen repeated upward movements, altcoins have lacked momentum, and some even fell below $90,000 in less than a month after reaching…

#分析# 加密# 脫機#交換#市場#代幣© 版權聲明文章版权归作者所有，未经允许请勿转载。 上一篇 The man who struck a chord with American society has issued a cryptocurrency. 下一篇 Crypto2026 Outlook II. Macroeconomic Review and Forecast 相關文章 為什麼 Perp DEX 空投仍然重要：您不能錯過的三個專案 6086cf14eb90bc67ca4fc62b 21,357 1 Ethereum’s identity dilemma: Is it cryptocurrency, or a shadow of Bitcoin? 6086cf14eb90bc67ca4fc62b 17,942 2 Binance 8th Anniversary Highlights 6086cf14eb90bc67ca4fc62b 32,679 8 RWA Weekly Report｜Stablecoin Market Cap Drops 4.3%; White House to Hold Another Stablecoin Yield Discussion Meeting Today (Feb 4-10) 6086cf14eb90bc67ca4fc62b 7,581 When the NFT bubble bursts, who will still be able to tell the “IP story” well? 6086cf14eb90bc67ca4fc62b 16,680 Betting on Transparency: How Prediction Markets Are Pricing the Digital Asset Market Transparency Act of 2026 6086cf14eb90bc67ca4fc62b 9,343 Bee.com 全球最大的 Web3 入口網站 合作夥伴 CoinCarp Binance CoinMarketCap CoinGecko 幣活 盔甲 下載Bee Network APP開啟您的Web3之旅 白皮書 角色 常問問題 © 2021-2026.版權所有。. 隱私政策 | 服務條款 下載蜜蜂網路APP 並開始 web3 之旅 全球最大的Web3入口網站 合作夥伴 CoinCarp Binance CoinMarketCap CoinGecko Coinlive Armors 白皮書 角色 常問問題 © 2021-2026.版權所有。. 隱私政策 | 服務條款 搜尋 搜尋站內鏈上社群媒體新聞 熱門推薦： 擼毛打金 數據分析 必關大神 教我避坑 繁體中文 English 简体中文 日本語 Tiếng Việt العربية 한국어 Bahasa Indonesia हिन्दी اردو Русский 繁體中文

智能索引记录