How Did Solana’s Recent Outgate Incident Happen?
According to a Solana Foundation update, the recent Solana blockchain downtime was caused by a bug in the blockchain’s code and was afflicted by a failing hot spare node, resulting in duplicate blocks.
When a validator operates a second node that is online and meant to be utilized as a backup if the primary one fails, this is referred to as a hot-spare node. Nonetheless, the spare node got live and was functioning alongside the primary one. As a result, the two nodes sent separate blocks to the network, resulting in parallel blocks.
For the first 24 hours, this was handled nicely, as the blockchain ended up picking between the two alternate blocks as it would with any tiny fork in the network. However, a fault in the blockchain’s coding caused it to fail to create any further blocks after one of these options.
Initially, duplicate blocks were handled by the network as expected. However, at the next slot, 221, duplicate blocks were observed again but an edge case was encountered.
Even though the correct version of block 221 was confirmed, a bug in the fork selection logic prevented block producers from building on top of 221 and prevent the cluster from achieving consensus.
What came in the end, Solana was down for about seven hours, and the problem was fixed after that.
DISCLAIMER: The Information on this website is provided as general market commentary and does not constitute investment advice. We encourage you to do your own research before investing.
Join us to keep track of news: https://linktr.ee/coincu
Website: coincu.com
Harold
CoinCu News
Author
Blockchain
How Did Solana’s Recent Outgate Incident Happen?
According to a Solana Foundation update, the recent Solana blockchain downtime was caused by a bug in the blockchain’s code and was afflicted by a failing hot spare node, resulting in duplicate blocks.
When a validator operates a second node that is online and meant to be utilized as a backup if the primary one fails, this is referred to as a hot-spare node. Nonetheless, the spare node got live and was functioning alongside the primary one. As a result, the two nodes sent separate blocks to the network, resulting in parallel blocks.
For the first 24 hours, this was handled nicely, as the blockchain ended up picking between the two alternate blocks as it would with any tiny fork in the network. However, a fault in the blockchain’s coding caused it to fail to create any further blocks after one of these options.
Initially, duplicate blocks were handled by the network as expected. However, at the next slot, 221, duplicate blocks were observed again but an edge case was encountered.
Even though the correct version of block 221 was confirmed, a bug in the fork selection logic prevented block producers from building on top of 221 and prevent the cluster from achieving consensus.
What came in the end, Solana was down for about seven hours, and the problem was fixed after that.
DISCLAIMER: The Information on this website is provided as general market commentary and does not constitute investment advice. We encourage you to do your own research before investing.
Join us to keep track of news: https://linktr.ee/coincu
Website: coincu.com
Harold
CoinCu News
Other Posts
Related Posts
News
90% Of Stablecoin Transaction Volumes Have No Participation From Real Users
Analysis
Market Overview (Apr 29 – May 5): Ethereum Security Status, Bitcoin ETF, and Market Predictions
News
90% Of Stablecoin Transaction Volumes Have No Participation From Real Users
Knowledge
US Election Predictions: The Effects And Importance Of The New US President
News
