Sui Foundation disclosed on Sunday that the three outages of the Sui mainnet on Thursday and Friday were caused by two different bugs introduced by the v1.72 upgrade.


The first two outages were due to a gas fee vulnerability exposed by the "address balances" feature; the temporary fix deployed by the team on Thursday contained a "known issue that could, with low probability, cause a shutdown," but the risk was accepted for quick service restoration, and the outage was triggered again on Friday.
The third outage was triggered when validators rebooted and reinstalled the fix, involving a potential bug related to the network's preservation of randomness settings.
Sui stated that the related bugs have been fixed, user funds are not at risk, settled transactions have not been rolled back, and a mechanism has been built to forcibly close stalled epochs. (The Block)
SUI-2.08%
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
  • 12
  • 1
  • Share
Comment
Add a comment
Add a comment
GateUser-23bf1070
· 12h ago
v1.72 Chain of failures, temporarily deploying with known risks, classic technical debt
View OriginalReply0
StakingSparrow
· 23h ago
Validator restarts can trigger downtime; this randomness setting’s save logic is so fragile.
View OriginalReply0
TheProphetOfToast
· 23h ago
Bugs related to randomness are really high risk on the consensus chain; this module needs to be audited multiple times.
View OriginalReply0
PaperHandsPro
· 23h ago
All three times involved different bugs, indicating that root cause analysis was not thoroughly done before rushing to deploy.
View OriginalReply0
MintLaterMaybe
· 23h ago
Not rolling back settled transactions is indeed the correct approach, preserving the finality guarantee.
View OriginalReply0
L2Mailman
· 23h ago
Thursday maintenance, Friday crash, Friday maintenance, Sunday announcement, I’m familiar with this rhythm.
View OriginalReply0
LatencyLullaby
· 23h ago
Let's see if we can fill in the testing process later; otherwise, institutional funds won't dare to come in.
View OriginalReply0
MosaicButterfly
· 23h ago
A low-probability risk was accepted, but the result turned out to be a high-probability slap in the face—keep the decision document so you can do a retrospective and revisit the calls.
View OriginalReply0
Paper-CutOctopusMarketAnalysis
· 23h ago
Sui's shutdown density, the new chain's aura is almost worn out.
View OriginalReply0
RetroRadioEcho
· 23h ago
The foundation will issue an announcement on Sunday, and will work overtime over the weekend to write the postmortem. Thank you for your hard work.
View OriginalReply0
View More
  • Pinned