• Solana recently experienced transaction failures across 75% of transactions.

  • Team Lead Matt Sorg responded that the failure was not a bug but a feature of user protection.

  • Matt details the types of transaction results, pouring more light into the prevailing issues.

Solana’s network congestion and failed transactions have created a buzz in the community recently. Responding to the matter, Matt Sorg, the Tech and Product Lead at Solana, shared an article positing that a failed transaction is not a “bug” but a “feature of user protection.”

https://t.co/bsVVfaiGWG

— Matt Sorg 🍨 (@tamgros) April 5, 2024

Solana recently experienced transaction issues, with around 75% of transactions reportedly failed. According to a recent X post shared by Colin Wu, a Chinese crypto reporter on Wu Blockchain, the Solana network has been confronting delayed or failed transactions. Reportedly, the core issue is based on a QUIC implementation and an Agave client implementation.

Phantom shows that the Solana network is currently experiencing congestion and users' transactions may fail or be delayed. The core issue relates to a QUIC implementation, and the behavior of the Agave validator client on Solana when asked to process a large number of requests.… https://t.co/KuutKBbB0B

— Wu Blockchain (@WuBlockchain) April 6, 2024

Sorg asserted that the prevailing issues aren’t a matter of failed transactions. Ensuring that there are “known solutions” for the issue, he added, “

“Transaction reliability is incredibly important and the current status is unacceptable. The implication that there is a fundamental flaw in the network is incorrect. Solana is a highly efficient protocol that hasn’t nearly hit its scaling ceiling. This particular issue doesn’t hit the transaction processing part of the protocol and isn’t an issue of failed transactions.”

Unveiling the real connotation of the word “failure,” Sorg explained that a transaction failure is “an application-level functionality.”  Though the transactions are entitled as failed, they do not imply the protocol’s inability to process the logic or load.  He added, “When a transaction fails, the network is protecting consumers and users by checking the conditions of a transaction.”

Further, Sorg elaborated on the transaction results, which could be either “executed” or “dropped.” The execution level is marked when the transaction is included in a block, and the fee is paid. There are two subcategories for the level: Executed Successful and Executed but failed. When there is no error in the transaction, it is executed successfully, and if it returns an error, it is executed but failed.

Commenting on Solana’s recently reported transaction failures, Sorg referred to the result as “dropped.” He added that the troubles can arise when “any of the conditions in the transaction logic aren’t met.”

The post Solana’s Team Lead Ensures “Known Solutions” for Transaction Failures appeared first on Coin Edition.