According to the Sui Network’s official status page, the blockchain is facing a “major outage” as it has stopped processing user transactions. The Sui team explained that the last stall is related to the solution of the first stall, and a problem that became more and more serious as the era changed.
Key Takeaways:
- Sui quit for the third time in two days, disrupting the market while the core team then worked on a long-term solution.
- The cause appears to be the new stablecoin’s 0-fee transaction logic, which had design flaws.
- Sui stopped again at 4:30 PM EDT and froze user transactions while it investigates era change issues.
Sui falls for the third time
Sui, a powerful blockchain, has experienced problems with its network activity for the third time in two days.
The official Sui status page indicated that the network stopped processing transactions at 7:58 a.m. EDT, completely affecting the operation of the network.
The Sui team acknowledged this issue on social media, stating that their mainnet was experiencing a “network outage” and that it was looking for a solution. “Please note that transactions may be paused at this time. Updates will be shared as they become available,” they posted.
At 11:34 a.m. EDT, the network was processing transactions again, with Sui’s team explaining that both today’s and yesterday’s issues were related to the changes to the “gas charging logic” that the blockchain recently applied to make stablecoin transactions free.
“Yesterday’s implemented fix was an interim measure designed to restore functionality to the network while the Sui Core team worked on a long-term solution. The interim fix had a known issue that was unlikely to cause a shutdown. This morning the network hit a variation of the known issue and shut down,” Sui explained, emphasizing that network activity had resumed.
X user 0xarthur.sui claimed that while the first network outage was likely due to a design flaw, this second one was perpetrated by a threat actor. “A hacker probably opened short positions in advance just to crash Sui,” he stated.
Moreover, he believes that the solution to the problems with AI has been coded and applied. “For such a large project, they should not be completely dependent on AI. They should use multiple AI models for batch detection and then do a final manual validation before submitting,” he advised.
Nevertheless, at approximately 4:30 PM EDT, Sui encountered yet another problem that prevented transactions from being processed. Sui linked it to an issue during the era change, when validators created system transactions but ignored user transactions. “The Sui Core Team is investigating and updates will be shared as they become available,” it concluded.