rollback

Cronos confirmed in a post-mortem report that the attack on the lending platform Tectonic on August 30 involved $120.4 million in borrowing activities. The validators made the "difficult decision" to roll back the on-chain history, successfully recovering approximately $111.2 million (about 92% of the affected funds), while about $9.19 million flowed out before the network was paused and could not be recovered. The attacker leveraged weak DEX liquidity to inflate the price of Tectonic token TONIC by about 100 times within minutes and borrowed $120.4 million through a single transaction across nine markets. The validators paused the network about two hours later, restoring the chain to the last block before the suspicious activity, with block production resuming approximately 11 hours after the attack. The rollback involved reversing 1 hour and 54 minutes of on-chain history, totaling 10,961 blocks, with all transactions within that window being canceled, regardless of whether they were involved in the attack. Cronos stated that the alternative would have been to restart the network without restoring the previous state, which would have left the stolen assets in the hands of the attacker. This rollback closely followed Harmony's announcement of a similar plan, while Flow abandoned its rollback proposal last December due to community opposition. The validator cap for Cronos is 100, which facilitated quick coordination for the pause and restart, but also indicated that the network's finality in emergencies depends on validator consensus.

Harmony has released a rollback plan, intending to retain shard 0 block 92,730,034 and shard 1 block 94,978,278, both corresponding to the time of August 11, 2026, 23:25:37 UTC.Validators will use a replacement database, and the new client version will reject the relevant abnormal block hashes, subsequently continuing to produce blocks from the new block height.

According to Harmony monitoring, Harmony stated that it is advancing the rollback plan and has reached an agreement with validators and exchanges on the specific path. The minting vulnerability fix has been activated, and a complete list of attacker wallets will be announced soon.Previously, the number of ONE tokens abnormally minted on the Harmony network had exceeded 30 trillion, involving 6 abnormal blocks.

Harmony stated that it is collaborating with internal teams and relevant exchanges to attempt to stop and freeze the flow of related funds. A patch and rollback plan are also being developed. Further information will be updated in a timely manner.

Paradex announced on its maintenance page that it has identified the issue and will roll back the chain state to block 1604710 (UTC time 04:27:54). This is the state prior to the database maintenance and is the last known correct state. All accounts will be restored to the state before the database maintenance.According to previous news from ChainCatcher, Starknet ecosystem Perp DEX Paradex announced a temporary maintenance, and although the expected maintenance completion time has passed, the protocol is still not online. According to community feedback, some users experienced forced liquidation of their perpetual contract trades on Paradex due to abnormally high funding rates.

The Ethereum L2 network Starknet released an analysis report on the short-term mainnet outage that occurred this Monday, stating that the cause of the incident was the inconsistency between the execution layer (blockifier) and the proof layer: under specific cross-function calls and rollback combinations, the execution layer incorrectly recorded a state write that had been rolled back, leading to abnormal transaction execution. The related transactions did not receive L1 finality confirmation. This incident triggered a block reorganization, with approximately 18 minutes of on-chain activity being rolled back.This is the second major interruption since 2025, following a September incident where a sequencer vulnerability caused an outage of over 5 hours and rolled back about 1 hour of on-chain activity.

Flow officials provided an update on the attack incident on the X platform, stating that they will abandon the network rollback and shift to an "isolation recovery plan." Key points of the new plan include:No rollback/restructuring, retaining all legitimate user activities;No need for partners to replay transactions;Over 99.9% of accounts are unaffected, and normal operations will resume upon restart;During the restart, temporary restrictions will be placed on accounts receiving illegally minted tokens;Additionally, the network will be restored in phases:Phase 1: Cadence environment goes live, EVM temporarily restricted;Phase 2: Cadence fixes (approximately 24-48 hours);Phase 3: EVM fixes and restart;Phase 4: Cross-chain bridges/exchanges resume operations, with specific recovery times determined by operators based on actual conditions after confirming stability.

deBridge co-founder Alex Smirnov posted on the X platform, stating that he has noticed the news regarding Flow's decision to roll back the blockchain state and expressed concerns about the execution of that decision.Alex pointed out that although Flow officials claim to be in a synchronization window with key ecosystem partners such as bridges, CEXs, and DEXs, deBridge, as one of the main cross-chain bridges for Flow, has not received any communication or coordination from the Flow team. Alex stated that the economic losses that may result from a hasty rollback of the chain state could far exceed the initial security incident itself and could trigger systemic issues, affecting cross-chain bridges, custodians, users, and counterparties that were operating normally during the relevant time window.He specifically mentioned potential issues during the cross-chain process, such as balance doubling and assets being unrecoverable, and pointed out that several large cross-chain and custodial transactions have already been completed during the rollback window, including USDC-related transactions managed by LayerZero. Alex further compared that in past similar incidents, such as with BNB Chain, the approach taken was more about isolating the attacker rather than rolling back the global state.He urged Flow validators to pause the validation of the rollback chain until a clear remedy plan is established, ecosystem coordination is completed, and security organizations are involved, to avoid irreversible consequences. He emphasized that the current situation requires more transparency, collaboration, and restraint, rather than rapid execution of aggressive actions.

ChainCatcher news, Unichain announced that it has implemented a block construction mechanism based on TEE (Trusted Execution Environment), becoming the first L2 network to adopt this approach. This design enables transaction priority ordering, MEV protection, and transaction rollback protection, and supports future verifiable block features.Unichain stated that the traditional Rollup sorting mechanism is usually an offline operation, making it difficult to audit, while its TEE sorting system can publicly prove the transaction order, reducing MEV value loss. In addition, the rollback protection mechanism will prevent users from losing Gas in failed transactions, enhancing price accuracy and block space utilization efficiency. The aforementioned features are supported by Rollup-Boost, developed in collaboration with Uniswap Labs and Flashbots.

ChainCatcher news, Bitget's Chinese head, Xie Jiayin, stated on Twitter, "The technical team is working hard to follow up on the affected accounts. Some accounts have gradually completed transaction rollbacks and restored trading, deposit, and withdrawal functions. If users face liquidation due to account restrictions today, we will take full responsibility. Users who actively participated in trading and incurred losses on the VOXELUSDT contract positions between 16:00 and 16:30 on April 20 will receive appropriate compensation."