[ZIP-15] Update ZKsync Security Council Parameters

Abstract

ZIP-XX proposes a reduction in the ZKsync Security Council (ZKSC) from 12 to 8 signers, along with updating all relevant Security Council parameters to reflect the new council size. This change aligns the Security Council’s structure and operating requirements with the current stage of protocol development for ZKsync, while also reflecting a growing focus on the development of Prividium.

Existing signing threshold percentages are preserved, with the exception of the Soft Freeze threshold which remains fixed at 3 signers. Monthly compensation for members will be set at $3,000 USD per member, effective 1 May 2026.

Motivation

The ZKsync Security Council provides an independent technical check on protocol upgrades, adding a critical layer of decentralisation that ensures no single entity or governance body can unilaterally push changes to the ZKsync protocol. This proposal does not question the importance of having a Security Council. The ZKSC is a necessary and valuable element of the ZKsync protocol upgrade system and should remain in place.

This proposal reflects a shift in ZKsync's phase of development and aligns the Security Council's structure and compensation to match the security model the current phase requires.

1. From Protocol Development to Product Development

ZKsync has been in an active phase of protocol development, characterised by frequent upgrades to ZKsync Era and the infrastructure underpinning it. This phase demanded a large, well-resourced Security Council capable of reviewing and approving a high volume of protocol changes.

In 2025, eleven ZIPs were proposed and executed:

The execution of these ZIPs reflects a protocol that has reached a level of maturity after an intensive development cycle. An impressive amount of foundational work on the core protocol was shipped in 2025. ZKsync will continue to evolve through ZIPs as needed, but the pace of change is different from the one that shaped the current Security Council structure.

The Security Council no longer needs to be sized and compensated for the demands of a protocol development cycle for launch. The ZKSC should adapt to meet the oversight requirements of a permissioned, enterprise-grade network.

2. An Enterprise-Focused Strategy Requires a Different Council Composition

The shift to focusing on Prividium also impacts the membership of the ZKsync Security Council. Matter Labs has advised that potential Prividium customers, particularly banks, have expressed a preference for Security Council members to be entities rather than individuals. As ZKsync's security model evolves to serve institutional counterparties, the composition of the Security Council should reflect that.

This proposal removes the four individual signers from the ZKSC, retaining the eight entity-based members. This is not a reflection on the contributions of departing members, but an alignment of the Security Council's composition with the direction of ZKsync.

3. Sizing for Stage 1 Minimum Requirements

L2Beat's Stage 1 framework sets a minimum threshold for Security Council structure: at least 8 members, with signing thresholds of at least 75% for emergency upgrades. The existing threshold parameters of the ZKsync Security Council already meet those requirements. This proposal reduces the total number of signers from 12 to 8, positioning the ZKSC for long-term sustainability and full alignment with Stage 1 requirements.

All threshold percentages are preserved proportionally with one intentional exception: the RECOMMENDED_SOFT_FREEZE_THRESHOLD remains at 3 absolute signers, reflecting the view that this action should require a minimum number of members to engage regardless of council size.

4. Compensation Aligned to the New Security Model

This proposal recommends reducing monthly compensation to $3,000 USD per member, reflecting the scope of the role under the new security model and the treasury's current position. All entities will remain on a 6-hour SLA.

Specification

Changes Proposed

The proposed changes are detailed on Github and will be executed if this proposal is approved:

ZKSC Members

Governance Procedures

If this proposal is approved, the following sections of the ZKsync Governance Procedures will be updated to reflect the changes executed onchain:

• Schedule 1: Standard Governance Procedures
• Schedule 2: Emergency Response Procedures
• Schedule 3: ZKsync Security Council