Cronos' Single-Player Philosophy: Theft Is No Big Deal, Just Roll Back

Original Title: "Cronos' Single-Player Philosophy: Theft Is No Big Deal, Just Roll Back"
Original Author: Azuma, Odaily Planet Daily

On August 30, Tectonic, the largest lending protocol within the Crypto.com affiliated blockchain Cronos, suffered a hacker attack.

The attack itself was not particularly complex; the attackers inflated the price of the low liquidity Tectonic governance token TONIC by about 100 times in approximately 20 minutes, then used these inflated TONIC tokens as collateral to borrow other assets from Tectonic, involving an amount of about $75 million, of which about $6 million has been cross-chained to Ethereum.

More dramatic than the attack method was Cronos' response plan. After the attack occurred, Cronos first paused the network on the evening of August 30 (stopping the network immediately, showing early signs), preventing the outflow of other stolen funds; then on August 31, it announced a network restart plan, declaring that the chain state would be rolled back to before the theft on August 30, restarting the network from block height 90896189.

The Huge Controversy of the Rollback

The so-called blockchain rollback can be simply understood as reverting the network's state to a certain point in the past, after which transactions, transfers, and smart contract operations that occurred will, in principle, disappear from the new chain history.

This was also Cronos' choice this time. From the results, this is indeed the least troublesome and possibly the most effective solution. When the attack occurred, about $75 million in assets were affected, but before Cronos paused the chain, only about $6 million successfully escaped cross-chain, with the majority of the remaining assets still on the Cronos chain. Since the money hasn't run away, they simply deleted the on-chain history after the attack— in theory, most of the losses would also disappear.

From the perspective of protecting user funds, Cronos' choice is hard to criticize. If they hadn't done this, they might have had to watch the attackers layer by layer transfer the funds away, and how much could be recovered would depend entirely on luck after the security team tracked, froze, and negotiated.

Of course, the cost of the rollback is also evident. The attackers' transactions can disappear, but normal transfers, transactions, and settlements by ordinary users during this period will also vanish. In this incident, the Cronos network restarted from block height 90896189, but before the chain was paused, the network had reached block height 90907150, leaving a gap of 10,961 blocks—this also means that all normal transactions conducted within these more than ten thousand blocks have been canceled.

To give an extreme example, if you happened to be using the Cronos network for a transfer during this period (for instance, A pays B on-chain for goods or services), then with the execution of the rollback, the original payment transaction would be canceled, potentially leading to an extreme situation where the goods have been delivered but the payment disappears.

The bigger controversy lies in the "Finality of Transactions." One important reason why blockchain can be used as a value settlement network is that once a transaction has been sufficiently confirmed, participants believe that this transaction is irreversible— you receive money that truly belongs to you, and the payment I made won't suddenly disappear hours later.

However, Cronos' operation this time undoubtedly weakens its "transaction finality"; as long as something serious happens, even confirmed transactions may not truly be final.

Of course, choosing to roll back in extreme cases is not without precedent; historically, some public chains have coordinated with the community to modify chain states after major security incidents. But the problem is, once this door is opened, it becomes difficult to avoid the question: if $75 million is worth rolling back, what about $50 million? $10 million? Or, besides hacker attacks, what kind of events would be enough to make validators press the "rollback" button again?

This is precisely the biggest controversy surrounding rollbacks. It can indeed solve problems at the moment, but it also makes every on-chain participant realize— the so-called immutability is not an absolute rule for Cronos.

This Is Not Cronos' First Time "Modifying History"

If this rollback can still be explained as "special circumstances, special handling," then looking back a year, Cronos' attitude towards history has actually long been traceable.

In 2021, Crypto.com announced with great fanfare the destruction of 70 billion CRO, significantly reducing the total supply from 100 billion to about 30 billion. This destruction was then referred to as one of the largest token burns in cryptocurrency history.

Then in 2025, Cronos proposed a rather straightforward plan to mint back the 70 billion CRO that had already been burned and allocate it to strategic reserves, restoring the total supply of CRO back to 100 billion. The official reason given at the time was that "to reshape the golden era of Cronos, a large amount of funding is needed to support the Cronos roadmap," including promoting market expansion in the U.S., supporting ecological development, institutional processes, and potential CRO ETFs, etc.

This decision sparked huge controversy at the time. After all, when it was destroyed, it was clearly stated that it was a "permanent destruction," and no one could have imagined that a few years later, they would "mint another batch back." More dramatically, although the community strongly opposed it, the voting was reversed at the end due to concentrated voting by large holders, ultimately allowing the proposal to pass.

· Odaily Note: See "The Most Absurd Governance Farce in CRO's History, 70 Billion Tokens Created Out of Thin Air."

Cronos' "Single-Player Philosophy"

Looking at these two events together, it very much reflects Cronos' own style. 70 billion CRO burned? No problem, mint it back. $75 million stolen? No problem, roll it back.

The former modifies the supply, while the latter modifies the on-chain state. One brings back tokens that have already been "permanently destroyed"; the other makes transactions that have already occurred, and even been confirmed, disappear from history.

Cronos has reasons for every operation— minting back 70 billion CRO is to support the long-term development of the ecosystem; rolling back the chain state is to recover user assets as much as possible. Viewed separately, neither of these actions is entirely incomprehensible.

But the problem is, when similar things happen consecutively, it seems difficult for people to regard "immutability" as a principle of Cronos. The blockchain history in the eyes of others appears more like a draft that can be modified according to actual circumstances at Cronos. Perhaps this is Cronos' "single-player philosophy": rules are certainly important, decentralization is certainly important, but if modifying rules, modifying supply, or even modifying history can solve problems faster, then there's no need to pretend that they can't do it at all.

More starkly, in the face of centralization controversies, Cronos seems to never hesitate and does not hide it.

This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.