Site iconSite icon ForkLog

Outage hits Arbitrum scaling protocol

Outage hits Arbitrum scaling protocol

On September 14 at around 17:14 MSK, the Ethereum Layer-2 solution Arbitrum experienced a 45-minute outage due to a bug in the Sequencer contract. During this period the network did not process transactions.

The developers said that user funds were safe. Transactions accepted during the outage were assigned a new timestamp of 17:59 MSK, when the Sequencer came back online, but their order was preserved.

“The Sequencer cannot steal funds or forge transactions, because every transaction it processes bears the user’s digital signature, which is verified by the Arbitrum chain. User funds were not at risk,” the developers emphasised.

The primary cause of the outage was a Sequencer bug that received a very large burst of transactions in a short time. The project team is working on fixing the bug.

They also said that the Arbitrum network is resilient to prolonged Sequencer outages.

“Users have the option to bypass the Sequencer and submit transactions directly to Ethereum for delayed inclusion in the Arbitrum chain, and this option was fully preserved during the incident,” the developers explained.

The project team warned of possible repeat outages, as Arbitrum One, whose launch took place at the end of August, remains in beta testing.

Earlier this week, the value of assets on Arbitrum reached $2.2 billion.

Subscribe to ForkLog news on Telegram: ForkLog Feed — the full news feed, ForkLog — the most important news, infographics and opinions.

Exit mobile version