- September 14 Solana and Arbitrum One disconnected after large batches of transactions overloaded their networks.
- An unknown entity attempted to attack Ethereum unsuccessfully via an invalid sidechain.
Tuesday, September 14th was quite a drama- busy day in the crypto industry. One of Ethereum's toughest rivals First Solana (SOL) announced a denial of service outage at 12:38 UTC. Solana tweeted that her mainnet beta has been experiencing intermittent instability for about 45 minutes.
Six hours after start of her investigation, Solana attributed the incident to a sharp increase in the transaction load reaching 400,000 TPS. The surge overwhelmed the network, causing a denial of service and a forking of the network.
Solana engineers not having succeeded in stabilizing the network, it became necessary for the validators to restart it . The Solana community is now preparing for a new release, with more details about it coming soon.
Learn more about Solana, Arbitrum downtime
Consequentl y, the disruption caused a reduction in the trust of the Solana network and SOL lost 15% in 12 hours. The token had hit an all-time high of $ 215 on September 9, but fell below $ 175 before yesterday's incident. As word of the outage spread, SOL prices dropped to $ 145. At the time of writing, however, the token is trading at $ 164.10 according to our data .
Another very media networktized that suffered downtime yesterday was Arbitrum One, an Ethereum layer -two stacks. The network reported that its sequencer was offline for approximately 45 minutes, preventing transactions from being submitted. Since the network is still in beta, Arbitrum has warned that "more failures are possible in the early days ". Nonetheless, the network pointed out that user funds "have never been at risk.
Just like Solana, a very large batch of transactions have been submitted to the Arbitrum sequencer over a short period of time. Network downtime occurred after a bug caused the "sequencer to hang ".
Attack on Ethereum
To add to it all, Ethereum (ETH) was also unsuccessfully attacked by an unknown entity onsame day. The "experimental " early morning attack temporarily hijacked 0.8% of Ethereum nodes to an invalid chain. Alex S. of Flexpool on Ethereum R&D Discord was the first to report the event shortly after 3:00 a.m. ET.
" Is there still a problem with the main network? He wrote, referring to the channel split at the end of August. He also noted that some of his nodes recorded the "highest block" in the chain at a technically non-existent block number.
Ethereum developer Marius Van Der Wijden reported the incident on Twitter saying:
However, only a small percentage of Nethermind nodes were tricked into switching to the invalid chain. All other clients rejected the long side chain as invalid. All affected nodes have since reorganized to return to the chaincorrect.
Additionally, Van Der Wijden noted that