2024-03-25
The issue with Polygon's zkEVM Mainnet Beta over the weekend. The problem was caused by an L1 reorganization and resulted in the zkEVM going down for nearly 10 hours.
However, it's important to note that this issue was specific to zkEVM and did not affect Polygon's PoS or CDK.
The Emergency Council for Polygon zkEVM Mainnet Beta implemented an emergency fix to address the problem, and the zkEVM has now resumed operations.
The emergency state was activated to allow the necessary adjustments to be made by the Polygon zkEVM Core Team to resolve the system issues affecting L1 settlement.
The emergency state has been deactivated after the completion of the upgrade.
However, any future updates to the system will be subject to a 10-day timelock before implementation, ensuring that changes are carefully considered.
To provide transparency and insight into the recent events, the Polygon team plans to release a detailed post-mortem analysis on the @0xPolygonFdn forum early next week.
Oxpolygon Tweet on Twitter (X)
This analysis will inform stakeholders about the operational status of the Polygon zkEVM Mainnet Beta and future developments.
Polygon developer Jarrod Watts highlighted the significance of this incident in the context of Layer 2 (L2) upgradeability.
He emphasized that L2 upgradeability is crucial for supporting future improvements on L1, fixing bugs, and addressing vulnerabilities. While L2 upgradeability has its risks, it is essential for ongoing development and innovation.
Watts also acknowledged the concern about potential malicious upgrades in the current state of L2 networks.
He recognized that some argue L2 networks are more centralized compared to certain L1 networks.
