Around August 31, 2023, the crypto world simultaneously staged two radically different security scenarios on the same timeline: on one side, the Cronos validators forcefully rolled back the chain state to block height 90,896 at UTC time August 30, 2023, 23:49:01, erasing all on-chain transaction records that occurred after that moment, including the actions of the attackers and normal user transactions, in order to pull the exploited Tectonic protocol and its users' funds out of the “fait accompli.” Subsequently, Cronos Network announced that the network had resumed block production and fully restored operation; on the other side, Balancer’s officials disclosed a vulnerability in the old Balancer v1 contracts, which theoretically allowed for the complete draining of LP funds, highlighting that these deprecated old version liquidity pool contracts could not be paused through permissions, but could only be publicly warned about risks and encouraged LPs to withdraw their investments, substituting information disclosure for underlying state intervention. One was a strong intervention through chain-level rollback, while the other was a weak intervention through risk disclosure and user self-service. The juxtaposition of these two events on the same day made the question of “who pays for security” no longer an abstract proposition but a direct collision between centralized intervention and decentralized risk-bearing pathways. The following narrative will analyze the trade-offs of on-chain governance behind these two disposal methods.
Cronos Emergency Rollback: Stanching the Tectonic Funds
After Tectonic encountered an exploit on Cronos, the validators made the final decision. Faced with the fact that the protocol layer had already collapsed, the Cronos validators did not follow the path of “risk announcement + user self-rescue,” but instead took emergency consensus measures to directly rewrite history at the chain level: they quickly reached a consensus to roll back the entire chain's state to a safe snapshot before the exploit occurred. According to publicly available time anchors, this snapshot was accurately locked at UTC August 30, 2023, 23:49:01, corresponding to block height 90,896, which was reaffirmed as the new “historical endpoint” and the starting point for all subsequent states.
Technically, this means that all on-chain records from block 90,896 onward to the execution of the rollback are considered to have never happened: the exploitative actions of the attacker against Tectonic were entirely erased, and the assets that were originally transferred “returned” to their pre-attack position in terms of state. However, at the same time, the normal transactions, lending adjustments, and asset transfers of ordinary users during this period were also annulled. For Tectonic users, the safety of funds was restored on paper, but at the cost of sacrificing an entire period of real on-chain life. The Cronos validators used an extreme rollback to write the answer to the question of “who pays for security” at the boundary of block 90,896.
The Cost of Rollback: Finality and Trust Fractures
From a consensus perspective, the moment UTC August 30, 2023, 23:49:01 was written into the new boundary of Cronos: the validators pulled the state back to height 90,896, essentially declaring that all on-chain transaction records after that block would no longer be seen as “history,” but merely abandoned attempts. For a chain that has always been touted as “immutable” and having “transaction finality,” such an operation directly undermined the narrative of finality—transactions that were once thought to be irreversible upon confirmation could be collectively decided to be overturned in extreme circumstances, leaving users to accept afterward which segment of the chain counts.
What was rolled back was not just the actions of the attackers. According to Cronos's handling logic, all normal users’ lending, exchanges, and asset transfers during the vulnerability period were likewise retracted, which is an inevitable cost of the rollback and the most difficult aspect to explain to ordinary participants: they followed the rules to complete transactions, only to be told that this segment of “real life” technically never existed due to a security incident. Although rollbacks have not appeared for the first time in the history of public chain security, Cronos emphasized in its announcement that “the network has resumed operation,” rather than guaranteeing that finality would absolutely not be touched, thus publicly acknowledging that chain-level strong interventions could be used in the face of extreme risks. From a governance perspective, this choice clearly stood on the side of “fund safety prioritizes over absolute immutability,” while users’ trust in finality would need to be recalibrated on a new consensus basis.
Balancer v1 Old Pool Exploit
Almost at the same time when Cronos rolled back into a “wartime state,” the other line produced a completely different approach. Balancer's officials publicly admitted that a vulnerability was found in the old Balancer v1 contracts, which theoretically allowed LP funds in the pool to be completely drained, with the specifically named being the old version pools that had long been considered “deprecated.” The problem is that these v1 pools’ designs at the time allowed almost no room for emergency brakes by the management layer; the contracts themselves could not be paused through permissions, nor was there heavy tools like chain-level state rollbacks. All the protocol could do was disclose risks and remind users to withdraw funds on their own.
Thus, on one side was the technical reality of “old contracts, deprecated, cannot be paused,” while on the other side was the lethal risk of “LP funds being drainable.” Balancer's official statement contained almost no guarantees and could only repeatedly emphasize withdrawal suggestions—not rewritten by validators nor frozen by the development team, but left to each LP to decide whether and when to leave these old pools. In comparison to Cronos's choice to use consensus rollback to back up fund safety, the Balancer v1 event presented a different governance orientation: the protocol was limited to information disclosure and risk reminders, returning the final defense line to users, meaning that in this pathway, the costs and consequences of safety ultimately had to be borne by the individual LPs.
Old Contracts in Limbo: Who Will Clean Up DeFi?
Taking Balancer v1 as an example, the management gaps during the exit cycle of the old version contracts were thoroughly exposed by this incident. As an earlier version of the automated market maker (AMM), some v1 pools had already been marked as deprecated by the officials but continued to operate on-chain from a technical standpoint, and once the contract logic was deployed, it was difficult to recover. These pools could not be directly paused through permissions; even if the protocol confirmed the serious risk of “LP funds being drainable,” it could only watch the old pools maintain operation, while remedial measures were reduced to announcements and reminders, lacking technical tools for an immediate halt.
What truly determined the size of the risk exposure was whether users were willing and able to timely migrate or withdraw funds from the old pools. Governance votes could decide to deprecate v1 and launch new versions but could not force every LP to end long-tail positions; risk disclosures can be repeatedly issued, but if users do not understand what it means that contracts cannot be paused, reminders will be diluted amidst information noise. Thus, the old contracts have accumulated a layer of “legacy risk” that is difficult to manage in a timely manner—either relying on long-term user education and proactive migration to slowly digest it or directly imposing the liquidation costs and losses on those LPs who remain in the old pools when the next vulnerability is triggered.
Two Answers on the Same Day: A Fork in Security Governance
Looking at the time window of August 31, 2023, Cronos and Balancer provided two almost opposing security answers: according to AiCoin data, Cronos rolled back the chain state to block height 90,896 through validator consensus at UTC August 30, 2023, 23:49:01, erasing all subsequent transactions and using strong intervention to “pay for” Tectonic and ordinary users; while almost at the same time, Balancer chose a weak intervention path, only disclosing in its announcement the vulnerability in the v1 old pools that allowed LP funds to be drained, acknowledging these deprecated contracts could not be paused, and then returning the decision-making power for active withdrawals to LPs. One pushes the boundary of “immutability” back a step for fund safety through chain-level rewriting; the other adheres to the principle of contract unalterability, allowing risks to slowly unfold in information disclosure and self-service migration. In the future, it is worth observing not who was “more correct” in this incident but how public chains and DeFi will redefine the boundary between security and immutability under the next round of stress tests: whether to place strong tools like rollbacks and emergency switches in the governance framework or to consider improving vulnerability response processes, old contract exit, and migration mechanisms as key dimensions of ecosystem competition and prepare well in advance.
Join our community, let’s discuss and grow stronger together!
AiCoin exclusive Hyperliquid benefits: https://app.hyperliquid.xyz/join/AICOIN88
AiCoin exclusive Aster benefits: https://www.asterdex.com/zh-CN/referral/9C50e2
On-chain Telegram community: https://t.me/AiCoinWhaleData
On-chain community: https://www.aicoin.com/link/chat?cid=N6OVMor5g
AiCoin on-chain Twitter: https://x.com/aicoinwhaledata
免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。
