ZIP-002 Overview
ZIP-002 is a proposal that aims to decrease the execution delay to enhance user experience and operational efficiency, leveraging the recently established Security Council for rapid response in emergency situations.
View the ZIP-002 forum post HERE.
View the ZIP-002 proposal HERE.
ZIP-002 relies on the Security Council responding to an incident (in particular, any emergency incident) within a time frame of less than 3 hours.
Soft Freeze Test Run
The Security Council conducted a Sepolia test-run on Monday, 2 December, simulating an emergency response scenario. Below are the outcomes of the test-run, which aim to provide additional context to Delegates voting on ZIP-002.
The most critical outcome of any emergency scenario is the Security Council’s ability to collect three signatures in order to execute a Soft Freeze.
Test-Run Objectives
The overarching objective of the Soft Freeze test-run is to initiate an emergency incident notification and confirm that the Security Council is able to initiate and meet the threshold for a Soft Freeze within a 3-hour time frame.
- NOTIFICATION — Trigger an emergency notification for all Security Council members.
- ACKNOWLEDGE NOTIFICATION — Security Council members acknowledge the notification. Target response timelines:
- 4 members respond within 15 minutes.
- 4 additional members respond within 60 minutes.
- Final 4 members respond within 9 hours.
- CONFIRM IN CHAT — Security Council members confirm their presence in the group chat after acknowledging the notification.
- JOIN WAR ROOM CALL — Security Council members join a war room call to coordinate necessary actions.
- INITIATE & SIGN SOFT FREEZE — The Security Council initiates a Soft Freeze and collects a minimum of 3 signatures to proceed.
Test-Run Outcomes
- NOTIFICATION — A member of the Security Council successfully triggered an emergency notification. The test-run notification was initiated by Matter Labs.
- ACKNOWLEDGE NOTIFICATION — Security Council members exceeded expectations for acknowledging the emergency notification:
- Of the 9 teams*, 8 teams acknowledged the notification within 2 minutes of receiving the email/SMS/app notification.
*Note: The 4 individual members of the Security Council are grouped as a single team.
- Of the 9 teams*, 8 teams acknowledged the notification within 2 minutes of receiving the email/SMS/app notification.
- CONFIRM IN CHAT — Of the 12 Security Council members:
- 5 members confirmed their presence within 2 minutes of receiving the notification.
- Within 30 minutes, 10 members had communicated their presence.
- JOIN WAR ROOM CALL — 7 Security Council members joined the war room call within 20 minutes of the notification being sent.
- INITIATE & SIGN SOFT FREEZE — A Soft Freeze was initiated, and 5 signatures were collected within 25 minutes.
Objectives and Outcomes Summary
| Objective | Target | Outcome |
|---|---|---|
| NOTIFICATION | Trigger emergency notification for all members | Notification successfully triggered by Matter Labs. |
| ACKNOWLEDGE NOTIFICATION | 4 members respond within 15 minutes, 4 more within 60 minutes, final 4 within 9 hours | 8 out of 9 teams acknowledged within 2 minutes of receiving email/SMS/app notifications. |
| CONFIRM IN CHAT | Members confirm presence in group chat | 10 members in total confirmed within 30 minutes — 5 of those confirmed within 2 minutes. |
| JOIN WAR ROOM CALL | Members join war room call to coordinate actions | 7 members joined the war room call within 20 minutes. |
| INITIATE & SIGN SOFT FREEZE | Collect a minimum of 3 signatures for Soft Freeze | 5 signatures collected within 25 minutes. |
Overall, the test-run was a success. The Security Council’s response time exceeded expectations set in legal agreements between members and the Security Council Foundation. The Security Council initiated a Soft Freeze and was able to meet the threshold to execute a Soft Freeze within 30 minutes of the emergency notification being triggered.
For more information on the Security Council, view the relevant schedule in the Governance Procedures HERE.
Next Steps
This test-run marks a promising starting point for the ZKsync Security Council, showcasing strong emergency response capabilities. There are still opportunities to enhance the Council’s resilience and preparedness.
Monitoring and Notification
A key priority moving forward is decentralizing the monitoring and notification infrastructure to reduce single points of failure.
Signing and Verification
The Security Council experienced difficulty with signatures being displayed in the GovAuth web app due to a known issue with the interaction between Wallet Connect, SAFE, and the GovAuth web app. This experience highlighted the need to prioritize the development of alternative signing and verification tools to ensure multiple alternate solutions alongside the GovAuth web app.
Updates on the decentralization timeline will be shared in the Security Council forum category in the coming weeks, ensuring ongoing transparency and progress.