Solana faces network degradation for the second time this week
Solana suffered a fourth network incident in Spain a few months. Two out of the four issues happened for the current week.
The Solana blockchain has faced its second network performance degradation incident this week, according to Solana, this is happening rise in high compute transactions.
Therefore, the network limit, which was initially advertised to be 50,000 transactions per second(TPS), was decreased to several thousand TPS, Solana referred to this as the reason why users experienced failed transactions and added that its developers are already working to fix the issue.
The network issue came only a couple of days after a similar incident on Tuesday, where users experienced the same problems. Many speculated that the Tuesday incident was due to a distributed denial of service (DDoS) attack, but Solana co-founder Anatoly yakovenko reacted on Twitter. saying that it's just the "pain of getting a new runtime commercialized."
Cyber capital chief investment officer Justin Bons communicated his objection with Solana and published a series of tweets enumerating the reasons why he doesn't support the project. Bonus claims that Solana is "consistently showing a pattern of bad behavior" and "prioritizing attracting ignorant investors over attractive blockchain design"
Bons also criticized the security of the network, targeting that DDoS attacks are not the only concern. He said that DDoS can be combined with a 51% attack. with this, he claims that attackers can "temporarily gain proportional-staked control over the network by attacking other stakeholders."
Yakovenko excused this as "exhausting nonsense," expressing, "it's difficult to DDoS a private key."
The previous year, Solana was hit by a DDoS attack causing a similar effect and degrading the network's performance. Solana Labs head of communications Austin Federa said that the outage came after several transactions during an initial DEX offering "landed in a Solana block that took an excessive amount of computing power." "compute for those kinds of transactions wasn't properly metered by the network, and caused blocks to take much longer to process than the network expected," Federa expressed.