Sui Developers Trace Three Network Halts to Upgrade Errors After Turbulent 48 Hours

Key Highlights

• The Sui blockchain suffered three separate mainnet halts within 48 hours following its v1.72 upgrade
• Developers traced the disruptions to two distinct software bugs introduced during the update process
• The first two outages were linked to a flaw involving gas accounting and a new balance-tracking feature
• A third halt was caused by an issue affecting validator randomness-state during network recovery
• Emergency patches were deployed to restore block production after each incident
• The Sui Foundation confirmed that no user funds were lost and no finalized transactions were reversed
• The events have intensified discussions around blockchain upgrade testing and network resilience

The Sui Foundation has released details surrounding a series of network disruptions that caused the blockchain’s mainnet to halt three times within a 48-hour period. According to developers, all three incidents were ultimately linked to bugs introduced during the rollout of the network’s v1.72 software upgrade.

The first outage occurred after a flaw emerged in newly implemented gas-charging logic tied to an address-balance feature introduced as part of the upgrade. Under specific conditions, the issue caused validator nodes to crash, preventing the network from processing transactions and producing new blocks.

Developers quickly issued an emergency patch to restore functionality, but the workaround itself carried a known low-probability failure risk. That risk materialized shortly afterward, contributing to a second network halt when similar conditions reappeared. The result was another temporary interruption to block production as validators coordinated a recovery effort.

A third outage followed during the recovery process, although developers later determined it stemmed from a separate bug. This issue involved how validator nodes handled randomness-state data during restarts and epoch transitions, creating another unexpected failure scenario that briefly stopped the network once again.

Despite the repeated disruptions, the Sui Foundation emphasized that user funds remained secure throughout the incidents. The organization stated that no assets were lost, no wallets were compromised, and no finalized transactions were rolled back as a result of the outages.

The incidents have nevertheless drawn attention because Sui is positioned as a high-performance Layer 1 blockchain designed to support large-scale decentralized applications. Network reliability is considered a critical component of that value proposition, making multiple halts in such a short period a notable event for developers, investors, and ecosystem participants.

The foundation has since implemented fixes addressing both identified bugs and says additional safeguards will be introduced to strengthen future upgrade procedures. Developers also indicated that lessons learned from the incident will be incorporated into testing and deployment processes to reduce the likelihood of similar disruptions occurring again.

For the broader blockchain industry, the episode serves as a reminder that even advanced networks can encounter unexpected challenges when deploying major protocol upgrades. As blockchain ecosystems become increasingly complex, balancing innovation with operational stability remains one of the sector’s most important engineering challenges.