Solana developers have set their sights on April 15 as the date to address an “implementation bug” that caused a significant increase in transaction failure rates on the Solana network. Mert Mumtaz, the CEO of Helius Labs, a blockchain infrastructure firm that exclusively supports the Solana network, emphasized that the issue is not a design flaw but rather a bug in the implementation process. Mumtaz highlighted the importance of distinguishing between implementation errors, which are typically minor, and design errors, which are more serious and fundamental. On April 4, data revealed that over 75% of non-vote Solana transactions failed due to a recent surge in memecoin activity on the network. However, this figure has since dropped to 64.8%. According to Mumtaz, the problem lies in the way Solana developers implemented “QUIC,” a data transfer protocol developed by Google that involves all nodes in the network. He compared this issue to car design, explaining that while all cars have similar components, there are various implementations of the design, such as BMW, Mercedes, Toyota, F1, and Tesla. If one BMW model has poor steering, it does not mean that all cars are flawed; it simply means that specific model needs fixing. Similarly, Solana’s implementation of QUIC has some deficiencies and bugs that need to be addressed, but it does not require a complete overhaul of the network. Mumtaz also mentioned a comment from Solana researcher Richard Patel, who believes that Firedancer’s implementation does not suffer from the same issues. Assuming no additional problems arise during testing, the fix is scheduled for April 15. Cointelegraph reached out to Mumtaz to inquire about the specifics of the fix but did not receive an immediate response. The network failures on Solana have raised concerns within the community, considering that Solana’s native token, SOL, has a market cap of $79.9 billion, and an additional $4.6 billion is locked on the network, according to DefiLlama.
Solana developers aim to address failed TX by April 15, clarifying that it is not a design defect.
No Comments2 Mins Read
Related Posts
Add A Comment