The zkSync Era second-layer solution stopped processing blocks on December 25 due to an error in calculating state updates, the developers reported.
On December 25 at 05:50 UTC, zkSync Era encountered an issue triggered by one of the network's automated safety procedures.
The issue is completely resolved, but we want to share details with the community about what happened, and what teams did to address it.
TL;DR
•There… pic.twitter.com/hO9TKlfBMQ— zkSync Developers (∎, ∆) (@zkSyncDevs) December 25, 2023
Data is processed both on the protocol side and on the node side. There was a small bug in the latter’s software, the team explained. As a result of the discrepancy in calculations, security procedures were activated and the network went into the most secure mode.
After the error was eliminated, the sequencer began processing transactions again, starting with those that had accumulated in the mempool. The developers have released a software update for node operators.
Due to holidays, solving the problem took longer than during regular work, since most of the specialists were on vacation.
The team noted that it now considered the maximum protection mode that was activated to be redundant, but was unable to discuss canceling the procedure during the incident. The developers also plan to improve their online emergency response during the holidays in the new year.
User funds were safe during the outage, they emphasized.
In August, Polygon accused zkSync Era's main developer, Matter Labs, of stealing code for the Boojum update.
Source: Cryptocurrency
I am an experienced journalist and writer with a career in the news industry. My focus is on covering Top News stories for World Stock Market, where I provide comprehensive analysis and commentary on markets around the world. I have expertise in writing both long-form articles and shorter pieces that deliver timely, relevant updates to readers.
