Again it was unfortunately hit for the Solana (SOL) blockchain. The network was experiencing major problems and the network speed was temporarily significant diminished. Originally, the network was supposed to handle 50,000 transactions per second, but this was reduced to just a few thousand. These new problems arose just days after the network fell victim to an attack that also destroyed the capacity of the Solana network.
Solana in trouble
Last Tuesday the Solana network was attacked with a so-called distributed denial of service (DDoS) attack. The network was overloaded with spam transactions and the network speed plummeted as a result of this attack.
So just a few days later it happened again. This time, however, there does not appear to be an organized attack, but the network is simply overloaded by too many transactions. Users are reporting that transactions are failing and Solana’s team has indicated they are working on a fix.
Strong criticism
From CIO van Cyber Capital, Justin Bons, indicated some time ago that he believes the Solana network is fundamentally chock-full of vulnerabilities. The repeated attacks on the network and common capacity problems are the result of a poorly designed blockchain, Bons said.
In fact, he points out that Solana’s team is showing “patterns of bad behavior” and that the team is only concerned with attracting “ignorant investors” rather than addressing existing problems with the network.
Anatoly Yakovenko
Solana co-founder Anatoly Yakovenko rejects these criticisms. According to him, the recent attacks on the network part of the process to commercialize the network.
Yakovenko also lashed out hard at Justin Bons and his fierce criticism of the project. According to Yakovenko, Bons’ words are complete nonsense.
????♂️, exhausting nonsense. it’s impossible to ddos a private key. The public key of which validator signs the shreds for the block are in the leader schedule, not the physical link on which they receive txs or transmit shreds. https://t.co/ZNIy49PIb4
– anat ◎ ly ????????????) (@aeyakovenko) January 6, 2022
–
