The Evolution of Cypherpunk Values in Smart Contract Platforms
September 30, 2024
Bitcoin’s Future: How the Upcoming U.S. Presidential Election Could Influence Prices
September 30, 2024Zilliqa Faces Block Production Issues Amid System Bugs
On September 27 and 29, critical system bugs adversely affected the block production of the Zilliqa mainnet, necessitating a temporary halt in transactions while the team worked on fixes. On September 29, Zilliqa proactively disclosed a system bug that prevented the network from generating new blocks, coinciding with reports from several crypto investors who encountered difficulties accessing their funds through ZilPay, a wallet for the Zilliqa blockchain.
Community Concerns Arise
Community members expressed growing concerns about the stability of the Zilliqa chain, especially in light of a similar incident that had occurred just two days prior. While the first bug on September 27 resulted in slowed block production, the second bug led to a complete stall. Addressing the worries of users on social media platform X, Zilliqa stated:
“The network was operational and working fine until it stopped producing blocks due to another bug last night. The Zilliqa team is investigating the issue, debugging, and working to restore the network. Please stay tuned for further updates.”
Unrelated to Zilliqa 2.0 Upgrade
Zilliqa clarified that the two incidents were unrelated to its recent Zilliqa 2.0 upgrade, which aims to enhance speed and cross-chain compatibility. The September 27 bug was resolved on the same day, with Zilliqa confirming that the network was “fully operational” thereafter. However, the issue on September 29 took longer to address. At the time of publication, while normal operations had not yet resumed, the network had been restored for validators, and work on a “permanent fix” was in progress.
Zilliqa’s challenges come amid heightened scrutiny of blockchain security, highlighted by a recent incident involving Cosmos developers who fixed a critical bug in their Inter-Blockchain Communication (IBC) protocol. This bug posed a risk of a reentrancy attack that could have potentially allowed hackers to mint infinite tokens on IBC-connected chains, jeopardizing at least $126 million. The bug was patched by Cosmos developer Carlos Rodríguez, emphasizing the importance of timely responses to vulnerabilities in the blockchain space.
