NFT public chain Flow experienced an unprecedented security shock at the end of the year. A hacker attack involving 10% of the total supply caused this expanding ecosystem project to fall into trouble.

Here's what happened: the hacker illegally minted approximately 150 million FLOW tokens on the Flow network in one go. The speed was astonishing—these tokens were quickly transferred out, with some flowing to a major exchange and eventually exchanged for BTC for withdrawal. The method was covert, the scale was massive, and the entire ecosystem suffered serious damage.

Flow's official team made a difficult decision: to urgently shut down the entire network. This was initially to stop the bleeding, but the aftereffects followed. The leading NFT lending platform Flowty was forced to suspend settlements due to the network outage, and some users' lending assets faced processing delays.

The most interesting part was the community's subsequent discussion—should they perform a chain rollback? This issue once sparked fierce debates. Some supported rolling back to restore the stolen assets, while others firmly opposed (after all, this would break the immutability feature of blockchain). The Flow Foundation ultimately listened to the opposition, abandoned the rollback plan, and chose a more transparent recovery path: first restore the Cadence mainnet, relaunch the EVM chain within 24 hours, then precisely locate and destroy all illegally minted tokens.

This crisis tested not only technical emergency response capabilities but also the governance maturity of a public chain project.