Abstract

This GAP is a supplementary proposal to ZIP-19, which removes the ZKsync Guardians from their governance roles and requests the dissolution of the Guardians entity. The ZIP sets out the full motivation and specification. This GAP carries the onchain change needed on the GovOps Governor. It moves the Onchain Veto over GAPs from the Guardians to the ZKsync Foundation.

Approval of this GAP constitutes the GovOps Governor Approval required under Article 5.1.1 of the ZKsync Guardians Bylaws for the dissolution of the ZKsync Guardians entity. It formally requests that the Guardians’ Board of Directors resolve to dissolve the entity following the execution of ZIP-19, TPP-20 and this GAP.

Motivation

The ZkGovOpsGovernor stores its veto guardian as an immutable value set at deployment. It cannot be changed in place. The only way to move the veto seat is to deploy a new governor with the new veto guardian and transfer control of the existing GovOps Timelock to it.

The new governor is a copy of the current one in every other respect. It uses the same ZK token, the same GovOps Timelock, the same voting delay (3 days), voting period (7 days), proposal threshold (21,000,000 ZK), quorum (630,000,000 ZK) and late quorum vote extension (2 days). Only the veto guardian changes, to the ZKsync Foundation Safe on ZKsync Era.

Specification

If approved, this GAP executes six calls on the GovOps Timelock (0xC9E442574958f96C026DeF9a50C3236cab17428a). It first grants the proposer, canceller and executor roles to the new ZkGovOpsGovernor (0xB99860AD8B1de3376d8b4c5f4D52Efa46e413A8c). It then revokes the same three roles from the current ZkGovOpsGovernor (0xEEEa739a8b6fB1b8f703E23C9Be03CeeA643b160). Grants come before revokes, so the timelock is never left without a governor holding these roles.

After execution, all new GAPs are submitted to the new ZkGovOpsGovernor. Its veto guardian is the ZKsync Foundation Safe on ZKsync Era (0xF197677d63BF6E2841F5108b8dFd2FD6eCEff74B). The GovOps Timelock and the assets it holds are unchanged. The current ZkGovOpsGovernor will no longer be able to queue, execute or cancel proposals.

The new ZkGovOpsGovernor is source-verified on ZKsync Era and its bytecode hash is recorded in the zk-governance repository. Before execution, the ZKsync Foundation will confirm that the GovOps Timelock holds no pending operations and that the new governor has no pending, active or succeeded proposals.