The Sui mainnet suffered three separate halts within a 48-hour window this week, each triggered by a bug in the network's v1.72 release. The outages, which temporarily stopped block production, stemmed from a problematic interaction between a new address-balance feature and the blockchain's existing gas and consensus logic, according to a post-mortem published by the Sui Foundation.
What the v1.72 release changed
The upgrade introduced a feature designed to track address balances more efficiently. But when that code ran alongside the gas-pricing mechanism and the consensus engine that finalizes transactions, it created a conflict. The result: the network would get stuck, unable to process new blocks until validators manually intervened. Each time the chain came back online, the same underlying condition re-triggered the halt.
Root cause identified
In the post-mortem, the Sui Foundation's development team traced the failures to a race condition in the way the new balance-tracking logic interacted with the existing gas accounting. The consensus protocol, which expects certain state transitions to happen in a strict order, hit an unexpected state when the balance feature recalculated gas costs mid-block. That inconsistency forced validators to stop producing blocks to prevent a split in the chain.
The foundation said the bug was specific to the v1.72 deployment and that no user funds were lost during any of the three halts. The network has since been restarted and is operating normally.
Impact on users and developers
During each outage, transaction processing on Sui ground to a halt. Decentralized applications built on the chain, including DeFi protocols and NFT marketplaces, were unable to confirm trades or transfers. The repeated interruptions frustrated some developers who had to pause their own services and wait for the chain to stabilize. The foundation did not disclose the total downtime across the three events.
The Sui Foundation has not yet released a timeline for a permanent software patch. The post-mortem outlines the root cause but stops short of specifying a fix or a date for the next upgrade. Validators have been instructed to monitor the network closely and to be ready for further interventions if the condition reappears. For now, the chain is running on the same v1.72 release, raising questions about whether the bug is truly resolved or simply dormant.
