Sui mainnet experienced an approximately 6-hour outage on January 14. According to the event review released by the Sui Foundation, the root cause of this failure was an internal disagreement among validators during consensus processing, which led to new checkpoints being unable to be properly certified, and subsequently, transaction submissions also experienced timeouts.
It is worth noting that this was not caused by network congestion or a surge in transaction volume leading to a shutdown, but rather a consensus mechanism issue at the validator level. The foundation also explicitly stated that user funds and account statuses remained completely secure, and there were no instances of certification state forks or transaction rollbacks during this period. This means that although the network was temporarily unable to process new transactions, historical data and user assets were not at any risk.
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.
14 Likes
Reward
14
6
Repost
Share
Comment
0/400
ImpermanentSage
· 21h ago
Validators fighting causing network shutdown, this move is really incredible
When the consensus mechanism has issues, it strikes for 6 hours. Why not fix it earlier?
As long as the funds are safe, it's okay, but this experience really makes people frustrated
Sui needs to quickly optimize validator coordination, can't keep going like this
By the way, will this incident affect future fundraising?
Is this the cost of decentralization?
I really can't understand such low-level errors like validator disagreements
The network was down the entire afternoon, all transactions were stuck. What to do if the market moves suddenly?
Fortunately, there was no fork, or else it would have been disastrous
The problems exposed this time are more serious than expected
View OriginalReply0
GasBankrupter
· 01-17 06:36
Validator internal conflicts, we have to shut down, this logic is really absolute
---
6 hours huh, it's again the validator's fault, when will they stop messing around
---
As long as the assets are safe, anyway, interruption is much better than losing tokens
---
If this happened on other public chains, the community would have exploded long ago. Is Sui just for fun?
---
Validator consensus disagreements are probably an architecture issue, why does this show keep happening
---
Fortunately, there was no rollback, or else those holding positions would be crying
---
I just want to know if those who shorted during this period made a lot of money
View OriginalReply0
GmGnSleeper
· 01-16 02:43
Validators fighting is a thing, but at least the funds are safe, which is better than anything else.
---
6 hours? I thought it was another big event, but it turns out there was just a consensus issue.
---
Basically, it's still a misalignment on the validator side. As long as asset security is maintained, everything else is acceptable.
---
Is it not congestion but the collapse of the consensus layer? Such failures are actually more heartbreaking.
---
Sui is down again, when will it stabilize, brothers?
---
The security of user assets is very critical. No forks mean the main network is stable, which is a good sign.
---
It was caused by internal disagreements among validators, feeling like family members arguing and shutting the door.
View OriginalReply0
GamefiGreenie
· 01-16 02:43
Validators passing the buck to each other, so we have to shut down. That logic is really something.
The consensus mechanism throwing a tantrum is indeed a bit hard to handle, but at least the funds are safe.
6 hours again, another thrilling "exercise."
Validators fighting among themselves, and we’re the ones paying the price. I’m really familiar with this combo.
Mindset may collapse, but at least I didn’t lose money, so I’ll keep buying the dip.
Another incident, when will Sui finally settle down?
Consensus issues are more troublesome than network congestion, feels like not the main point.
Fund safety is the last stubbornness.
Checkpoint authentication sounds really ridiculous.
This is a common problem with big projects, causing trouble every now and then.
View OriginalReply0
Tokenomics911
· 01-16 02:37
Validators fighting causing network downtime, I didn't see this plot coming haha
6 hours, luckily assets are fine, otherwise the mentality would really explode
Sui's architecture design is still a bit fragile, is the consensus layer so prone to issues?
So basically, it's just that the validator nodes are not aligned, and the checkpoint got stuck
Fortunately, there was no rollback, otherwise that would have been a real disaster
Will there be an enhancement to the synchronization mechanism among validators after this incident?
Network interruption ≠ funds are at risk, the foundation explained this clearly
Validators fighting caused a bug, will we learn a lesson next time?
Consensus issues sound more unsettling than congestion issues, that's my intuition
The 6-hour "service suspension" is still a bit damaging to on-chain activities
View OriginalReply0
TestnetFreeloader
· 01-16 02:27
Validators are fighting, and we're affected... but at least the funds are safe. Let's just consider it a maintenance pause.
Validator consensus issues? That’s quite a mess. Luckily, there was no rollback.
Six hours of downtime sounds easy to say, but all my pending orders were left waiting in vain.
As long as the assets are intact, that's fine... but I feel a bit uneasy.
Consensus disagreement? It seems Sui still needs to optimize its mechanism.
Fortunately, there was no trade rollback, or it would have caused a real uproar.
Validators are "playing mahjong," so let's just wait and see.
Sui mainnet experienced an approximately 6-hour outage on January 14. According to the event review released by the Sui Foundation, the root cause of this failure was an internal disagreement among validators during consensus processing, which led to new checkpoints being unable to be properly certified, and subsequently, transaction submissions also experienced timeouts.
It is worth noting that this was not caused by network congestion or a surge in transaction volume leading to a shutdown, but rather a consensus mechanism issue at the validator level. The foundation also explicitly stated that user funds and account statuses remained completely secure, and there were no instances of certification state forks or transaction rollbacks during this period. This means that although the network was temporarily unable to process new transactions, historical data and user assets were not at any risk.