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 latest stall is related to the fix of the first stall, and a problem that surged at the epoch change.
Key Takeaways:
- Sui halted for a 3rd time in 2 days, disrupting the market as the Core Team next works on a long-term fix.
- The cause seems to be the new stablecoin’s 0-fee transaction logic, which had design defects.
- Sui halted again at 4:30 PM EDT, freezing user transactions as it investigates issues regarding epoch change.
Sui Falls For The Third Time
Sui, a high-performance blockchain, has experienced issues 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 AM EDT, affecting network operability completely.
The Sui team acknowledged this issue on social media, stating that their mainnet was experiencing a “network stall” and that it was looking for a solution. “Be aware that transactions may be paused at this time. Updates will be shared as soon as they are available,” they posted.
At 11:34 AM EDT, the network was processing transactions again, with Sui’s team explaining that both today’s and yesterday’s problems were linked to the “ gas charging logic” changes 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 with a low probability of causing a halt. This morning, the network hit a variant of the known issue and halted,” Sui explained, stressing that network activity had resumed.
X user 0xarthur.sui alleged that while the first network stall was likely due to a design defect, this second one was perpetrated by a threat actor. “A hacker likely opened short positions in advance, just to make Sui crash,” he declared.
In addition, he believes the fix for the problems was vibe-coded with AI and applied. “For such a large project, they shouldn’t rely entirely on AI. They should use multiple AI models for batch detection and then perform a final manual validation before submission,” he recommended.
Nonetheless, at approximately 4:30 PM EDT, Sui faced yet another issue that stopped transactions from getting processed. Sui linked it to a problem during the epoch change, as validators created system transactions but ignored user transactions. “The Sui Core Team is investigating, and updates will be shared as soon as available,” it concluded.
Leave a Reply
You must be logged in to post a comment.