Zilliqa developers have announced a permanent fix for a bug that compelled the blockchain to halt transactions over the weekend.
In their latest X post, Zilliqa developers clarified that they were working on fixing a bug that prevented the blockchain from creating new blocks. The bug which was identified on Sept. 29, left users unable to conduct transactions and access their funds.
Notably, this latest setback followed another bug flagged on Sept. 27, when block production was slowed down, although it didn’t result in a full network halt. The developers managed to deploy a fix on the same day, restoring normal operations swiftly, but the recurrence of technical issues just two days later has raised concerns about the stability of the network’s infrastructure.
Some community members have questioned the timing of these issues, which emerged shortly after the Zilliqa 2.0 upgrade, an update intended to enhance network speed and cross-chain compatibility. However, Zilliqa has clarified that these recent disruptions are unrelated.
At the time of writing, the network was yet to resume normal operations and deploy the permanent fix, but block production had been restored for validators. Meanwhile, the developers have assured users that all funds are safe.
The recent issues have affected the price of the blockchain’s native token, ZIL (ZIL), which had slipped over 2.3% in the past 24 hours.
Block generation hiccups have become a recurring theme for Zilliqa, and these latest setbacks echo similar issues seen over the past year.
In May, the network experienced a slowdown in block production, followed by a brief transaction halt. While developers managed to resolve the issue with a subsequent update at the time, they acknowledged that the root cause of the problem had not been fully identified.
Similarly, the network encountered another disruption in December 2023, with block production slowing down for nearly half a day.
In related news, Ethereum layer 2 solution Starknet faced an outage earlier this year that prevented transactions from being processed on-chain. More recently, layer 1 protocol Canto also faced back-to-back outages due to issues with its consensus mechanism.
