- This lasted several hours
- Transaction packets were not posted to Ethereum during this time
- The bug was in the sequencer, which did not finalize the transfers
- The bug was quickly fixed and the network was back to normal
On June 7, Arbitrum suspended operations for several hours. The failure was caused by an error in the sequencer, which led to an overload. The bug was fixed quickly.
“The sequencer is responsible for receiving user transactions, creating a package, and placing it in the chain.. As soon as this happens, a request for its execution is received. At that time, the sequencer continues to collect offchain transactions,” Arbitrum explained.
It appears that the error was in the mechanism for placing the onchain package. When the sequencer tried to publish it to the network, there was an error and the transaction failed.
That is, the sequencer didn’t finalize transactions for a while, but it performed other functions properly. The bug was quickly fixed, and the problem was solved.
Also the Arbitrum team denied that the failure was caused by a lack of funds in the sequencer. Analysis of the event shows the funds were being sent correctly, but the packet was never posted on the Ethereum network.
The failure lasted several hours. The administration claims that all transactions have been completed successfully and the sequencer continues to work as usual. The ARB exchange rate was not affected.
We remind you that earlier we reported that USDC would start working in the Arbitrum network. In the near future, all users will be able to exchange the “bridge” token for regular Stablecoin at a rate of 1:1.