Critical system bugs negatively impacted the Zilliqa mainnet’s block production on Sept. 27 and 29, forcing the blockchain network to halt transactions temporarily while the issue is fixed.
On Sept. 29, Zilliqa proactively reported a system bug that suddenly disabled the network from creating new blocks. At the same time, several crypto investors reported difficulties accessing their funds on ZilPay, a browser wallet for the Zilliqa blockchain.
Source: Zilliqa
Community members raised concerns about the Zil chain, considering it had recovered from a similar event two days ago on Sept. 27. However, the previous bug caused block production to slow down drastically, unlike the current bug, which completely stalled block production.
In response to concerns raised by users on X, Zilliqa stated:
“Network was operational and working fine until network stopped producing blocks and stalled due to another bug last night. The Zilliqa team is looking into the issue, debugging and attempting to restore the network. Please stay tuned for further updates.”
Zilliqa struggles with block production bugs
Zilliqa also clarified that the persistent network issues are unrelated to its recent Zilliqa 2.0 upgrade, which focuses on speed and cross-chain compatibility.
There was a drastic drop in Zilliqa transactions and block production due to system bugs. Source: ViewBlock
The Sept. 27 bug, which slowed down block production, was rectified on the same day. At the time, Zilliqa confirmed that “the network is now fully operational.” However, the Sept. 29 bug is taking longer to resolve.
Source: Zilliqa
The Zilliqa network has not yet resumed normal operations at the time of publication. However, the blockchain has been restored for validators and works for a “permanent fix“ is underway, according to an X post from the Zilliqa team.
Related: Critical bug identified and remedied in Circle’s Noble-CCTP
Timely bug fix avoided a $126 million attack
Recently, Cosmos developers fixed a “critical” security bug in its Inter-Blockchain Communication (IBC) protocol that put at least $126 million at risk.
Source: Asymmetric Research
The bug could be exploited for a reentrancy attack, which would allow hackers to mint infinite tokens on IBC-connected chains such as Osmosis and other decentralized finance ecosystems on Cosmos.
GitHub commits data shows that Cosmos developer Carlos Rodríguez patched the bug up.
Magazine: Worldcoin fined again! Crypto store clerk runs off with $500K cash: Asia Express