Zilliqa blockchain crashes again, ‘permanent maintenance’ underway.
On September 27th and 29th, critical system bugs adversely affected the blockchain production of the Zilica mainnet, forcing the blockchain network to temporarily halt transactions while the problem was fixed.
On September 29, Zilica actively reported a system bug that prevented the network from creating new blocks randomly. At the same time, several crypto-investors reported having difficulty accessing their funds on Zilpay, a browser wallet on Zilka's blockchain.
Source: Zilica
Community members raised their concerns about the Zill chain on September 27, considering that it had recovered from a similar incident two days earlier. But the previous fault, unlike the current fault, caused a significant drop in block production.
In response to user concerns about X, Zilica said:
“The network started up and was working fine until it stopped producing network blocks and was stopped by another error last night. The Zilica team is looking into the issue, trying to fix it and restore the network. Please stay tuned for more updates.”
Zilica struggles with block production bugs
Zelica clarified that the ongoing network issues are not related to the recently launched Zelica 2.0 update, which focuses on speed and cross-chain compatibility.
Zilica's transactions were drastically reduced and production was halted due to system errors. Source: ViewBlock
The September 27 bug, which reduced block production, was fixed the same day. At the time, Zilica confirmed that “the network is now fully operational.” However, the September 29 bug is taking longer to resolve.
Source: Zilica
At the time of publication, the Zilica network had not yet begun formal operations. However, the blockchain is back for validators and works for “permanent maintenance,” the Zelica team explained in an X article.
Related: Critical Bug Identified and Fixed in Circle's Noble-CCTP
At the time, bug fixes averted a $126 million attack.
Cosmos developers recently fixed a “critical” security flaw in its Inter-Blockchain Communication (IBC) protocol that put at least $126 million at risk.
Source: Asymmetric Research
The flaw could be exploited for a re-entry attack, which would allow hackers to create infinite tokens on Cosmos in IBC-related platforms like Osmosis and other decentralized financial ecosystems.
According to a GitHub commit, Cosmos developer Carlos Rodriguez has fixed the bug.
Magazine: Worldcoin Punished Again! Crypto Store Clerk Makes $500K Cash: Asia Express
