TLDR
- Sui Foundation linked three mainnet halts to two bugs introduced during the v1.72 upgrade release.
- The first two outages came from a gas-charging flaw exposed by address balances functionality.
- A rushed temporary fix restored service but carried a known low-probability network halt risk.
- The third halt started after validators restarted and triggered a bug in randomness settings.
- Sui said user funds remained safe, and no settled transactions were reversed after recovery.
Sui Foundation said three mainnet halts came from two bugs linked to its v1.72 upgrade. The outages happened on Thursday and Friday, and the foundation published its review on Sunday. It said user funds were safe, and no settled transactions were reversed.
v1.72 Upgrade Triggered the First Two Sui Mainnet Halts
Sui Foundation said the first two halts came from one gas-charging bug. The issue appeared after the v1.72 software release. That upgrade added an “address balances” feature for easier account use.
The first halt began around 10 a.m. ET on Thursday. The network returned at about 4:30 p.m. ET. A second outage followed early Friday and ended later that morning.
The bug involved how Sui charged some transactions for gas. A transaction could fail because of low funds. Yet the network could still spend those funds after cancellation.
That process created a negative balance in some cases. Validators then failed during account checks. As a result, the Sui mainnet stopped processing activity.
Temporary Fix Carried a Known Halt Risk
Sui Foundation said the team released a temporary fix on Thursday. The foundation said that fix had a “known issue with a low probability of causing a halt.” It accepted that risk to restore the network faster.
The network later reached a related version of that problem. That event caused the second halt on Friday morning. Sui said teams were already working on a stronger fix.
The foundation said validators have now addressed the gas-charging issue. It also said no user funds were at risk during the outages. No settled transactions were rolled back after the restart.
Sui also said it built a tool to force-close a stalled epoch. The team used that mechanism once during recovery. That step helped the network move forward after the halt.
Randomness Bug Caused the Third Network Freeze
Sui Foundation said the third halt had a different cause. It happened after validators restarted to install Friday’s fix. The restart exposed a hidden bug in randomness settings.
Sui uses a setup process for randomness at each epoch start. Some apps rely on that random number system. During the restart, too few validators were ready for the setup.
The system switched randomness off as designed. However, validators failed to record that choice. Because of that bug, they could not close the epoch.
The third halt began around 4:30 p.m. ET Friday. The network resumed around 10:20 p.m. ET. Sui said validators have now fixed both known bugs.
Sui Foundation wrote, “As of now, validators have fully addressed the known issues caused by both the original gas-charging bug and the randomness-state bug, and network activity has resumed.”
The foundation also said AI agents helped the team review logs and metrics. These tools helped engineers study validator data during the incidents. Sui said future work will focus on limiting failures before they halt the full network.
Get 3 Free Stock Ebooks
Discover top-performing stocks in AI, Crypto, and Technology with expert analysis.
- Top 10 AI Stocks - Leading AI companies
- Top 10 Crypto Stocks - Blockchain leaders
- Top 10 Tech Stocks - Tech giants
