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 was 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.
Community members raised concerns about the Zil chain, considering it had recovered from a similar event two days before on Sept. 27. Still, the first bug caused block production to slow, unlike the second, which completely stalled block production.
In response to concerns raised by users on X, Zilliqa said:
“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 added that that the two network issues were unrelated to its recent Zilliqa 2.0 upgrade, which focuses on speed and cross-chain compatibility.
The Sept. 27 bug, which slowed 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 was taking longer to resolve.
The Zilliqa network had not yet resumed normal operations at the time of publication. However, the blockchain was restored for validators and work for a “permanent fix“ was underway, according to an X post from the Zilliqa team.
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.
The bug potentially could have been exploited for a reentrancy attack, which could 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.