The community has recently become buzzy about Solana’s network congestion and botched transactions. In response, Matt Sorg—Solana’s Tech and Product Lead—shared an article suggesting that a failed transaction is a “feature of user protection” rather than a “bug.”
Over 75% of transactions in Solana are said to have failed as a result of recent transaction problems. Colin Wu, a Chinese crypto reporter for Wu Blockchain, mentioned in a recent X article that the Solana network has been dealing with unsuccessful or delayed transactions. QUIC and Agave client implementations are said to be the foundation of the main problem.
Sorg claimed that unsuccessful transactions are not the cause of the current problems. Assuring that the problem has “known solutions,” he continued,
“Transaction dependability is crucial, and things can’t continue as they are right now. It is untrue to suggest that the network has a basic weakness. The scalability ceiling of Solana, a very efficient protocol, has not yet been reached. This specific problem isn’t related to failed transactions or the protocol’s transaction processing section.”
Uncovering the true meaning of the term “failure,” Sorg clarified that a transaction failure is “an application-level functionality,” meaning that while the transactions are marked as unsuccessful, the protocol’s incapacity to handle the logic or load is not implied. “The network is protecting consumers and users by checking the conditions of a transaction,” he continued.
The execution level is indicated when the transaction is included in a block and the fee is paid, according to Sorg, who also went into detail about the transaction results, which might be either “executed” or “dropped.” The level has two subcategories: executed successfully and executed but unsuccessfully. The transaction is executed successfully when there are no errors in it; if an error is returned, the transaction is executed but failed.
April 2024, Cryptoniteuae
