In keeping with the Sui community’s official standing web page, the blockchain is dealing with a “main outage” because it has stopped processing consumer transactions. The Sui staff defined that the newest stall is said to the repair of the primary stall, and an issue that surged on the epoch change.
Key Takeaways:
- Sui halted for a third time in 2 days, disrupting the market because the Core Workforce subsequent works on a long-term repair.
- The trigger appears to be the brand new stablecoin’s 0-fee transaction logic, which had design defects.
- Sui halted once more at 4:30 PM EDT, freezing consumer transactions because it investigates points concerning epoch change.
Sui Falls For The Third Time
Sui, a high-performance blockchain, has skilled points with its community exercise for the third time in two days.
The official Sui standing web page indicated that the community stopped processing transactions at 7:58 AM EDT, affecting community operability fully.
The Sui staff acknowledged this concern on social media, stating that their mainnet was experiencing a “community stall” and that it was searching for an answer. “Remember that transactions could also be paused presently. Updates will probably be shared as quickly as they’re out there,” they posted.
At 11:34 AM EDT, the community was processing transactions once more, with Sui’s staff explaining that each right now’s and yesterday’s issues had been linked to the “ fuel charging logic” adjustments that the blockchain not too long ago utilized to make stablecoin transactions free.
“Yesterday’s carried out repair was an interim measure designed to revive performance to the community whereas the Sui Core Workforce labored on a long-term answer. The interim repair had a recognized concern with a low chance of inflicting a halt. This morning, the community hit a variant of the recognized concern and halted,” Sui defined, stressing that community exercise had resumed.
X consumer 0xarthur.sui alleged that whereas the primary community stall was doubtless attributable to a design defect, this second one was perpetrated by a risk actor. “A hacker doubtless opened quick positions prematurely, simply to make Sui crash,” he declared.
As well as, he believes the repair for the issues was vibe-coded with AI and utilized. “For such a big challenge, they shouldn’t rely totally on AI. They need to use a number of AI fashions for batch detection after which carry out a ultimate handbook validation earlier than submission,” he really useful.
Nonetheless, at roughly 4:30 PM EDT, Sui confronted one more concern that stopped transactions from getting processed. Sui linked it to an issue throughout the epoch change, as validators created system transactions however ignored consumer transactions. “The Sui Core Workforce is investigating, and updates will probably be shared as quickly as out there,” it concluded.
