Solana developers share 3 key mitigation steps to make the network robust

cointelegraph.com:

TheSolana network faced its seventh outage on April 30, resulting in a downtime of over seven hours. The developer team has come out with an outage report along with three key mitigation steps to make the network more stable.

The network outage on Solana was caused by a significant surge in the number of transactions due to nonfungible token (NFT) minting bots. The bots used Candy Machine, a popular application used by Solana NFT projects to launch collections.

The transaction volume reached 6 million per second, overflowing individual nodes with 100 Gbps data. As a result, validators ran out of data memory, leading to a loss of consensus among them.

The developers ruled out distributed denial of service (DDoS) attacks and blamed NFT minting bots for the congestion. The network came online at 03:30 UTC on Sunday, May 1.

The official report highlighted three key mitigation steps that are in work to make the Solana network more resilient against such congestion issues. The first major step is to move from its current data transfer protocol called user datagram protocol (UDP) to Google-developed quick UDP internet connection (QUIC). QUIC offers fast asynchronous communication like UDP, but with sessions and flow control like transmission control protocol.

The second key step is the integration of stake-weighted transaction processing, instead of its current first-come-first-serve basis. The developers claimed a stake-weighted transaction processing along with QUIC would be more robust.

The third mitigation step is to introduce “Fee-based execution priority,” where users would have the option to add an additional fee on top of the base fee. The fee prioritization is set for the v1.11 release.

Related: Solana DAOs can now bug you