Sui marked its mainnet incident resolved after three halts

Sui’s official status tracker marked a two-day mainnet-settlement incident resolved on May 30, 2026 after reporting that validator participation had recovered to 93% by stake. The resolution followed three separate halts that interrupted transaction settlement as validators coordinated emergency software changes.

The May 30 status update established that the network had recovered sufficiently for the operator to close the incident. It did not establish that every validator was online, that every affected application had returned to normal or that the underlying software defects had received a complete public review. Those distinctions mattered for a layer-one network whose applications depended on validators reaching agreement and advancing checkpoints.

Recovery remained gradual

Earlier on May 30, the status tracker reported that Sui had progressed into epoch 1143 and was online with degraded participation. The final update later that date said participation had reached 93% by stake and that the network would continue to be monitored.

The surviving status-page mirror displays those updates at 02:32 and 16:43 on May 30 but does not identify the viewer timezone in its extracted record. The exact hours should therefore be treated as displayed timestamps rather than converted into an unsupported universal timeline. The calendar date of the resolution is clear.

The incident had begun on May 28 and affected both Sui mainnet validators and public remote-procedure-call nodes. Status updates across May 28 and May 29 showed validators repeatedly adopting fixes representing more than two-thirds of stake, bringing the network online and then monitoring it for renewed problems. Later on May 29, validators were reported to be waiting for an epoch change while processing only system transactions.

That sequence demonstrated why an initial restart was not equivalent to a durable recovery. A sufficient validator supermajority could resume progress after adopting a patch, but subsequent execution paths or epoch-transition logic could still expose another defect.

What was knowable on May 30

The contemporaneous public record supported three conclusions: mainnet settlement had suffered a major incident; validators deployed coordinated fixes over multiple recovery attempts; and Sui marked the incident resolved on May 30 after stake participation improved.

A repository record merged on May 29 supplied technical evidence for one emergency correction. The change removed address-balance entries from a gas payment after an `InsufficientFundsForWithdraw` abort, preventing an already depleted balance from underflowing during settlement. The pull request described the change as originating in an out-of-band fix for Sui’s 1.72 release branch.

That code record did not, by itself, prove the complete cause of every halt. It supported the narrower conclusion that gas processing involving the recently introduced address-balance feature had produced a settlement failure serious enough to require an emergency patch.

No verified event-day token-price, application-loss or transaction-backlog measurement is included here. SUI traded continuously across multiple venues, and neither the official incident record nor the contemporaneous repository entry supplied a defined exchange, benchmark or measurement window from which a defensible market reaction could be calculated.

Why the incident mattered

A blockchain can preserve committed history while still failing as live financial infrastructure when it stops advancing. During a halt, users may retain ownership of recorded assets, but transfers, liquidations, application updates and other time-sensitive operations can be delayed. Recovery therefore depends not only on protecting past state but also on restoring predictable forward progress.

Sui’s repeated recovery attempts also illustrated the coordination embedded in proof-of-stake operations. Software fixes required adoption by enough validator stake to restore network participation, making operational resilience a combined problem of code correctness, deployment and validator coordination.

Later context

On May 31, Sui Foundation published a fuller incident review. It said the first two halts arose from gas-charging bugs involving release 1.72 and address balances. A third halt exposed a separate latent defect in preserving distributed-key-generation status across validator restarts during an epoch change. The foundation said no user funds were at risk and no committed transactions were reverted.

Those findings clarify the May 30 resolution but were not yet part of the complete public record when the incident was closed. They should be read as later technical context, not as information available throughout the event day.