Avalanche halts block production amid inscription wave launch
|The decentralized application (DApp) platform Avalanche had a significant technical disruption impacting the block production of the proof-of-stake (PoS) blockchain.
On Feb. 23 at 12:02:27 pm UTC, Avalanche’s primary network experienced block production issues, seemingly halting the network. Avalanche’s blockchain explorer showed that the last block on Avalanche’s P-Chain, X-Chain and C-chain subnets was produced over an hour earlier. Avalanche also put out an official alert related to the block finalization stall. In a status update, Avalanche wrote:
Developers across the community are currently investigating a stall in block finalization that is preventing blocks from being accepted on the Primary Network.
Block production is an important process for the stability and continuity of blockchain networks. It involves the inception of new blocks that validate and record transactions. Interruptions in the block production process result in delays in transaction processing, impacting the overall functionality of the network.
In an X post, Kevin Sekniqi, the co-founder of Ava Labs, said the team is already investigating the issue. According to Sekniqi, the halt in block production may be connected to a “new inscription wave” launched an hour before the problems surfaced.
The Ava Labs executive believes that the issue might be an “esoteric bug from some edge case” and mentioned that the issue is likely a mempool handling issue with inscriptions. Sekniqi assured the community that this would be “handled quickly.”
Nearly an hour later, Sekniqi clarified that the issue was a code-related bug unrelated to performance handling. The executive explained that inscriptions may have hit the edge case but did not affect performance.
Clarification on this: the issue seems to be a gossip-related mempool management bug, which is purely a code-related bug, and not an issue with performance handling. Inscriptions seem to have hit the edge case, but inscriptions did not affect performance. https://t.co/9cvQSAmTVu
— Kevin Sekniqi (@kevinsekniqi) February 23, 2024
Clarification on this: the issue seems to be a gossip-related mempool management bug, which is purely a code-related bug, and not an issue with performance handling. Inscriptions seem to have hit the edge case, but inscriptions did not affect performance. https://t.co/9cvQSAmTVu
— Kevin Sekniqi (@kevinsekniqi) February 23, 2024
Similar reports on Avalanche’s block production halting surfaced on March 23, 2023. At the time, the Avalanche blockchain explorer showed that the C-chain stopped producing blocks. However, Sekniqi explained that the network had been unstable due to a bug with its v1.9.12, and the team deployed a fix to stabilize the network.
Information on these pages contains forward-looking statements that involve risks and uncertainties. Markets and instruments profiled on this page are for informational purposes only and should not in any way come across as a recommendation to buy or sell in these assets. You should do your own thorough research before making any investment decisions. FXStreet does not in any way guarantee that this information is free from mistakes, errors, or material misstatements. It also does not guarantee that this information is of a timely nature. Investing in Open Markets involves a great deal of risk, including the loss of all or a portion of your investment, as well as emotional distress. All risks, losses and costs associated with investing, including total loss of principal, are your responsibility. The views and opinions expressed in this article are those of the authors and do not necessarily reflect the official policy or position of FXStreet nor its advertisers.