Avalanche blockchains fail due to bugs in new software
As a result of the failure, the network’s throughput has significantly decreased
23.03.2023 - 10:45
1251
2 min
0
Avalanche’s AVAX token fell nominally after nodes on the protocol’s X- and C-Chains went down due to bugs in a new software release.
Avalanche is unique as it uses three chains: the C-Chain, X-Chain and P-Chain.
The C-Chain is home to Avalanche’s decentralized finance (DeFi) community and is the chain that hosts smart contracts and is used with MetaMask. The X-Chain is the exchange chain, used to send funds back and forth. The P-Chain is the platform chain, which is used for staking AVAX and serving as a validator.
While the C-Chain recovered after an hour-long outage, some X-Chain nodes are still offline as of time of publication.
On-chain data shows the network quality of X-Chain has been degraded, and it's only able to process a handful of transactions. It appears that it's only able to process a few transactions per hour, making the chain virtually unusable.
Over 90% of validators have upgraded to the latest version of AvalancheGo. This is up from 12% earlier Thursday.
While Avalanche has yet to make a public statement regarding the outage, many contributors are working on its GitHub forum to resolve the issue.
AVAX is trading for $16.89 at writing time in Asian afternoon hours on Thursday.
This material is taken from the website https://www.coindesk.com.
Useful material?
Incidents
The company is linking the incident to a compromised private key on a service wallet, rather than a smart contract exploit
May 22, 2026
Incidents
Following the incident, the project temporarily halted trading operations and node activity.
May 15, 2026
Incidents
The user spent weeks unsuccessfully trying to guess the password until Claude helped find an old wallet backup file
May 14, 2026
Crypto regulations
Authorities are introducing mandatory registration for companies handling cross-border crypto transactions
May 8, 2026
Incidents
According to Blockaid, the attack may have been carried out by the same hacker behind the 1inch Fusion V1 exploit.
May 7, 2026
Incidents
The attacker gained administrative access and altered contracts to drain user funds
Apr 30, 2026
Telegram
Twitter