rewrite this content and keep HTML tags as is. This is content from rss feed and I don’t need their *Daily Debrief Newsletter*, their tags from bottom like this *Share this articleCategoriesTags*, Editorial Process section, phrases like *Featured image from Peakpx, chart from Tradingview.com*, SPECIAL OFFERS and similar sections – just remove such sections and save only article itself:
Key Takeaways
- Sui mainnet stalled for exactly 5 hours and 55 minutes on May 29, resulting from a bug in the Sui 1.72 release, which halted onchain block production.
- Following a 6.6% drop in price post-incident, developers deployed network patches to help resume services as usual.
- Sui’s dev team has noted that a full incident review will be shared in the coming days.
Onchain Data Shows Block Production Halt for Sui Mainnet
The Sui blockchain experienced a severe network stall, halting all block production for exactly five hours and 55 minutes. According to onchain data from Suiscan, the mainnet stopped processing new checkpoints, effectively freezing all decentralized finance ( DeFi) activity. The Sui core team confirmed the issue on X, stating that a crash bug in the gas charging logic introduced during the 1.72 release caused the disruption.
The network first alerted users that it was experiencing a stall, warning that transactions would be delayed while developers worked on a fix. During the outage, the network’s native token SUI dropped approximately 6.6%, reaching a low of $0.90 per unit before partially recovering once services resumed.
The incident marked the second major downtime event for Sui in 2026, following a similar January network stall that kept validators offline for over six hours.
The Technical Reasoning Behind the Breakdown
The gas charging logic is a critical component governing transaction fee calculations, and a failure at this layer resulted in a complete network freeze rather than degraded performance. At a high level, the incident was caused by an edge-case bug in the consensus commit logic related to handling conflicting transactions, causing different validators to reach different conclusions when computing consensus commits.
The Sui core stack utilizes multiple layers of transaction processing, where consensus produces an ordered stream of commits and deterministic execution turns those commits into checkpoints. Because validators observed that more than one-third of the stake was signing a different digest, certification became impossible.
Consequently, validators on the Sui mainnet were forced to manually identify the divergence, implement a fix to purge incorrect consensus data, and enable corrected logic. Even after regular operations resumed, some nodes were still reported to be operating with degraded performance.
While the interruption was unintended, the network’s default safety-focused architecture behaved as designed by preventing a user-visible fork. At the time of the outage, Sui ranked among the top blockchain platforms by total value locked (TVL), securing approximately $536 million across 137 protocols.
