Sui mainnet activity has resumed after a second network halt tied to the 1.72 release, which introduced Address Balances and interacted unexpectedly with gas charging logic.
Transactions are now flowing normally after validators implemented a longer-term fix. The update follows two back-to-back disruptions that paused activity and placed renewed pressure on Sui’s reliability record.
The latest halt was connected to the same original bug behind the previous incident. Sui’s first fix was an interim measure designed to restore network functionality while the Core team continued working on a permanent solution. That interim patch carried a known low-probability risk of causing another halt. The network hit a variant of that issue this morning, forcing another pause before validators rolled out the stronger fix.
What Caused The Second Halt
The problem came from the interaction between Sui’s 1.72 release, Address Balances, and gas charging logic. Address Balances were introduced as part of Sui’s push toward more flexible balance handling, including new user-facing features such as gasless stablecoin transfers.
Gas charging sits deep inside transaction execution. When that logic breaks or creates inconsistent behavior across validators, the network can stop advancing rather than risk finalizing an unsafe or inconsistent state. That makes the incident a liveness problem first: users may face paused transactions, failed submissions, delayed app activity, and temporary settlement disruption even if the chain preserves safety.
The Sui team said the longer-term fix now fully addresses the known issues caused by the original bug. A more detailed incident review is still pending.
Two Halts Put Reliability Back In Focus
The update follows Sui’s earlier mainnet stall, which temporarily halted block production and forced validators to coordinate a fix. Having a second halt so soon after the first turns the story from a single operational disruption into a broader test of release safety, validator rollout speed, and incident response.
Sui has been trying to grow beyond a high-throughput Layer-1 narrative. The network has pushed into payments, DeFi, stablecoins, gaming, and institutional products, including CME SUI futures. Those use cases depend on the same baseline requirement: transactions need to keep moving when users and apps are active.
A chain can recover from downtime, but repeated halts create harder questions for developers and traders. DeFi apps need reliable execution for swaps, collateral movements, liquidations, oracle updates, and withdrawals. Wallet users need confidence that transfers will not pause during time-sensitive activity. Market makers and exchanges need predictable settlement across deposits and withdrawals.
Validators Roll Out Long-Term Fix
Sui’s live status update marked the network online after more than two-thirds of stake upgraded to the latest fix. That threshold matters because validator stake weight determines whether the network can resume normal consensus and settlement.
The remaining questions now move to the incident review. Users and developers will be looking for a clear timeline, the exact failure path, why the interim fix carried halt risk, how the final patch removes that risk, and whether additional release-testing changes are planned before similar balance or gas logic updates reach mainnet.
Sui’s recovery gives the network breathing room, but the technical review will decide how the incident is judged. The confirmed facts are already sharp enough: the 1.72 release introduced a gas-related bug, the interim patch restored activity but carried a known halt risk, a second halt hit that risk path, and validators have now deployed the longer-term fix that brought transactions back online.
Be the first to comment