Cronos Restarts Its Chain With the Tectonic Exploit Rolled Back

Cronos is producing blocks again. Validators restored the chain state to a point before the Tectonic exploit and restarted the network from block 90,896,189. Crypto.com, which built the chain and issues CRO, said user funds are safe. The halt ran more than ten hours, and the restart timestamps in circulation fall on two different days. What the rollback did to the money left in the attacker's addresses has not been published anywhere.

What the validators did

This was an emergency action, not a governance vote. Cronos runs Tendermint consensus with a cap of 100 validators, a set small enough to agree on stopping and small enough to agree on starting again. Node operators were told to move to Cronos v1.7.8 with the latest mainnet snapshot, a detail Coinpedia carries alone.

"The Cronos Network halted earlier today. This was a validator-consensus emergency action to protect users from an exploit on the Tectonic protocol. The chain state was restored to before the Tectonic exploit," Cronos said in the post announcing the resumption.

Two days, one clock time

The restart timestamp does not settle. The Crypto Times and TronWeekly both put it at 23:49 UTC on 30 August. Bloomingbit gives 08:49:01 Korean time on 31 August, which is the same instant written from another desk. Coinpedia prints the same clock time a full day later, 23:49 UTC on 31 August. Three accounts point at Sunday night and one at Monday night, and we could not establish which is right. On the Sunday reading, this desk's own Monday-morning piece on the halt was already out of date when it reported that no resumption had been announced.

The block heights do not line up either

Every account naming a restart height gives 90,896,189. The Defiant, alone among the outlets located, put the last block before the halt at 90,907,150 and said the chain went 10 hours and 36 minutes without producing one. Those two heights sit about 11,000 blocks apart. No account explains the gap, and neither figure has been confirmed against the other.

Four numbers for one loss

The size of the theft is still written four ways. PeckShield flagged three addresses holding about $74 million. Weilin Li, the on-chain researcher whose estimate most outlets carried first, started at about $66 million and revised to roughly $75 million after finding a further attacker wallet. The Defiant counted $68.7 million frozen on Cronos and cited a third researcher, Hajedan, tracing $110.5 million still on the chain. About $6.29 million had already crossed to Ethereum as 2,592 ETH before the halt, and that is the closest thing here to an agreed figure. The rest are measurements of different things, and no outlet reconciles them.

What a reversible chain costs

Tectonic held $121.7 million in deposits before the attack, and CoinDesk put the protocol near $3 million by Monday. CRO is quoted three ways over three windows: down 9.3% across 24 hours in The Defiant's reading, down 4.89% at $0.05636 on the day by Coinspeaker, and $0.05675 in AMBCrypto's, after a peak near $0.064 during the episode. This desk reported a gain of 3% to 5% on the day of the halt itself. The windows do not overlap, so none of these supersedes another. Two other chains hit the kill switch in a single day last month. Stopping a chain has become a familiar move. Unwinding one draws objections, and The Crypto Times reported users arguing that a network able to reverse itself under emergency consensus could be pressed to do it in circumstances less clear-cut than a theft. That objection sits in that account alone.

Nothing about the money is settled

No compensation plan has been announced. No final accounting of the loss has been published, and the technical postmortem Cronos promised had not appeared at the time of writing. Tectonic's instruction to users not to interact with the protocol still stands in every account located. The narrow question a postmortem would have to answer is whether the rollback touched the attacker's balances or left them where they were. Cronos has not said.