The Sui mainnet has resumed operation, confirming that both outages were caused by the same software defect.

robot
Abstract generation in progress

BlockBeats News, May 29 — According to an official announcement, the Sui mainnet has resumed normal operation, and transaction processing and network activity have both been restored. The two network outages that occurred yesterday and today are related to interaction issues between the "address balance" feature introduced in version 1.72 and the Gas billing logic. The fix deployed yesterday was only a temporary measure aimed at quickly restoring network operation, but it carries a known and low-probability risk of causing a shutdown.

Today, the network triggered a variant of this known issue, causing the mainnet to pause again. Currently, validators have completed the deployment of a long-term fix, and the official statement says the known issue caused by the original vulnerability has been thoroughly resolved, with the network back to normal. The Sui team stated that they will release a more detailed incident review report in the future, explaining the cause of the failure and the repair process.

SUI-4.71%
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
  • Reward
  • 10
  • 1
  • Share
Comment
Add a comment
Add a comment
MemeSourdough
· 05-31 15:15
Waiting for a detailed review; I want to know where the testing coverage missed.
View OriginalReply0
OldKeyboardTraitor
· 05-31 14:38
Are the Sui ecosystem project team members' hearts still okay these days?
View OriginalReply0
MarginMarmot
· 05-31 05:12
Web3 Normalcy: Launch → Bugs → Emergency Patch → Review → Cycle
View OriginalReply0
BudgetDeFi
· 05-30 13:04
I hope this is really the last time; DeFi users can't take much more of this.
View OriginalReply0
0xCaffeine
· 05-29 16:18
Validators respond quickly, but user confidence takes longer to restore.
View OriginalReply0
ParabolicTracker
· 05-29 15:59
Other chains' upgrades have also failed, but failing twice in two days is indeed rare.
View OriginalReply0
NonceNina
· 05-29 15:59
Address balance and Gas interactions, on the edge cases that sound headache-inducing
View OriginalReply0
StainedGlassSun
· 05-29 15:59
Can the architecture complexity be considered excessive if even basic functions like address balances can run into issues during interaction?
View OriginalReply0
HashbrownHero
· 05-29 15:59
Version 1.72 has become a nightmare version; it is recommended to skip directly to 1.73.
View OriginalReply0
Mint-ColoredSlippage
· 05-29 15:59
The hidden traps planted in version 1.72 have finally been triggered; waiting for the review.
View OriginalReply0
View More
  • Pinned