Two outages stemmed from a gas-charging bug that caused validator crashes when failed transactions triggered balance errors. A separate randomness-state bug caused the third halt by preventin
- Two outages stemmed from a gas-charging bug that caused validator crashes when failed transactions triggered balance errors.
- A separate randomness-state bug caused the third halt by preventing validators from properly closing a network epoch.
- Sui said no user funds were affected, implemented fixes, and added safeguards to improve network resilience.
Sui Foundation on Sunday detailed the causes behind three mainnet outages that disrupted network operations across Thursday and Friday, tracing the incidents to two separate bugs introduced in the v1.72 software upgrade. The outages occurred as validators worked to address issues tied to the new address balances feature and a separate randomness-state problem. According to the foundation, no user funds were at risk and no committed transactions were reversed during recovery.
Gas-Charging Bug Triggered First Two Outages
The first outage began around 7 a.m. PT on Thursday and lasted until about 1:30 p.m. PT. However, a second halt followed on Friday morning after validators deployed an interim fix.
According to Sui Foundation, both disruptions originated from a flaw involving gas charging and the newly introduced address balances feature. The issue appeared when transactions competing for the same funds triggered an InsufficientFundsForWithdraw error.
Although the transaction was canceled, subsequent gas-processing steps attempted to spend the same balance again. As a result, validators encountered a negative balance during settlement, causing nodes to crash.
To restore operations quickly, the Sui Core Team proposed an interim fix on Thursday. However, the team acknowledged a known low-probability risk remained within that temporary solution.
Consequently, the network encountered a variation of the same issue on Friday morning, leading to the second outage before validators implemented a more comprehensive fix.
Randomness Bug Caused Third Halt
Following the second recovery, the network operated normally until the next scheduled epoch change on Friday afternoon. At that point, a separate bug triggered the third outage.

According to the foundation, validators restarted to install the Friday fix but failed to meet participation requirements for distributed key generation. As designed, the process disabled randomness for the epoch.
However, a latent bug prevented validators from preserving that status across restarts. Consequently, randomness-dependent transactions remained unresolved, causing a queue buildup that prevented the epoch from closing.
The outage lasted from approximately 1:30 p.m. PT until 7:20 p.m. PT on Friday.
Foundation Outlines Fixes And Lessons
Following the incidents, validators fixed both the gas-charging and randomness-state bugs. Additionally, the foundation introduced a mechanism allowing validators to force-close a stalled epoch when necessary.
The report also highlighted areas for improvement, including gas-charging logic, end-of-epoch resilience, and failure containment. Furthermore, Sui Foundation said AI agents helped engineers diagnose the incidents faster by analyzing validator logs, production data, and network metrics during the outages.
The post Sui Explains Three Mainnet Halts After v1.72 Upgrade appears on Crypto Front News. Visit our website to read more interesting articles about cryptocurrency, blockchain technology, and digital assets.