Cosmos

Zilliqa

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.&nbsp;
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.
<figure>
 <img alt="Zilliqa blockchain malfunctions again, ‘permanent fix’ underway" name="" src="https://s3.cointelegraph.com/uploads/2024-09/019241cb-cf84-741e-a8e3-044022f11a69">
 <figcaption style="text-align: center;">
 Source: <a data-ct-non-breakable="null" href="https://x.com/zilliqa/status/1840123434258317685" rel="null" target="null" text="null" title="https://x.com/zilliqa/status/1840123434258317685">Zilliqa</a>
 </figcaption>
</figure>
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 <a data-ct-non-breakable="null" href="https://x.com/zilliqa/status/1840224621179646057" rel="null" target="null" text="null" title="null">said</a>:
<blockquote>
 “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.”
</blockquote>
<h2 id="zilliqa-struggles-with-block-production-bugs">Zilliqa struggles with block production bugs </h2>
Zilliqa added that that the two network issues were unrelated to its <a data-ct-non-breakable="null" href="https://cointelegraph.com/news/zilliqa-2-0-upgrade-sharding-evm" rel="null" target="null" text="null" title="https://cointelegraph.com/news/zilliqa-2-0-upgrade-sharding-evm">recent Zilliqa 2.0 upgrade</a>, which focuses on speed and cross-chain compatibility.&nbsp;
<figure>
 <img alt="Zilliqa blockchain malfunctions again, ‘permanent fix’ underway" name="" src="https://s3.cointelegraph.com/uploads/2024-09/019241cc-4929-7b62-9be4-d4fe08c6ac3d">
 <figcaption style="text-align: center;">
 There was a drastic drop in Zilliqa transactions and block production due to system bugs. Source: ViewBlock
 </figcaption>
</figure>
The Sept. 27 bug, which slowed block production, was rectified on the same day. At the time, Zilliqa <a data-ct-non-breakable="null" href="https://x.com/zilliqa/status/1839724284773839217" rel="null" target="null" text="null" title="null">confirmed</a> that “the network is now fully operational.” However, the Sept. 29 bug was taking longer to resolve.&nbsp;
<figure>
 <img alt="Zilliqa blockchain malfunctions again, ‘permanent fix’ underway" name="" src="https://s3.cointelegraph.com/uploads/2024-09/019241cc-8a1b-737b-917f-653b32f6269e">
 <figcaption style="text-align: center;">
 Source: <a data-ct-non-breakable="null" href="https://x.com/zilliqa/status/1840447094232096810" rel="null" target="null" text="null" title="https://x.com/zilliqa/status/1840447094232096810">Zilliqa</a>
 </figcaption>
</figure>
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.
Related: <a data-ct-non-breakable="null" href="https://cointelegraph.com/news/critical-bug-identified-remedied-circle-noble-cctp" rel="null" target="null" text="null" title="null">Critical bug identified and remedied in Circle’s Noble-CCTP</a>
<h2 id="timely-bug-fix-avoided-a-126-million-attack">Timely bug fix avoided a $126 million attack </h2>
Recently, <a data-ct-non-breakable="null" href="https://cointelegraph.com/news/cosmos-patches-bug-ibc-protocol-saves-126m" rel="" target="_self" text="null" title="https://cointelegraph.com/news/cosmos-patches-bug-ibc-protocol-saves-126m">Cosmos developers fixed a “critical” security bug</a> in its Inter-Blockchain Communication (IBC) protocol that put at least $126 million at risk. 
<figure>
 <img alt="Zilliqa blockchain malfunctions again, ‘permanent fix’ underway" name="" src="https://s3.cointelegraph.com/uploads/2024-09/019241cc-f2da-7173-8f95-a8e7baf15b2a">
 <figcaption style="text-align: center;">
 Source: <a data-ct-non-breakable="null" href="https://x.com/asymmetric_re/status/1782765042540138805" rel="null" target="null" text="null" title="https://x.com/asymmetric_re/status/1782765042540138805">Asymmetric Research</a>
 </figcaption>
</figure>
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 <a data-ct-non-breakable="null" href="https://github.com/cosmos/ibc-go/security/advisories/GHSA-j496-crgh-34mx" rel="nofollow noopener" target="_blank" text="null" title="https://github.com/cosmos/ibc-go/security/advisories/GHSA-j496-crgh-34mx">data</a> shows that Cosmos developer Carlos Rodríguez patched the bug.
 Magazine: <a data-ct-non-breakable="null" href="https://cointelegraph.com/magazine/worldcoin-fined-dmm-bitcoin-system-face-ban-asia-express/" rel="null" target="null" text="null" title="null">Worldcoin fined again! Crypto store clerk runs off with $500K cash: Asia Express</a>

Zilliqa blockchain malfunctions again, ‘permanent fix’ underway

Table of Contents

Cointelegraph

Other articles published on Sep 30, 2024

Crypto market hits Monday blues ahead of September economic data

Bitcoin Defies History: BTC Prepares to Enter a Bullish Month! Will History Repeat Itself?

eCash Monthly Recap - September 2024

Ripple CTO Reacts To New XRP Burn Proposal That Creates New Token

Market Analysts Assess Bitcoin, DXY, and TAO Coin Trends

Hamster Kombat Token Crashes 39%: What Happened to HMSTR?

Join our free newsletter for daily crypto updates!