The Sui Foundation’s post-mortem published Sunday traces all three outages to interactions between a new address-balance feature shipped in the v1.72 release and the network’s existing gas and consensus logic.
Updated Jun 1, 2026, 6:02 a.m. Published Jun 1, 2026, 5:38 a.m. 3 min read
A new feature shipped in Sui’s v1.72 release exposed an edge case in the Layer-1 blockchain’s gas-charging logic that halted mainnet three separate times across May 28 and May 29, with each fix either triggering or exposing the next failure, the Sui Foundation said in a post-mortem published Sunday.
The first outage began at roughly 7 a.m. PT on Thursday and lasted close to seven hours.
According to the foundation, it stemmed from a rare issue in how the network charged gas for transactions paying with a mix of the new address-balance feature and traditional coin objects. The bug caused validators to crash with an underflow error when a transaction was canceled for insufficient funds, but the gas-smashing routine still tried to spend those same funds.
Think of a coin object as a digital banknote. A user’s SUI balance isn’t a single number — it’s a stack of distinct “notes,” each with its own ID, that can be moved or combined. The wallet might hold three coin objects worth 60, 30, and 10 SUI rather than a single 100-SUI balance. To pay for something, the network combines the notes it needs.
Validators are computers (and the operators behind them) that run the network by processing transactions, voting on which ones are valid, and keeping the chain alive.
The core team brought the network back up around 1:30 p.m. PT with what it called an “interim fix” that addressed the most common version of the bug but carried “a known issue with a low probability of causing a halt.” The team accepted that risk to restore the mainnet quickly while a more robust fix was developed.
The known risk materialized the next morning. A second outage began around 5 a.m. PT on Friday, when a transaction triggered a masked variant of the same bug, in which the insufficient-funds error was overridden by another cancellation reason, bypassing the interim patch. The core team finished a more robust fix, and validators adopted it by about 9:40 a.m. PT.
The third halt was a knock-on from the second. When validators restarted to install the robust fix, validator participation in the protocol that bootstraps the network’s on-chain randomness fell below the required threshold, and randomness disabled itself as designed.
(On-chain randomness is a protocol the network uses to produce a number nobody can predict or fake, even though every validator has to agree on the same value. Apps that depend on chance — lotteries, certain games, random NFT mints — can’t run without it.)
A latent bug then failed to persist that disabled state to disk, leaving validators unaware on the next restart that randomness had been turned off. The next epoch change stalled for close to six hours as randomness-dependent transactions piled up in a paused queue.
No user funds were at risk during any of the outages, and no committed transactions were reverted, the foundation said.
SUI dropped roughly 8% during the cascade to a low of $0.90 and was trading near $0.90 on Monday, leaving the token down about 19% on the week, per CoinDesk data.
The events represent Sui’s third major reliability incident since its 2023 mainnet launch, following a two-hour transaction scheduling bug in November 2024 and a six-hour consensus divergence in January 2026.
More For You
0xflorent, a security researcher, found an integer-overflow flaw in the HongCoin token sale contract that lets the team unlock funds for 48 original investors. It is the second such recovery he has publicized in eight days.
What to know:
- A security researcher known as 0xflorent helped the team behind a failed 2016 HongCoin ICO unlock about 1,003.62 ETH, or roughly $2 million, that had been trapped in its smart contract for nine years.
- By coordinating with HongCoin’s multisig wallet holders, he used an unpatched integer-overflow flaw in an admin…
