Polygon zkEVM Beta Resumes After Emergency Fix

Polygon zkEVM Beta Resumes After Emergency Fix

Polygon zkEVM Beta Resumes After Emergency Fix

Polygon zkEVM Mainnet Beta faced a nearly 10 hour downtime over the weekend due to a sequencer issue which have been resolved.

Polygon’s zkEVM, currently in beta, did not function properly for close to ten hours throughout the previous weekend. The Polygon zkEVM Mainnet Beta experienced a sequencer issue due to organization.

However, this problem was exclusive to Polygon zkEVM and did not include Polygon PoS or CDK in its scope of influence.

Polygon zkEVM Resumes Operation After Emergency Fix

Following an emergency patch by the Emergency Council for Polygon zkEVM Mainnet Beta, the Polygon zkEVM Mainnet Beta has resumed its activities.

The Polygon zkEVM Core Team issued a state of emergency to allow necessary adjustments to address system difficulties impeding L1 settlement activities.

The system has removed the emergency state due to the completion of the upgrade. However, we will implement any future system improvements subject to a ten-day timelock.

The Polygon team released a statement announcing their intention to publish a comprehensive post-mortem study on the @0xPolygonFdn forum at the beginning of the following week.

Through the implementation of this effort, the goal is to provide transparency and insight into the recent events that have surrounded the Polygon zkEVM Mainnet Beta.

This will guarantee that stakeholders stay updated on the platform’s operational status and forthcoming advancements. During the weekend, Polygon developer Jarrod Watts talked about the recent incident that involved Polygon zkEVM.

He emphasized the significance of this occurrence in the discussion regarding the upgradeability of Layer 2 programming. According to the chain of events, there was a problem with zkEVM that caused block production to stop, which prompted the Security Council to activate the emergency state to speed up the process of upgrading.

The team implemented an upgrade to resolve the issue. The team deactivated the emergency state after the upgrade was complete, allowing the chain to resume its normal operations.

Watts strongly emphasized the significance of L2 upgradeability, pointing out that in the absence of this capability, L2s would be unable to support future enhancements on L1, provide bug fixes, or patch vulnerabilities.

Even though L2 upgradeability is not without flaws and is associated with dangers, he admitted that it is essential for the continuous development and innovation of the system.

In addition, Watts brought up the possibility of malicious upgrades, although they are uncommon, continuing to be a cause for concern in the current condition of L2 networks.

He agreed that the arguments that suggested that L2 networks are more centralized than some L1 networks were correct. 

Read Previous

HashKey Leads Hong Kong Spot ETF Custodianship

Read Next

Binance Ceases USDC Transactions on Tron Network