- It lasted several hours
- At this time, transaction batches were not hosted on Ethereum
- The error lay in the sequencer, which did not finalize the translations
- The bug was quickly fixed and the network returned to normal operation.
Yesterday, June 7, Arbitrum suspended work for several hours. The failure occurred due to a bug in the sequencer, which resulted in an overload. The bug was quickly fixed.
“The sequencer is responsible for accepting user transactions, creating a package, and placing it on the chain. As soon as this happens, an application for its implementation is received. At this time, the sequencer continues to collect off-chain transactions” – explain in Arbitrum.
Apparently, the error was in the mechanism for placing the package on-chain. When the sequencer tried to publish it to the network, an error occurred and the transaction failed.
That is, for some time the sequencer did not finalize transactions, but at the same time it regularly performed other functions. The bug was quickly fixed, after which the problem was solved.
Also, the Arbitrum team denied the information that the reason for the failure was a lack of funds in the sequencer. An analysis of the event shows that the funds were sent correctly, but the package was never placed on the Ethereum network.
The crash lasted several hours. The administration claims that all transactions have been successfully completed, and the sequencer continues to work normally. The incident had no effect on the ARB course.
As a reminder, we previously reported that USDC will work in the Arbitrum network. In the near future, all users will be able to exchange the “bridge” token for a regular stablecoin at a rate of 1:1.