[GAP-4] Adjust GovOpsGovernor Parameters for GAPs

Governance Operations Active GAPs
1

[GAP-4] Adjust GovOpsGovernor Parameters for GAPs

:ballot_box: This proposal passed with a majority of ~920M ZK in-favor of the proposal. See final results here.

Field Details
Title [GAP-4] Adjust GovOpsGovernor Parameters for Governance Advisory Proposals (GAPs)
Proposal Type GAP
One Sentence Summary This proposal reduces the vote delay and vote extension periods for Governance Advisory Proposals (GAPs) to improve the efficiency of the ZKsync governance process.
Proposal Author ScopeLift
Proposal Sponsor ScopeLift
Date Created 6-November-2025
Version v1
Summary of Action Reduce the vote delay for GAPs from 7 days to 3 days, and the late quorum vote extension from 7 days to 2 days.

Abstract

This proposal updates the GovOpsGovernor parameters governing Governance Advisory Proposals (GAPs), reducing both the VotingDelay period and the LateQuorumVoteExtension window. These changes bring GAP governance in line with the streamlined parameters already adopted for ZIPs and proposed for TPPs.

Motivation

Over the past year, the Token Assembly have demonstrated consistent engagement, timely voting behavior, and improved operational reliability. The current 7-day delay between proposal creation and voting start has often proven excessive, slowing the governance process without meaningfully increasing participation or review quality.

In May 2025, the Token Assembly approved ZIP-5 to reduce the vote delay period and late quorum extension period for ZIPs. This change streamlined the ZIP proposal lifecycle. The changes to ZIP governance parameters have been positive, and it is expected that updating GAP parameters will have a similar outcome.

By reducing the vote delay and vote extension periods for GAPs:

  • Proposals can progress to the active voting stage sooner
  • Extensions due to late quorum achievement are limited to a manageable 2 days
  • Governance becomes more agile while maintaining the safeguards provided by the Guardian veto mechanism on both GAPs.

These changes reflect a governance system transitioning from cautious bootstrapping to operational maturity.

Specification

GovOpsGovernor Parameter Changes (for GAPs)

Parameter Current Proposed Description
votingDelay 7 days 3 days Time between GAP creation and voting start
lateQuorumVoteExtension 7 days 2 days Extra time added if quorum is reached late in the voting period

These changes will be executed via parameter update functions on the GovOpsGovernor contract responsible for GAPs.

No redeployment of contracts is required.

Rationale

Shorter delays increase responsiveness while retaining security and review safeguards. GAPs often concern procedural or governance coordination matters, for which agility is especially valuable.

Backwards Compatibility

Fully backwards compatible.

No changes to proposal logic, thresholds, or Guardian authority.

Security Considerations

The same security mechanisms remain in place: Guardian oversight and transparent on-chain proposal tracking. No new risks are introduced.

Links

2

:zap:GAP-4 Submitted Onchain

[GAP-4] Adjust GovOpsGovernor Parameters for GAPs has been submitted onchain. Voting for GAP-4 will open on Monday, November 17th at 〜20:30 UTC.

:link: Onchain proposal: ZKsync | [GAP-4] Adjust GovOpsGovernor Parameters for GAPs

3

The following reflects the views of L2BEAT’s governance team, composed of @kaereste and @Manugotsuka, and is based on their combined research, fact-checking, and ideation.

We voted FOR.

Our research team reviewed the parameter adjustments and found them fully consistent with the improvements already made to ZIPs and recently proposed for TPPs. GAPs often deal with process and coordination rather than protocol-level risk, so faster turnaround times are especially useful here.

Since the change is backward-compatible, introduces no new attack surface, and simply brings GAPs in line with the broader governance cadence, we view it as a practical and low-risk step toward a more efficient system.