ZKsync Governance Feed

By ZKSync Governance • 11/30/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66631208
Timestamp: 11/30/2025, 3:55:35 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExecuted
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "59956436467786828609747327435664724459335730934530897411573906572229159062327"
}

CallScheduled - ZkGovOpsGovernor Timelock v2.0

By ZKSync Governance • 11/30/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66631208
Timestamp: 11/30/2025, 3:55:35 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallExecuted
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0xd7612e5c9c37b50e8665f692f8697ba23de648d359c1b9d68f0cd78f4f811451",
  "index": "0",
  "target": "0x8d03F20C213D435A8B50127DE3d5797845b2120D",
  "value": "0",
  "data": "0x2f2ff15d...88e6ba3d"
}

By ZKSync Governance • 11/28/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66606893
Timestamp: 11/28/2025, 3:01:36 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallScheduled
Contract Address:0xC9E4...428a0xC9E442574958f96C026DeF9a50C3236cab17428a

Event Data

{
  "id": "0x7254c290a383392a10eb4cf03ad563b289e31e9e0abb8da4a99aa207ccec9429",
  "index": "0",
  "target": "0xEEEa739a8b6fB1b8f703E23C9Be03CeeA643b160",
  "value": "0",
  "data": "0x70b0f660000000000000000000000000000000000000000000000000000000000003f480",
  "predecessor": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "delay": "259200"
}

By ZKSync Governance • 11/28/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66606886
Timestamp: 11/28/2025, 3:01:22 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallScheduled
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0x34b27ffb3f9c18b756daa021bbafc507eaa2a275383b32b0d7afb8a3e349992d",
  "index": "0",
  "target": "0xb83FF6501214ddF40C91C9565d095400f3F45746",
  "value": "0",
  "data": "0x70b0f660000000000000000000000000000000000000000000000000000000000003f480",
  "predecessor": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "delay": "259200"
}

ProposalExecuted - ZkProtocolGovernor

By ZKSync Governance • 11/25/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66544163
Timestamp: 11/25/2025, 12:33:40 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallScheduled
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0xd7612e5c9c37b50e8665f692f8697ba23de648d359c1b9d68f0cd78f4f811451",
  "index": "0",
  "target": "0x8d03F20C213D435A8B50127DE3d5797845b2120D",
  "value": "0",
  "data": "0x2f2ff15d...88e6ba3d",
  "predecessor": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "delay": "259200"
}

By ZKSync Governance • 11/21/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66452136
Timestamp: 11/21/2025, 3:48:47 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExecuted
Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
Proposal Link: View Proposal

Event Data

{
  "proposalId": "56697539346434504259886089137844919991955896472242107434527974192173343556352"
}

CallExecuted - ZkProtocolGovernor Timelock v2.0

By ZKSync Governance • 11/21/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66452136
Timestamp: 11/21/2025, 3:48:47 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallExecuted
Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714

Event Data

{
  "id": "0xe32d9aea3227385013512bde33d699116387e76bf350b6957ed3f28d21c0601d",
  "index": "0",
  "target": "0x0000000000000000000000000000000000008008",
  "value": "0",
  "data": "0x62f84b24...00000000"
}

ProposalExtended - ZkGovOpsGovernor v2.0

By ZKSync Governance • 11/21/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66447739
Timestamp: 11/21/2025, 1:12:56 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExtended
Contract Address:0xEEEa...b1600xEEEa739a8b6fB1b8f703E23C9Be03CeeA643b160
Proposal Link: View Proposal

Event Data

{
  "proposalId": "106273763076555939732473066377698909735843793351966221159383225521787704405222",
  "extendedDeadline": "1764335576"
}

CallScheduled - ZkProtocolGovernor Timelock v2.0

By ZKSync Governance • 11/21/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66447726
Timestamp: 11/21/2025, 1:11:46 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExtended
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "68452231205260788796569713423066878142593117468039270123415287058789227565934",
  "extendedDeadline": "1764335506"
}

By ZKSync Governance • 11/21/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66445186
Timestamp: 11/21/2025, 11:59:33 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallScheduled
Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714

Event Data

{
  "id": "0xe32d9aea3227385013512bde33d699116387e76bf350b6957ed3f28d21c0601d",
  "index": "0",
  "target": "0x0000000000000000000000000000000000008008",
  "value": "0",
  "data": "0x62f84b24...00000000",
  "predecessor": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "delay": "0"
}

ProposalExtended - ZkProtocolGovernor

By ZKSync Governance • 11/18/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66350218
Timestamp: 11/18/2025, 11:29:22 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExtended
Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
Proposal Link: View Proposal

Event Data

{
  "proposalId": "56697539346434504259886089137844919991955896472242107434527974192173343556352",
  "extendedDeadline": "1763724562"
}

ProposalCreated - ZkGovOpsGovernor v2.0

By ZKSync Governance • 11/18/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66343038
Timestamp: 11/18/2025, 5:22:27 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExtended
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "59956436467786828609747327435664724459335730934530897411573906572229159062327",
  "extendedDeadline": "1764048147"
}

By ZKSync Governance • 11/10/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66123336
Timestamp: 11/10/2025, 8:36:02 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalCreated
Contract Address:0xEEEa...b1600xEEEa739a8b6fB1b8f703E23C9Be03CeeA643b160
Proposal Link: View Proposal

Event Data

{
  "proposalId": "106273763076555939732473066377698909735843793351966221159383225521787704405222",
  "proposer": "0xdEdD9b3214d422d7EFe71465A0915e6D164f360d",
  "targets": [
    "0xEEEa739a8b6fB1b8f703E23C9Be03CeeA643b160",
    "0xEEEa739a8b6fB1b8f703E23C9Be03CeeA643b160"
  ],
  "values": [
    "0",
    "0"
  ],
  "signatures": [
    "",
    ""
  ],
  "calldatas": [
    "0x70b0f660000000000000000000000000000000000000000000000000000000000003f480",
    "0xd07f91e9000000000000000000000000000000000000000000000000000000000002a300"
  ],
  "voteStart": "1763411762",
  "voteEnd": "1764016562",
  "description": "# [GAP-4] Adjust GovOpsGovernor Parameters for GAPs\n| **Field**                | **Details**                                                                                                                                                          |\n| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Title**                | \\[GAP-4] Adjust GovOpsGovernor Parameters for Governance Advisory Proposals (GAPs)                                                                                   |\n| **Proposal Type**        | GAP                                                                                                                                                                  |\n| **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. |\n| **Proposal Author**      | ZKsync Foundation                                                                                                                                                    |\n| **Proposal Sponsor**     | ScopeLift                                                                                                                                                            |\n| **Date Created**         | 10-November-2025                                                                                                                                                     |\n| **Version**              | v1                                                                                                                                                                   |\n| **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.                                                      |\n\n## Abstract\n\nThis 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.\n\n## Motivation\n\nOver 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.\n\nIn May 2025, the Token Assembly approved [ZIP-5](https://www.tally.xyz/gov/zksync/proposal/32477831455745537024214395992964479454779258818502397012096084176779102554510?govId=eip155:324:0x76705327e682F2d96943280D99464Ab61219e34f) 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.\n\nBy reducing the vote delay and vote extension periods for GAPs:\n\n* Proposals can progress to the active voting stage sooner\n* Extensions due to late quorum achievement are limited to a manageable 2 days\n* Governance becomes more agile while maintaining the safeguards provided by the Guardian veto mechanism on both GAPs.\n\nThese changes reflect a governance system transitioning from cautious bootstrapping to operational maturity.\n\n## Specification\n\n### GovOpsGovernor Parameter Changes (for GAPs)\n\n| Parameter                 | Current | Proposed | Description                                                     |\n| ------------------------- | ------- | -------- | --------------------------------------------------------------- |\n| `votingDelay`             | 7 days  | 3 days   | Time between GAP creation and voting start                      |\n| `lateQuorumVoteExtension` | 7 days  | 2 days   | Extra time added if quorum is reached late in the voting period |\n\nThese changes will be executed via parameter update functions on the **GovOpsGovernor** contract responsible for GAPs.\n\nNo redeployment of contracts is required.\n\n## Rationale\n\nShorter delays increase responsiveness while retaining security and review safeguards. GAPs often concern procedural or governance coordination matters, for which agility is especially valuable.\n\n## Backwards Compatibility\n\nFully backwards compatible.\n\nNo changes to proposal logic, thresholds, or Guardian authority.\n\n## Security Considerations\n\nThe same security mechanisms remain in place: Guardian oversight and transparent on-chain proposal tracking. No new risks are introduced.\n\n## Links\n\n* Governance Contract References: [GitHub – Governance Parameters Documentation](https://github.com/matter-labs/zksync-governance)\n* Related Proposal: [ZIP-5: Upgrade Governance Contracts](https://github.com/matter-labs/zksync-governance/pull/21)"
}

ProposalCreated - ZkProtocolGovernor

By ZKSync Governance • 11/10/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66123218
Timestamp: 11/10/2025, 8:29:23 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalCreated
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "68452231205260788796569713423066878142593117468039270123415287058789227565934",
  "proposer": "0xdEdD9b3214d422d7EFe71465A0915e6D164f360d",
  "targets": [
    "0xb83FF6501214ddF40C91C9565d095400f3F45746",
    "0xb83FF6501214ddF40C91C9565d095400f3F45746"
  ],
  "values": [
    "0",
    "0"
  ],
  "signatures": [
    "",
    ""
  ],
  "calldatas": [
    "0x70b0f660000000000000000000000000000000000000000000000000000000000003f480",
    "0xd07f91e9000000000000000000000000000000000000000000000000000000000002a300"
  ],
  "voteStart": "1763411363",
  "voteEnd": "1764016163",
  "description": "# [TPP-14] Adjust TokenGovernor Parameters for TPPs\n| **Field**                | **Details**                                                                                                                                                    |\n| ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Title**                | \\[TPP-14] Adjust TokenGovernor Parameters for Token Program Proposals (TPPs)                                                                                   |\n| **Proposal Type**        | TPP                                                                                                                                                            |\n| **One Sentence Summary** | This proposal reduces the vote delay and vote extension periods for Token Program Proposals (TPPs) to improve the efficiency of the ZKsync governance process. |\n| **Proposal Author**      | ZKsync Foundation                                                                                                                                              |\n| **Proposal Sponsor**     | ScopeLift                                                                                                                                                      |\n| **Date Created**         | 10-November-2025                                                                                                                                               |\n| **Version**              | v1                                                                                                                                                             |\n| **Summary of Action**    | Reduce the vote delay for TPPs from 7 days to 3 days, and the late quorum vote extension from 7 days to 2 days.                                                |\n\n## Abstract\n\nThis proposal updates the **TokenGovernor** parameters governing Token Program Proposals (TPPs), reducing both the `VotingDelay` period and the `LateQuorumVoteExtension` window. These changes align TPP governance with the faster and more effective parameters successfully applied to ZIPs since May 2025.\n\n## Motivation\n\nOver 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.\n\nIn May 2025, the Token Assembly approved [ZIP-5](https://www.tally.xyz/gov/zksync/proposal/32477831455745537024214395992964479454779258818502397012096084176779102554510?govId=eip155:324:0x76705327e682F2d96943280D99464Ab61219e34f) 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 TPP parameters will have a similar outcome.\n\nBy reducing the vote delay and vote extension periods for TPPs:\n\n* Proposals can progress to the active voting stage sooner\n* Extensions due to late quorum achievement are limited to a manageable 2 days\n* Governance becomes more agile while maintaining the safeguards provided by the Guardian veto mechanism on both TPPs.\n\nThese changes reflect a governance system transitioning from cautious bootstrapping to operational maturity.\n\n## Specification\n\n### TokenGovernor Parameter Changes (for TPPs)\n\n| Parameter                 | Current | Proposed | Description                                                     |\n| ------------------------- | ------- | -------- | --------------------------------------------------------------- |\n| `votingDelay`             | 7 days  | 3 days   | Time between TPP creation and voting start                      |\n| `lateQuorumVoteExtension` | 7 days  | 2 days   | Extra time added if quorum is reached late in the voting period |\n\nThese changes will be executed through the standard parameter update functions on the **TokenGovernor** contract responsible for TPPs.\n\nNo redeployment of contracts is required.\n\n## Rationale\n\nThe reduced timing parameters increase agility while preserving fairness and oversight. A 3-day vote delay provides sufficient review time, and a 2-day extension balances quorum flexibility with timely execution.\n\n## Backwards Compatibility\n\nFully backwards compatible.\n\nExisting proposals and governance logic remain unaffected.\n\n## Security Considerations\n\nThe shortened timing window introduces no new security risk. Guardians retain veto authority during both the vote delay and voting periods, ensuring rapid but safe governance.\n\n## Links\n\n* Governance Contract References: [GitHub – Governance Parameters Documentation](https://github.com/matter-labs/zksync-governance)\n* Related Proposal: [ZIP-5: Upgrade Governance Contracts](https://github.com/matter-labs/zksync-governance/pull/21)"
}

By ZKSync Governance • 11/10/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 66118288
Timestamp: 11/10/2025, 3:59:07 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalCreated
Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
Proposal Link: View Proposal

Event Data

{
  "proposalId": "56697539346434504259886089137844919991955896472242107434527974192173343556352",
  "proposer": "0xdEdD9b3214d422d7EFe71465A0915e6D164f360d",
  "targets": [
    "0x0000000000000000000000000000000000008008"
  ],
  "values": [
    "0"
  ],
  "signatures": [
    ""
  ],
  "calldatas": [
    "0x62f84b2400000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000340000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000020000000000000000000000000303a465b659cbb0ab36ee643ea362c509eeb521300000000000000000000000000000000000000000000000000ca8132b0328000000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000001e4d52471c10000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000014400000000000000000000000000000000000000000000000000ca8132b0328000000000000000000000000000db1e46b448e68a5e35cb693a99d59f784ad115cc000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001200000000000000000000000000000000000000000000000000000000000989680000000000000000000000000000000000000000000000000000000000000032000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000f378708b88841abb63e2316e4fc8f29469bee885000000000000000000000000000000000000000000000000000000000000004499a88ec40000000000000000000000005a7d6b2f92c77fad6ccabd7ee0624e64907eaf3e0000000000000000000000004fcd824d304e9b1584cdbb582c104bdcbfb1127400000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000"
  ],
  "voteStart": "1763049547",
  "voteEnd": "1763654347",
  "description": "#  [ZIP-14] Upgrade ZK Token with Permissionless Burn Function\n# \\[ZIP-14] Upgrade ZK Token with Permissionless Burn Function\n\n| **Proposal Title**        | Upgrade ZK Token with Permissionless Burn Function                                                                                                            |\n| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Proposal Type**         | ZIP                                                                                                                                                           |\n| **One Sentence Summary:** | ZIP-14 proposes upgrading the ZK Token contract to ZKTokenV3, introducing token burn mechanisms to support protocol-aligned supply management under ZKnomics. |\n| **Proposal Author**       | ZKsync Foundation                                                                                                                                             |\n| **Proposal Sponsor:**     | ScopeLift                                                                                                                                                     |\n| **Date Created:**         | 2025-11-7                                                                                                                                                     |\n| **Version**               | v1                                                                                                                                                            |\n| **Summary of Action**     | Upgrade ZK Token to ZKTokenV3, adding public and role-gated burn functionality.                                                                               |\n| **Link to contracts**     | [ZKTokenV3.sol (GitHub)](https://github.com/ScopeLift/zk-governance/blob/5c18bd1c7d18f17390bc6e2fc6e5d2167a326b30/l2-contracts/src/ZkTokenV3.sol)             |\n| **Link to forum**         | [ZKsync forum post](https://forum.zknation.io/t/zip-14-upgrade-zk-token-with-permissionless-burn-function/771)                                                |\n\n## Abstract\n\nZIP-14 proposes the upgrade of the [ZK token contract](https://explorer.zksync.io/address/0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E) to ZKTokenV3, a minimal extension of [ZKTokenV2](https://github.com/zksync-association/zk-governance/blob/master/l2-contracts/src/ZkTokenV2.sol) that introduces two burn functions and a public max supply function:\n\n1. **Public burn** – any token holder may permanently destroy their own tokens.\n2. **Role-gated burnFrom** – addresses with the `BURNER_ROLE` can burn tokens from designated accounts.\n3. **Public max supply** – allows any program to read the max supply of 21 billion ZK on the contract and the max supply is now enforced when minting new tokens.\n\nThis upgrade lays the foundation for the [**ZKnomics**](https://forum.zknation.io/t/zknomics-roadmap-vision/712) vision by enabling supply management through programmable token burning.\n\n## Motivation\n\nThe [ZKnomics framework](https://forum.zknation.io/t/zknomics-roadmap-vision/712) proposes usage-driven revenue distribution via two mechanisms: protocol staking and token burning. Token burn functionality is a prerequisite for implementing supply management and usage-based fee distribution at the protocol layer.\n\nThis proposal is the second step of the ZKnomics roadmap:\n\n1. [Enable permissionless staking (TPP)](https://forum.zknation.io/t/tpp-draft-zknomics-token-staking/766)\n2. Upgrade token with burn mechanism (this ZIP)\n3. Activate sequencer and interop fee switches (ZIP)\n4. Finalize programatic rules via governance proposal (ZIP)\n\nBy enabling burn functionality, the protocol establishes the supply-side mechanism necessary for usage-driven revenue distribution and long-term alignment between network activity and token value.\n\nThe upgrade delivers two benefits:\n\n* **Security & Recovery**: Token holders, and any other smart-contract, can permissionlessly burn unused minted tokens and return compromised funds to the Token Assembly unminted ZK token supply.\n* **Forward Compatibility**: Burn functions open up the design space for protocol fee switch designs (e.g. sequencer and interop fees).\n\nThis aligns the token with long-term protocol sustainability, while introducing minimal surface area of change.\n\n## Specification\n\nThe ZKTokenV3 contract extends `ZKTokenV2` with two functions:\n\n* `burn(uint256 amount)`: allows any account to burn their own tokens.\n* `burnFrom(address account, uint256 amount)`: allows addresses with the `BURNER_ROLE` to burn tokens from another account.\n\nBurning tokens decreases the ZK token’s `totalSupply` , which denotes the total minted supply.\n\nThis upgrade also introduces an onchain parameter `maxSupply` which is set at ZK’s maximum mintable supply of 21 billion. While token burns do not affect this value, ZKsync Governance can pass a protocol upgrade to adjust this value.\n\n## Rationale\n\n**Public burn**\n\n* Provides token holders autonomy in burning tokens.\n* Enables voluntary supply reduction, supporting deflationary tokenomics if ZKsync Governance activates such a mechanism in the future.\n\n**Role-gated burnFrom**\n\n* Currently, the BURNER\\_ROLE is unassigned and can only be assigned via a proposal from the Protocol Governor.\n* Allows the protocol to align token supply with fee-based burn mechanisms in the future.\n\nThis dual design balances **user empowerment** with **governance-controlled flexibility**, while maintaining minimal code complexity.\n\n## Implementation & Backwards Compatibility\n\n* ZKTokenV3 is a direct extension of ZKTokenV2, with only 19 SLOC added.\n* Existing balances and permissions remain unaffected.\n* The previous `burn` function still exists on the implementation and has the same functionality of `burnFrom`\n* All tooling compatible with ERC20 remains functional.\n\n## Breaking Changes\n\n* No breaking changes for standard ERC20 usage.\n\n## Security Considerations\n\n* **Irreversibility**: Burned tokens are not recoverable by the burner, they must be minted via ZKsync Governance.\n\n## Audit Summary\n\n**Auditor**: Richie Humphrey (Offbeat Security)\n**Date**: July 11, 2025\n**Link**: [Audit Report (HackMD)](https://hackmd.io/@offbeatsecurity/zksync-zktokenv3-07-14-2025)"
}

By ZKSync Governance • 11/6/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65988283
Timestamp: 11/6/2025, 7:57:09 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExecuted
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "97314764080859415498674952864578860560861880297360481348949362100730414449748"
}

By ZKSync Governance • 11/6/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65988283
Timestamp: 11/6/2025, 7:57:09 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallExecuted
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0x5a9d7dda18c8ef82d9711cc3a1b2bf91da5e97d6f032c7d03daaefaad6b9d042",
  "index": "0",
  "target": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
  "value": "0",
  "data": "0x2f2ff15d...83b6306b"
}

By ZKSync Governance • 11/5/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65911308
Timestamp: 11/5/2025, 9:55:17 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalCreated
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "59956436467786828609747327435664724459335730934530897411573906572229159062327",
  "proposer": "0x1f76a6Bf03429480472B3695E08689219cE15ED6",
  "targets": [
    "0x8d03F20C213D435A8B50127DE3d5797845b2120D"
  ],
  "values": [
    "0"
  ],
  "signatures": [
    ""
  ],
  "calldatas": [
    "0x2f2ff15d9f2df0fed2c77648de5860a4cc508cd0818c85b8b8a1ab4ceeef8d981c8956a60000000000000000000000009e43647ef21194d6b4b29673dadeec2688e6ba3d"
  ],
  "voteStart": "1762941317",
  "voteEnd": "1763546117",
  "description": "# [TPP-13] Assign Minter Role to Gov Infra Capped Minter\n## **[TPP-13] Assign Minter Role to Gov Infra Capped Minter**\n\n| Title | Proposal Title |\n| --- | --- |\n| **Proposal Type** | TPP |\n| **One Sentence Summary** | Assign minter role from the Rate Limiter Mod to the `Zk_Governance_Operations_2025` child capped minter, as outlined in TPP-11. |\n| **Proposal Author** | ZKsync Association |\n| **Proposal Sponsor** | Polar |\n| **Submitted onchain** | 2025-11-05 |\n| **Version** | V1.0 |\n| **Calldata Summary** | Assign minter role from the Rate Limiter Mod to the `Zk_Governance_Operations_2025` child capped minter, as outlined in TPP-11. |\n| **Link to forum post** | https://forum.zknation.io/t/tpp-14-assign-minter-role-to-gov-infra-capped-minter/823 |\n| **Link to contracts** | `Zk_Governance_RateLimit_2025`: [0x8d03F20C213D435A8B50127DE3d5797845b2120D](https://explorer.zksync.io/address/0x8d03F20C213D435A8B50127DE3d5797845b2120D) `Zk_Governance_Operations_2025`: [0x9e43647EF21194d6b4b29673DadeEC2688e6BA3D](https://explorer.zksync.io/address/0x9e43647EF21194d6b4b29673DadeEC2688e6BA3D) |\n\n### Summary\n\nThis proposal assigns the `Zk_Governance_Operations_2025` (Child Capped Minter) the **minter role** from the `Zk_Governance_RateLimit_2025` (Rate Limit Modifier). This call is required to  activate [[TPP-11] ZKsync Governance System Infrastructure Funding](https://vote.zknation.io/dao/proposal/8043865517871673466500920771587039178855876090726876272793935297016439640908?govId=eip155:324:0xb83FF6501214ddF40C91C9565d095400f3F45746).\n\n### Background\n\nDuring post-execution verification of TPP-11, the Governance Team identified that the `Zk_Governance_Operations_2025` capped minter contract was not granted the minter role from TPP-11’s Rate Limiter, which is controlled by the ZK Token Governor timelock. As a result, tokens are currently unable to be minted from the `Zk_Governance_Operations_2025` capped minter.\n\n### Motivation\n\nThe Governance Infra System Funding program was approved in [TPP-11](https://www.tally.xyz/gov/zksync/proposal/8043865517871673466500920771587039178855876090726876272793935297016439640908?govId=eip155:324:0xb83FF6501214ddF40C91C9565d095400f3F45746) by the Token Assembly. There are no changes to the approved program design, motive or mechanic.\n\n### Program Mechanics\n\nThis proposal assigns minting rights from the `Zk_Governance_RateLimit_2025` Rate Limiter mod to the `Zk_Governance_Operations_2025` child capped minter, as outlined in TPP-11.\n\n\n![Screenshot 2025-11-04 at 17.35.57](https://hackmd.io/_uploads/B1mtjjwJWg.png)\n\n\n\n|**Capped Minter**|Smart-Contract Address|**Smart-Contract Admin Role**|**Smart-Contract Minter Role**|**Smart-Contract Pauser Role**|**Minting Start**|**Minting End**|**Token Configuration Parameters**|\n| --- | --- | --- | --- | --- | --- | --- | --- |\n|`Zk_Governance_RateLimit_2025` (Rate Limit Modifier)|[0x8d03F20C213D435A8B50127DE3d5797845b2120D](https://explorer.zksync.io/address/0x8d03F20C213D435A8B50127DE3d5797845b2120D)|Token Governor Timelock|`Zk_Governance_Operations_2025`|Security Council via Parent Capped Minter|n/a|n/a|Rate Limit: **8M ZK per month**|\n|`Zk_Governance_Operations_2025` (Child Capped Minter)|[0x9e43647EF21194d6b4b29673DadeEC2688e6BA3D](https://explorer.zksync.io/address/0x9e43647EF21194d6b4b29673DadeEC2688e6BA3D)|ZKsync Association Governance Team 4/7 Multisig ([0x6162BEfaaf5C2598dD92087A5a479b10b135275a](https://app.safe.global/settings/setup?safe=zksync:0x6162BEfaaf5C2598dD92087A5a479b10b135275a))|Child Capped Minters for Service Providers|Security Council via Parent Capped Minter|October 3, 2025|December 31, 2026|Cap: **33,000,000 ZK**|\n\n\n**Calldata to be executed:**\n- Grant minter role from `Zk_Governance_RateLimit_2025` to `Zk_Governance_Operations_2025`"
}

By ZKSync Governance • 11/3/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65832787
Timestamp: 11/3/2025, 9:28:13 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExecuted
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "8043865517871673466500920771587039178855876090726876272793935297016439640908"
}

By ZKSync Governance • 11/3/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65832787
Timestamp: 11/3/2025, 9:28:13 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallExecuted
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0x981b4be2134566429ea5e5706177f1262f4b30bf9c391c59956f1c7788a442c6",
  "index": "0",
  "target": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
  "value": "0",
  "data": "0x2f2ff15d...189939a1"
}

By ZKSync Governance • 11/3/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65823271
Timestamp: 11/3/2025, 5:03:21 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallScheduled
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0x5a9d7dda18c8ef82d9711cc3a1b2bf91da5e97d6f032c7d03daaefaad6b9d042",
  "index": "0",
  "target": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
  "value": "0",
  "data": "0x2f2ff15d...83b6306b",
  "predecessor": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "delay": "259200"
}

By ZKSync Governance • 10/31/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65697884
Timestamp: 10/31/2025, 7:31:17 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallScheduled
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0x981b4be2134566429ea5e5706177f1262f4b30bf9c391c59956f1c7788a442c6",
  "index": "0",
  "target": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
  "value": "0",
  "data": "0x2f2ff15d...189939a1",
  "predecessor": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "delay": "259200"
}

By ZKSync Governance • 10/27/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65501996
Timestamp: 10/27/2025, 4:57:37 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExtended
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "97314764080859415498674952864578860560861880297360481348949362100730414449748",
  "extendedDeadline": "1762189057"
}

By ZKSync Governance • 10/24/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65445391
Timestamp: 10/24/2025, 7:26:40 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExtended
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "8043865517871673466500920771587039178855876090726876272793935297016439640908",
  "extendedDeadline": "1761938800"
}

UpgradeApprovedBySecurityCouncil - Protocol Upgrade Handler v2.0

By Ethereum Governance • 10/16/2025

Event Details

Network: Ethereum Mainnet
Chain ID: 1
Block: 23589343
Timestamp: 10/16/2025, 9:30:11 AM

Governance Info

Governance Body: Ethereum Governance
Event Type: UpgradeExecuted
Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3

Event Data

{
  "_id": "0x2d891fb5e539de72ae9ea8cbec41aa1b2bd49e77afb1cfcbdee95432216c1122"
}

By Ethereum Governance • 10/15/2025

Event Details

Network: Ethereum Mainnet
Chain ID: 1
Block: 23582174
Timestamp: 10/15/2025, 9:23:47 AM

Governance Info

Governance Body: Ethereum Governance
Event Type: UpgradeApprovedBySecurityCouncil
Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3

Event Data

{
  "_id": "0x2d891fb5e539de72ae9ea8cbec41aa1b2bd49e77afb1cfcbdee95432216c1122"
}

By Ethereum Governance • 10/15/2025

Event Details

Network: Ethereum Mainnet
Chain ID: 1
Block: 23582112
Timestamp: 10/15/2025, 9:11:11 AM

Governance Info

Governance Body: Ethereum Governance
Event Type: UpgradeExecuted
Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3

Event Data

{
  "_id": "0x797ed4fb2a525632d25f0128840e8f684188c823fec6e0037410465d197610f9"
}

By Ethereum Governance • 10/15/2025

Event Details

Network: Ethereum Mainnet
Chain ID: 1
Block: 23582102
Timestamp: 10/15/2025, 9:09:11 AM

Governance Info

Governance Body: Ethereum Governance
Event Type: UpgradeExecuted
Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3

Event Data

{
  "_id": "0x5451e3aa34aba5b9bd71b567e38be4d075915705d110a37a2d851945be2c4d43"
}

By ZKSync Governance • 10/15/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65267311
Timestamp: 10/15/2025, 8:50:16 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalCreated
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "97314764080859415498674952864578860560861880297360481348949362100730414449748",
  "proposer": "0xE8D848debB3A3e12AA815b15900c8E020B863F31",
  "targets": [
    "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
    "0xb1c5f8ea8cE447FDaFB234D85EAD8c8A83b6306B",
    "0xb1c5f8ea8cE447FDaFB234D85EAD8c8A83b6306B"
  ],
  "values": [
    "0",
    "0",
    "0"
  ],
  "signatures": [
    "",
    "",
    ""
  ],
  "calldatas": [
    "0x2f2ff15d9f2df0fed2c77648de5860a4cc508cd0818c85b8b8a1ab4ceeef8d981c8956a6000000000000000000000000b1c5f8ea8ce447fdafb234d85ead8c8a83b6306b",
    "0x2f2ff15d9f2df0fed2c77648de5860a4cc508cd0818c85b8b8a1ab4ceeef8d981c8956a60000000000000000000000008076e2d38e47f5f8c755633022dc9b75e5039529",
    "0x2f2ff15d65d7a28e3265b37a6474929f336521b332c1681b933f6cb9f3376673440d862a000000000000000000000000ffb6126ff8401665081b771bb11ccd0e09f95d5a"
  ],
  "voteStart": "1761123016",
  "voteEnd": "1761727816",
  "description": "# [TPP-12] ZKnomics Token Staking\n# [TPP-12] ZKnomics Token Staking\n\n| Title | ZKnomics Token Staking |\n| --- | --- |\n| **Proposal Type** | TPP |\n| **One Sentence Summary** | This proposal activates a capped minter with 37.5M ZK (~$1.9M USD at $0.05/ZK) to trial ZK token staking rewards over 6 months with up to 10% reward rate for participation in the pilot. |\n| **Proposal Author** | Dennison (Tally) |\n| **Proposal Sponsor** | Dennison (Tally) |\n| Date | 2025-10-15 |\n| **Version** | v1 |\n| **Summary of Action** | Activate a ZK Token staking program in support of ZKnomics vision using Tally's Staker contract, fund it autonomously over 2 seasons (6 months total) with two capped minters of 10M ZK and 25M ZK respectively. Staking is forward compatible with ZKsync decentralized sequencing. |\n| **Link to forum post** | https://forum.zknation.io/t/tpp-draft-zknomics-token-staking/766 |\n| **Link to contracts** | Repo: https://github.com/withtally/staker <br> ZKStaker: [0x8373A5dFb76bD6Bb93d89024d5B48438dCb0181E](https://explorer.zksync.io/address/0x8373A5dFb76bD6Bb93d89024d5B48438dCb0181E#contract#contract-info) |\n\n## Simple Summary\n\nThis proposal activates a capped minter with 37.5M ZK (~$1.9M USD) to pilot ZK token staking rewards over 6 months with up to 10% return for pilot participants. Rewards are distributed autonomously upon the funding of staking contracts. Reward eligibility is limited to tokenholders delegating to active Delegates, those that have voted a minimum of 2 out of last 5 votes.\n\n## Motivation\n\nIn alignment with the [ZKnomics vision published in June 2025](https://forum.zknation.io/t/zknomics-roadmap-vision/712), this proposal trials ZK Token Staking infrastructure by deploying Tally’s audited [Staker contract system](https://github.com/withtally/staker).\n\nAs mentioned in the ZKnomics Vision, this staking contract design enables **programmatic distribution** of rewards, with governance controlling key parameters, including reward amounts and staking rules.\n\nThe Staker contract allows ZK token holders to stake their tokens without any predetermined locking period, while simultaneously delegating their voting power. Moreover, delegation persists when stake is withdrawn. Over time, this framework could enable tokenholders to easily engage in any additional token utility opportunities like participating in DeFi with the ZK token.\n\nParticipation in this pilot will be limited to a predefined staking cap, with rewards funded by a 37.5M ZK capped minter divided over two seasons lasting ~3 months.\n\nTh proposal trials infrastructure necessary to support staking related to ZKsync’s future decentralized sequencer, while contributing to protocol sustainability via delegation. The system is non-custodial and integrated with Tally’s delegation interfaces.\n\nKey design choices include capped deposits, a reward emission stream over 30-day epochs, and a frontend hosted on Tally ([stake.zknation.io](http://stake.zknation.io/)).\n\nZK Token Staking will ensure staking works seamlessly and include recommendations for future versions. Tally and the Program Administrator will evaluate the traction of staking, its impact on  voting power, and additional configuration options to align participation to protocol liveness. Additional configuration examples include integration with ZKsync decentralized sequencing, sharing rewards with selected Delegate, contributing to protocol-owned liquidity, and crowdfunding conditional funding markets.\n\nThis program ensures security via completed audits, fund distribution pause and cancellation controls, and a framework that allows the Token Assembly to revoke or replace contract administration and operational teams via ZKsync governance proposals. Rewards will be distributed autonomously to eligible ZK token stakers over time.\n\n## Impact\n\nZK Token Staking builds towards a seamless tokenholder experience for the ZKnomincs Vision. Through staking, it deepens alignment between ZK holders and protocol design needs, distributing rewards to those supporting ZKsync’s long-term success. Most importantly, the program trials staking infrastructure necessary for the future decentralized sequencer supporting Stage 1 decentralization for ZKsync.\n\n### Pilot Strategic Objectives\n\n- Trial secure and reliable staking infrastructure in preparation for ZKsync’s decentralized sequencer, contributing to the [ZKnomincs Vision](https://forum.zknation.io/t/zknomics-roadmap-vision/712).\n- Increasing active voting power in governance from ~1B to ~2B. Active voting power is currently defined as participating in 2 or more of the most recent 5 votes.\n\n### **Pilot Operational Goals**\n\n- Deployment of staking infrastructure, ready for ZKsync decentralized sequencing and a modular design supporting ZKnomics.\n- **Season 1**: 400M ZK staked in total, with a maximum of 10M ZK distributed over 3 months (2.5% for 3-months or 10% annualized), 0 incidents.\n    - *Net increase of +200M active voting power (50% of staked ZK)*\n- **Season 2**: 1B ZK staked in total, with a maximum of 25M ZK distributed over 3 months (2.5% for 3-months or 10% annualized), 0 incidents, and integration with decentralized sequencing.\n    - *Net increase of +500M active voting power (50% of staked ZK)*\n\n> ℹ️ 1B ZK is ~15% of circulating supply (~7.1B).\n\n### Example Benchmarks Across Ethereum\n\n- ~29% of ETH is staked\n- stkAAVE peaked at ~20% of circulating supply\n\n\n> ⚠️ If there is not sufficient impact on the strategic objective during each season, as measured by a the increase in active voting power via staked ZK tokens, then the program may be cancelled by the Program Administrator.\n\n## Mechanic\n\n### **ZK Token Staker Contract by Tally: Pilot Configuration**\n\n| **Parameter name** | **Param value** | **Description** |\n| --- | --- | --- |\n| `stakeToken` | ZK | Users will stake ZK |\n| `rewardToken` | ZK | Rewards will be denominated in ZK |\n| `REWARD_DURATION` | 30 days | Each tranche of rewards is distributed pro-rata continuously over 30d window, to give stakers time to respond to changes in yield. |\n| `admin` | Season 1: Program Administrator Multisig <br> <br> Season 2: ZKsync Governance (Planned) | The admin can pause minting, set the `rewardNotifier` , set the `EarningPowerCalculator` , and change the `maxBumpTip`. |\n| `RewardNotifier` | [MintRewardNotifier](https://github.com/withtally/staker/blob/main/src/notifiers/MintRewardNotifier.sol) | The notifier will call `mint()` on the ZK token contract, then send the minted tokens to the staking system |\n| `EarningPowerCalculator` | [IdentityEarning PowerCalculator](https://github.com/withtally/staker/blob/main/src/calculators/IdentityEarningPowerCalculator.sol) | The `IdentityEarning PowerCalculator` makes every staker eligible. <br> <br> For future staking programs, earning power is calculated based on reward eligibility e.g. active participation in governance. |\n| `maxBumpTip` | 0.00005 ETH | The amount of ETH paid to searcher bots who update user’s earning power when it changes. <br> <br> (The `IdentityEarning PowerCalculator` does not change users’ earning power, but future calculators might) |\n| Governance compatibility | Yes | Staked ZK can delegate its voting power. | \nUpgradeability | Yes, via Token Governor | Staking contracts can be upgraded to support decentralized sequencing and other token utility upgrades |\n\nWhenever rewards enter the staking system, they are streamed out continuously over the next 30 days. That prevents discontinuities and race conditions. The turned-off staking system is planned to be deployed a minimum of 14 days prior to initial rewards start. As a result, all token-holders have the opportunity to stake with decreased time constraints.\n\nIn the pilot’s season 1, the annualised reward will be a maximum of 10% annualized. This assumes the staking cap of 400M ZK tokens is met, and rewarded a total of 10M ZK over the three-month period. This is equivalent to 2.5% for the 3 months of the season.\n\nIn season 2, the maximum reward would be ~10% annualized. This assumes the staking cap of 1B ZK tokens is met, and rewarded a total of 25M ZK over the three-month period. This is equivalent to ~2.5% for the 3 months of the season.\n\nAt the contract level, stakers can delegate their staked ZK’s voting power to any address. The Program Administration Team will have the ability to adjust reward eligibility such that staking rewards depend on the Delegate participating in governance.\n\nThe staking contracts are, like most smart contracts, open to anyone to call directly from any frontend. Tally will work with staking aggregators, wallets and custodians to integrate the system.\n\n### Capped Minter Configuration\n![Untitled-2025-06-18-1348(5)](https://hackmd.io/_uploads/By82Mb15xg.png)\n\n| **Capped Minter** | **Smart-Contract Addresses** |**Smart-Contract Admin Role** | **Smart-Contract Minter Role** | **Smart-Contract Pauser Role** | **Minting Start** | **Minting End** | **Token Configuration Parameters** |\n| --- | --- | --- | --- | --- | --- | --- | --- |\n| `Zk_StakingPilot_2025` (Parent Capped Minter) | [0xb1c5f8ea8cE447FDaFB234D85EAD8c8A83b6306B](https://explorer.zksync.io/address/0xb1c5f8ea8cE447FDaFB234D85EAD8c8A83b6306B#contract#read) | Token Governor | `Zk_StakingPilot_RateLimit_2025` | ZKsync Security Council | Oct 1, 2025 | Dec 31, 2026 | Cap: **37.5M ZK** |\n| `Zk_StakingPilot_RateLimit_2025` (Rate Limit Modifier) | [0x8076e2D38E47f5f8c755633022dc9B75e5039529](https://explorer.zksync.io/address/0x8076e2D38E47f5f8c755633022dc9B75e5039529#contract#read) |Program Administrator Multisig | `Zk_StakingPilot_Season1_2025` <br> <br> `Zk_StakingPilot_Season2_2025`<br> <br>`Zk_StakingPilot_Operations_2025` | n/a | n/a | n/a | Rate Limit: **10M ZK per month** |\n| `Zk_StakingPilot_Season1_2025` (Child Capped Minter) | [0xc977D85C66908F99b0948116Ba91705Eb6aF6a03](https://explorer.zksync.io/address/0xc977D85C66908F99b0948116Ba91705Eb6aF6a03#contract#read) |Program Administrator Multisig | Tally Staker | ZKsync Security Council | Oct 1, 2025 | Dec 31, 2026 | Cap: **10M ZK** |\n| `Zk_StakingPilot_Season2_2025` (Child Capped Minter) | [0x5E6f00629952B81bc8Cb461F085207D200eD8881](https://explorer.zksync.io/address/0x5E6f00629952B81bc8Cb461F085207D200eD8881#contract#read) | Program Administrator Multisig | Tally Staker | ZKsync Security Council | Oct 1, 2025 | Dec 31, 2026 | Cap: **25M ZK** |\n| `Zk_StakingPilot_Operations_2025` (Child Capped Minter) | [0xE11730Ede166eB06F444FFBF6B11b456C4e5C595](https://explorer.zksync.io/address/0xE11730Ede166eB06F444FFBF6B11b456C4e5C595#contract#read) |Program Administrator Multisig | Child Capped Minters and Rate Limiters for Service Providers. | ZKsync Security Council | Oct 1, 2025 | Dec 31, 2026 | Cap: **2.5M ZK** |\n\nThe capped minter/minter mod design is setup in a way where all child capped minters will be subject to an overall rate limit of 10M ZK per month. This rate limit is designed to accommodate variations in spending and potential token volatility.\n\nThe Token Assembly is the admin of the parent capped minter (`ZK_StakingPilot_2025`), and the Security Council has the pauser role.\n\nThe three calls that will be executed if this proposal is passed include: \n- Grant minter role from ZK token contract to `Zk_StakingPilot_2025`\n- Grant minter role from `Zk_StakingPilot_2025` to `Zk_StakingPilot_RateLimit_2025`\n- Grant pauser role on `Zk_StakingPilot_2025` to the ZKsync Security Council ([0xfFB6126FF8401665081b771bB11cCD0e09f95D5A](https://explorer.zksync.io/address/0xfFB6126FF8401665081b771bB11cCD0e09f95D5A))\n\n## **ZK Token Staker: Reward Management**\n\nRewards will be incrementally increased by the Program Administrator over the course of each season. This will optimize the reward in such a way that the cap is met at the lowest level of distributed award. For example:\n\n- Season Launch: Set at an initial 3% return.\n- Each week: The reward return may be increased by up to an absolute 1% if cap is not met.\n- The maximum return is capped at 10%, which is the full deployment of rewards.\n- Rewards may also be decreased to fully quantify change in demand.\n\nReward eligibility is limited to tokenholders delegating to active Delegates, those that have voted a minimum of 2 out of last 5 votes.\n\n> ℹ️ Please note the exact initial return and weekly increases will be defined by the Program Administrator during the program based on ongoing analysis. The exact methodology may vary based on guidance to ensure efficient use of pilot rewards.\n\n</aside>\n\n## **ZK Token Staker: User Interface**\n\nStaking would be available on [stake.zknation.io](http://stake.zknation.io/).\n\n- *See also [Obol's staking UI on Tally](https://www.tally.xyz/gov/obol/stake) as a reference.*\n\n![Tally 1](https://hackmd.io/_uploads/S1LtCJJ5le.png)\n\n\n![Tally 2](https://hackmd.io/_uploads/SyCYA1J9xx.png)\n\n\n![Tally 3](https://hackmd.io/_uploads/HJlvcCJkcxe.png)\n\n\nTo participate in staking, tokenholders are required to delegate their ZK voting power.\n\n![Tally 4](https://hackmd.io/_uploads/Hk-iCyy5xe.png)\n\n\n![Tally 5](https://hackmd.io/_uploads/B15iAkJcex.png)\n\n\nStakers earn rewards over time. Rewards are proportional to their share of the total staked amount. For example, Alice stakes 600 ZK and Bob stakes 400 ZK, for a total of 1000 staked ZK. No one else stakes. If there is a reward of 10 ZK emitted over one day, 6 of it would go to Alice and 4 of it to Bob. Additionally, stakers can choose to split their voting power to more than one Delegate, and each staking position has its own eligibility to rewards. \n\n### [Click to View Demo Video](https://drive.google.com/file/d/1VyiUIfoFPK1NNTrIw0biuUAVgYtcQxqd/view)\n\nStaking contracts are upgradeable with the Token Governor Timelock set as owner. For future seasons, the ZKsync Token Assembly can choose, via ZKsync Governance, to upgrade the staking contracts include expanded token utility options, such as supporting decentralized sequencing.\n\nDelegate selection is customizable on Tally and guided by the ZKsync Governance Team, in collaboration with the Program Administrator. Delegates eligibility will be refined over time.\n\nDelegate eligibility criteria will also be adapted based on and program performance. Operator selection (e.g. such as sequencers) may become available depending on protocol development progress. Stakers will be able to view their annualized return. For example, 10M ZK rewards over 3 months for 400M staked = ~10% APY annualized.\n\n## Operational Timeline Estimate\n\n- **September 2025:** Governance approval, parameter tuning, UI integration + frontend testing\n- **October 2025**: Season 1 launch\n- **January 2026**: Season 2 launch\n\n## Accountability\n\n- **Token Allocation Tracking:** Token minting will be available for public review using the ZKsync [Capped Minter Dune Dashboard](https://dune.com/zk_nation/zksync-token-program-capped-minters), or alternative interface if applicable.\n- **Governance Forum Posts:** The Program Administration Team will publish updates on the ZKsync Governance Forum at the start and end of each season. Should a period extend beyond three months, an intermediate update will be included.\n- **Token Assembly Oversight:** The Token Assembly may cancel the parent capped minter at any point via a Token Program Proposal and revoke any further disbursements.\n- **Security Council Oversight:** The Security Council may pause any of the capped minters at any point if deemed necessary.\n- **KYC/KYB**: Required for Program Administration Team and service providers.\n- **Audit Requirements**: Contracts fully [audited and published](https://github.com/withtally/staker/tree/main/audits).\n- **Excess Tokens:** Any excess tokens not used for the program should remain unminted. If excess tokens are minted, they will be returned to the control of the Token Assembly.\n- **Impact:** If there is not sufficient impact on the strategic objective during the first season, as measured by increase in active voting power via staked ZK tokens, the Program Administration Team will provide a recommendation to continue or pause the program.\n\n## Service Provider Token Allocation\n\nService provider token allocations are designed to align with program objectives. For ZK Token Staking, token allocations are locked for 6-months, ensuring the Program Administration Team can confirm completion of services prior to unlock.\n\n| **Service Provider** | Tally |\n| --- | --- |\n| **Token Allocation** | *Up to 2.5M ZK tokens, with minting rate limited to ~416,667 ZK per month.* |\n| **Services Description** | **Staker Smart Contract Deployment**: Secure deployment and initialization of the staking contract, customized to meet network-specific requirements. [Supported by ScopeLift Engineering] <br> <br> **Frontend Activation & Customization**: Integration with the Tally interface, including branding, UI/UX adjustments, Delegate eligibility and discovery, and user onboarding configuration.<br> <br> **Analytics & Reporting**: Public dashboards and periodic reports to monitor staking activity, program objectives, and participation trends.<br> <br> **Continuous Contract Configuration**: Ongoing adjustment of staking parameters, reward logic, and utility integrations in accordance with program objectives. <br> <br> **Staker Smart Contract Audit:** Complete audit of network-specific related customizations to Tally Staker contract. [Supported by Offbeat Security] <br> <br> **Continuous Contract Security Review:** Ongoing security monitoring of staking contract, and security review of contract changes and additional modules. [Supported by Offbeat Security] <br> <br>**Operational Support**: Assistance for program execution throughout the program, including troubleshooting, community support workflows, and governance coordination. |\n\nService providers will complete a contract with ZKGPS in alignment to the services scope and payment as defined in this proposal.\n\n## Program Administrator\n\nThe Program Administrator, overseeing Tally’s operational execution and contracts, will be composed by a 4/7 multisig [`0x4eA3EA51f8fDFfb34583C9B729b1c443607Be0bC`](https://explorer.zksync.io/address/0x4eA3EA51f8fDFfb34583C9B729b1c443607Be0bC) :\n\n- ZKsync Foundation\n- Matter Labs Signer 1\n- Matter Labs Signer 2\n- ScopeLift\n- Areta \n- Security Council Signer 1\n- Security Council Signer 2\n\nCompensation for independent participants, set at 100,000 ZK for the program (approximately 7-9 months), will be covered by ZKGPS. \n\nThe ZKsync Security Council Multisig ([0xfFB6126FF8401665081b771bB11cCD0e09f95D5A](https://explorer.zksync.io/address/0xfFB6126FF8401665081b771bB11cCD0e09f95D5A)) will be granted the Pauser role on program Capped Minters.\n\n## Participants\n\n- **Tally:** Proposal development, staker contracts, frontend, and analytics. Day to day operations.\n- **Program Administrator:** Responsible for overseeing program and admin role of contracts.\n- **Marketing Support**: The ZKsync Foundation will coordinate efforts with current service providers to support the proposal if necessary.\n- **[ZKGPS](https://docs.zknation.io/legal/zksync-governance-program-systems-zkgps):** Serves as legal counterparty for program service providers.\n- **Token Assembly:** Oversees minting and retains final authority to halt program.\n\n## Other Information\n\n- [ZKsync roadmap on decentralization](https://zksync.mirror.xyz/QG2Xr4lQdJTbyjeKftPVc6-pj2t9-H9WEGnvCcnusck)\n- [ZK tokenomics vision](https://forum.zknation.io/t/zknomics-roadmap-vision/712)\n- ZKStaker: [0x8373A5dFb76bD6Bb93d89024d5B48438dCb0181E](https://explorer.zksync.io/address/0x8373A5dFb76bD6Bb93d89024d5B48438dCb0181E#contract#contract-info)\n- Earning Power Calculator: [0x6Df898C28C161B864c0FED3E7A098cCf99407119](https://explorer.zksync.io/address/0x6Df898C28C161B864c0FED3E7A098cCf99407119#contract)\n- [Staker GitHub](https://github.com/withtally/staker)\n- [Staker Audit](https://github.com/withtally/staker/tree/main/audits)\n- [Contract Implementation Spec](https://docs.google.com/document/d/1Ng8NM1eZZk7DZDrlhtHikJ3FJP9TXDUYzQx9yQ1KbtQ/edit?tab=t.0)\n\n- [Deployment parameters](https://hackmd.io/UWxXdY3ERJq-_ocVhnDLAg)"
}

By ZKSync Governance • 10/15/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65266586
Timestamp: 10/15/2025, 7:55:08 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalCreated
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "8043865517871673466500920771587039178855876090726876272793935297016439640908",
  "proposer": "0x1f76a6Bf03429480472B3695E08689219cE15ED6",
  "targets": [
    "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
    "0x1E386bc1FC6556c831371816f0a62705189939A1",
    "0x1E386bc1FC6556c831371816f0a62705189939A1"
  ],
  "values": [
    "0",
    "0",
    "0"
  ],
  "signatures": [
    "",
    "",
    ""
  ],
  "calldatas": [
    "0x2f2ff15d9f2df0fed2c77648de5860a4cc508cd0818c85b8b8a1ab4ceeef8d981c8956a60000000000000000000000001e386bc1fc6556c831371816f0a62705189939a1",
    "0x2f2ff15d9f2df0fed2c77648de5860a4cc508cd0818c85b8b8a1ab4ceeef8d981c8956a60000000000000000000000008d03f20c213d435a8b50127de3d5797845b2120d",
    "0x2f2ff15d65d7a28e3265b37a6474929f336521b332c1681b933f6cb9f3376673440d862a000000000000000000000000ffb6126ff8401665081b771bb11ccd0e09f95d5a"
  ],
  "voteStart": "1761119708",
  "voteEnd": "1761724508",
  "description": "# [TPP-11] ZKsync Governance System Infrastructure Funding\n# [TPP-11] ZKsync Governance System Infrastructure Funding\n\n| **Title** | ZKsync Governance System Infrastructure Funding |\n| --- | --- |\n| **Proposal Type** | TPP |\n| **One Sentence Summary** | The ZKsync Association requests funding ~$1.65M USD (33M ZK at $0.05/ZK) in services to maintain and evolve the governance infrastructure, critical for executing ZKsync’s protocol upgrades, token programs, and network coordination until December 31, 2026. |\n| **Proposal Author** | ZKsync Association |\n| **Proposal Sponsor** | Polar |\n| **Date Created** | 2025-10-15 |\n| **Version** | v1.0 |\n| **Summary of Action** | This proposal activates a capped minter with access to 33M ZK, approximately $1.65M USD, with a rate-limit of 8M ZK per month. The ZKsync Association will serve as the manager of these services and will facilitate disbursements via capped minters under approved scope. |\n| **Link to proposal discussion** | https://forum.zknation.io/t/tpp-draft-zksync-governance-system-infrastructure-funding/781 |\n\n---\n\n## Abstract\n\nThis proposal funds governance infrastructure that power protocol upgrades, token distribution, and coordination across the ZKsync ecosystem.\n\nThis Token Program Proposal (TPP) approves a ZK Capped Minter for ~33M ZK, approximately $1.65M USD calculated at $0.05/ZK, with a rate limit of up to 8M ZK per month, and an expiry date of December 31, 2026.\n\nThe ZKsync Association’s governance team will serve as the manager of these services and will facilitate disbursements via capped minters under approved scope. The token allocation request does not include any tokens for the ZKsync Association itself, salaries, or other operational overhead.\n\n## Motivation\n\n[The ZKsync Governance System launched on September 12th 2024](https://blog.zknation.io/zksync-governance-system/), activating the governance smart-contracts, interfaces, and operations.\n\nGovernance systems underpin major coordination functions in the ZKsync ecosystem. These include executing protocol upgrades, activating new token programs, and responding to protocol emergencies. Ensuring these systems remain secure, adaptable, and easy to use is critical to delivering on [ZKsync’s roadmap](https://zksync.mirror.xyz/QG2Xr4lQdJTbyjeKftPVc6-pj2t9-H9WEGnvCcnusck).\n\nSince launch, the ZKsync Association’s Governance Team has played the role of facilitator, steward, and quality manager in design, launch, and maintenance of the system. The Governance Team works in close collaboration with the Security Council, Guardians, ZKsync Foundation and Token Assembly Delegates. This role closely aligns with multiple of the ZKsync Association’s purposes, as defined in their Articles of Association. For example:\n\n> *2.2 Support the development of secure, transparent and censorship resistant digital infrastructures for the benefit of the society; \n2.5 Promote the democratization and  decentralization of blockchain technology and ensure that engagement in the development and governance of ZK protocols  and similar technology is possible for all individuals, irrespective of their origin and financial resources;*\n> \n![Frame(2)](https://hackmd.io/_uploads/ryCMsBWTel.png)\n\n\n>*Figure 1: The ZKsync Association supports and helps secure the ZKsync governance system*\n\nThe work from today until the end of 2026 will maintain and responsively evolve the infrastructure activated at launch.\n\nThis proposal scope and token allocation assumes the ZKsync Association’s Governance Team serves as the program administrator of this TPP, responsible for execution of the scope and any required service provider selection and management. The Governance Team would use their resources and relationships to maintain and improve the security, capability, and accessibility of ZKsync governance. Tactical services scope will be defined by the Governance Team, along with the necessary service provider selection process.\n\nPerformance is [measured via metrics](https://dune.com/zk_nation/zk-nation-governance-overview) tracking governance security, reliability, responsiveness, and participation. These include voting power, time to quorum, incidents, and protocol upgrades approved via standard upgrades.\n\nThe ZKsync Association will coordinate legal contracts between service providers and ZKGPS based on performance history, ecosystem alignment, and cost. A full service provider history is available for reference.\n\n## Program Mechanics\n\nThe ZKsync Association’s Governance Team will manage service providers responsible for core governance infrastructure and facilitate token allocations using capped minters. This includes:\n\n- Publishing a roadmap for governance, aligned with protocol and ecosystem priorities.\n- Managing RFPs for service delivery based on scope and urgency.\n- Creating and administering capped minters for compensating participating service providers.\n\n### Governance Activities Overview\n\n| **Activity Category** | **Description** | **Scope of Activities** |\n| --- | --- | --- |\n| **1. Governance Contracts for Protocol and Token Coordination** | Maintain capped minter contracts, minter mods, governor contracts, related L1 contracts such as custom multisigs, the ZK token contract, and any other related smart-contract. | Governors and Timelocks <br> Compatibility with Upgrade Handler <br> ZK Token Contract <br> Capped Minters and Minter Mods <br> Emergency Board, Guardians, and Security Council Multisigs <br> Token Mechanics Patterns <br> Token Mechanics Deployments <br> Other smart-contracts |\n| **2. Governance Interfaces and Participation Tooling** | Maintain the [Governance Portal](http://vote.zknation.io), [Governance Forum](http://forum.zknation.io), [Github Repo](https://github.com/ZKsync-Association), [ZK Nation Website](http://zknation.io), [Documentation](http://docs.zknation.io), [communication channels](https://t.me/ZKsyncDelegateAnnouncements), [RSS governance feed](https://www.zknation.io/feed), and other related interfaces. | Canonical Governance Portal <br>Secondary Governance Portal <br> Governance Forum <br> Governance Analytics <br> ZK Nation Website <br> ZK Nation Blog <br> ZK Nation Docs  <br> ZK Nation Brand Assets and Content <br> GovFeed RSS <br> GitHub Repository  <br> Other communication channels (Twitter, Telegram, etc.) |\n| **3. Security Infrastructure for Protocol and Token Safety** | Continue security efforts related to monitoring, assessment frameworks, reviews, audits, and security rehearsals. [Governance audits are available for review at the ZKsync Docs.](https://docs.zksync.io/zksync-protocol/security/audits) | Governance Audits <br> Capped Minter Audits <br> Proposal Verification Tool <br> Contract Monitoring <br> Security Reviews <br> Security Policies <br> Governance Action Rehearsals <br> Threat Modelling and Simulations <br> Incident Response Management |\n| **4. Operational and Legal Infrastructure for Decentralized Execution** | Maintain legal entities, regulatory requirements (e.g. MiCA whitepaper), and other related operations such as legal contract management for ZKGPS, ZKsync Guardians, and token programs. | Legal Counsel <br> IP Management <br> Security Council Operations <br> ZKGPS Operations <br> Integrations with custodians <br> Global SteerCo, Proposal Contributors <br> General Token Program Analytics <br> Regulatory Alignment (e.g. MICAR) <br> Other Token Program needs |\n\n### Funding Request Summary\n\nThe requested costs for the period of September 2025 to December 2026 are derived from direct experience preparing, launching, and maintaining governance infrastructure from 2024 through to the end of August 2025. Each category contributes to the system’s capacity to deploy secure, adaptive, and decentralized upgrades.\n\nAs noted in the table, operations were supported by donations and services from both Matter Labs and the ZKsync Foundation.\n\n| **Activity Category** | **Requested ZK @ $0.05** | **USD Forecast September 2025 to December 2026** | **USD Reference Resource Costs from Jan 2024-August 2025** |\n| --- | --- | --- | --- |\n| **1. Governance Contracts for Protocol and Token Coordination** | 7,100,000 | $355,000 | ~$1,050,000 |\n| **2. Governance Interfaces and Participation Tooling** | 9,566,660 | $478,333 | ~$420,000 |\n| **3. Security Infrastructure for Protocol and Token Safety** | 7,987,500 | $399,375 | ~$770,000 |\n| **4. Operational and Legal Infrastructure for Decentralized Execution** | 8,250,000 | $412,500 | ~$710,000 |\n| **Total** | 33,000,000 ZK <br> *[Rounded 32,904,160 ZK]* | **$1,645,208** | **~$2,950,000** <br> *Bootstrapped via donations from Matter Labs and support from the ZKsync Foundation* |\n\n### Funding Request Analysis Assumptions\n\n- **Reference Cost Estimate:** References from 2024-2025 includes governance-related service provider invoices as well as a conservative estimate of engineering effort at industry rate.\n- **Forecast Cost Estimate:** Includes linear projection of ongoing services required for regular operations.\n- **Out of Scope:** The costs in the requested budget exclude ZKsync Security Council member payments, ZKsync Guardians member compensation, ZKsync Association Directorships, Governance Team salary and overhead costs, ZKsync Association coordinated events, or ZKsync Association education initiatives.\n- **Audit Costs:** Any protocol upgrades related to the scope of this proposal are planned to be audited using the token allocation from this proposal. As a result, they would opt-out of security audit reimbursements via TPP3 ZKsync Audit Reimbursement Program (ZARP).\n- **Category Budget Flexibility:** The ZKsync Association Governance Team may adjust spending across categories. Services and category-level token allocations will be communicated to the Token Assembly through the ZKsync Governance Forum.\n- Includes a 20% budget buffer to account for:\n    - Additional significant smart-contract changes when aligning to new protocol components such as Gateway.\n    - Additional security requirements.\n    - Additional regulatory requirements.\n- **Estimates Rounding:** Historical figures rounded to nearest $10k. Final ZK figures have been rounded to the nearest 1,000,000 ZK.\n\n### Capped Minter Structure\n![Gov Infra Updated](https://hackmd.io/_uploads/r1wQYln3ge.svg)\n\n| **Capped Minter** | **Smart-Contract Address** | **Smart-Contract Admin Role** | **Smart-Contract Minter Role** | **Smart-Contract Pauser Role** | **Minting Start** | **Minting End** | **Token Configuration Parameters** |\n| --- | --- |--- | --- | --- | --- | --- | --- |\n| `Zk_Governance_2025` (Parent Capped Minter) | [0x1E386bc1FC6556c831371816f0a62705189939A1](https://explorer.zksync.io/address/0x1E386bc1FC6556c831371816f0a62705189939A1#contract#read) | Token Governor Timelock | `Zk_Governance_RateLimit_2025` | Security Council | October 3, 2025 | December 31, 2026 | Cap: **33M ZK** |\n| `Zk_Governance_RateLimit_2025` (Rate Limit Modifier) |[0x8d03F20C213D435A8B50127DE3d5797845b2120D](https://explorer.zksync.io/address/0x8d03F20C213D435A8B50127DE3d5797845b2120D#contract#read) | Token Governor Timelock | `Zk_Governance_Operations_2025` | Security Council via Parent Capped Minter | n/a | n/a | Rate Limit: **8M ZK per month** |\n| `Zk_Governance_Operations_2025` (Child Capped Minter) | [0x9e43647EF21194d6b4b29673DadeEC2688e6BA3D](https://explorer.zksync.io/address/0x9e43647EF21194d6b4b29673DadeEC2688e6BA3D#contract#read) | ZKsync Association Governance Team Multisig | Child Capped Minters for Service Providers | Security Council via Parent Capped Minter | October 3, 2025 | December 31, 2026 | Cap: **33M ZK** |\n| Child Capped Minters for Service Providers (Child Capped Minters) | To be created as confirmed | Service Providers | Service Providers | ZKsync Association Multisig; Security Council via Parent Capped Minter | Aligned to Services | Aligned to Services | Aligned to Services |\n\nThe program will be managed through a series of capped minters and will be subject to a global rate limit of 8M ZK per month. This rate limit is designed to accommodate variations in spending and potential token volatility. All child capped minters are subject to the global rate limit (i.e. collectively they cannot mint over the 8M global rate limit).\n\nMinting rights for future child capped minters assigned to service providers will be granted from the `ZK_Governance_Operations_2025` capped minter, controlled by the ZKsync Association Governance Team 3/5 Multisig. This enables service providers to mint at their discretion within the designated minting window. \n\nThe three calls that will be executed if this proposal is passed include:\n\n - Grant minter role from ZK token contract to `Zk_Governance_2025`\n - Grant minter role from `Zk_Governance_2025` to `Zk_Governance_RateLimit_2025`\n - Grant pauser role on `Zk_Governance_2025` to the ZKsync Security Council ([0xfFB6126FF8401665081b771bB11cCD0e09f95D5A](https://explorer.zksync.io/address/0xfFB6126FF8401665081b771bB11cCD0e09f95D5A))\n\n\n\n## Accountability\n\n- **Token Allocation Tracking:** Token minting will be available for public review using the ZKsync [Capped Minter Dune Dashboard](https://dune.com/zk_nation/zksync-token-program-capped-minters), or alternative interface if applicable.\n- **Governance Forum Posts:** The ZKsync Association Governance Team will publish updates on the forum at the start and end of contracted services. Should a book of work extend beyond three months, an intermediate update will be included.\n- **Token Assembly Oversight:** The Token Assembly may cancel the parent capped minter at any point via a Token Program Proposal and revoke any further disbursements.\n- **Security Council Oversight:** The Security Council may pause the parent capped minter at any point if deemed necessary.\n- **Annual Reports:** The ZKsync Association Governance Team will publish a report annually, or otherwise required by any future governance guidance. The report will summarize:\n    - Governance system updates\n    - Selected service providers and contracted scope of work\n    - Total token allocations by category\n- **Excess Tokens:** Any excess tokens not used for the budget should remain unminted. If excess tokens are minted, they will be returned to the control of the Token Assembly.\n- **Budget Changes:** If budget requirements increase beyond the request, the ZKsync Association Governance Team will submit a Governance Advisory Proposal (GAP) to authorize the budget increase and any relevant scope changes.\n\n## Governance Team Metrics\n\nThe primary metrics for the governance system functionality are as follows:\n\n| **Metric^** | **Current (as of Sept 9 2025)** | **Objective (18-months)** | **Notes** |\n| --- | --- | --- | --- |\n| **Category A: Security and Reliability** |  |  |  |\n| A.1 % of ZKsync standard protocol upgrades voted on by Token Assembly | 100% | 100% | Shows system is working as expected, no emergency actions needed for standard upgrades. |\n| A.2 Number of governance incidents  (Operational or Onchain) | [1](https://zksync.mirror.xyz/W5vPDZqEqf2NuwQ5x7SyFnIxqqpE1szAFD69iaaBFnI)** | 0 | Tracks errors in governance infrastructure design, deployment, and monitoring. Excludes protocol-specific incidents and emergency actions. |\n| A.3 % Token Proposals configured correctly with capped minters | 100% | 100% | Reflects adoption of infra across ecosystem |\n| — | — | — | — |\n| **Category B: Responsiveness and Participation** |  |  |  |\n| B.1 Average time to quorum in last 5 votes (days) | 4.6 days | 3 days | Faster quorum = more responsive system. |\n| B.2 Active* delegates voting power | ~980 Million | 2 Billion | The goal is to double active governance engagement. |\n| B.3 % of ZKsync Partners active* in governance | Not Tracked | >80%*** | Ties governance infra to real-world ecosystem orgs. |\n| B.4 % of Emergency Upgrade Board members who responded in at least 1 of last 2 actions (rehearsal or upgrade) | Not Tracked | 100% | Ensures all critical signers are active and responsive in case of emergency. |\n\n> *^Public metrics are available for review on the ZK Nation Governance Performance [Dune Dashboard.](https://dune.com/zk_nation/zk-nation-governance-overview)\n*Active means voted at least twice in recent 5 votes\n**Further details related to the governance incident are available on the [ZKsync blog.](https://zksync.mirror.xyz/W5vPDZqEqf2NuwQ5x7SyFnIxqqpE1szAFD69iaaBFnI)\n***Exclude ZKsync Partners who are not be eligible to participate in governance due to legal requirements or other business policy. In some cases, ZKsync Partners would participate indirectly via delegation, which would satisfy the criteria.*\n\n## Program Administrator\n\nThe Program Administrator, overseeing the operational execution and contracts, will be composed by a 4/7 multisig ([`0x6162BEfaaf5C2598dD92087A5a479b10b135275a`](https://explorer.zksync.io/address/0x6162BEfaaf5C2598dD92087A5a479b10b135275a)) :\n\n- ZKsync Association: 5 signers, including team members and board members\n- Security Council: 2 signers\n\nThe ZKsync Security Council Multisig ([0xfFB6126FF8401665081b771bB11cCD0e09f95D5A](https://explorer.zksync.io/address/0xfFB6126FF8401665081b771bB11cCD0e09f95D5A)) will be granted the Pauser role on program Capped Minters.\n\n## Participants\n\n- **ZKsync Association Governance Team:** Defines governance improvement roadmap, creates new capped minters, and manages tactical work from service providers.\n- **Service Providers:** Responsible for completion of work in alignment with ZKsync Governance System Needs.\n- [**ZKGPS**](https://forum.zknation.io/t/zkgps-advancing-accountability-in-proposal-execution/480): Serves as legal counterparty for service providers.\n- **Token Assembly:** Oversees minting and retains final authority to halt program."
}

By ZKSync Governance • 10/14/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65246640
Timestamp: 10/14/2025, 7:19:56 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExecuted
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "15539336001504922041482045464843306651217071205321499428543388348391561812720"
}

UpgradeApprovedBySecurityCouncil - Protocol Upgrade Handler v2.0

By ZKSync Governance • 10/14/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65246640
Timestamp: 10/14/2025, 7:19:56 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallExecuted
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0xbea83587cc39eb79da7a70ef2cf34a7b687ce2b2d98fef1c1ee975d16d1f5d4c",
  "index": "0",
  "target": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
  "value": "0",
  "data": "0xa9059cbb...b9000000"
}

By Ethereum Governance • 10/13/2025

Event Details

Network: Ethereum Mainnet
Chain ID: 1
Block: 23568177
Timestamp: 10/13/2025, 10:24:35 AM

Governance Info

Governance Body: Ethereum Governance
Event Type: UpgradeApprovedBySecurityCouncil
Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3

Event Data

{
  "_id": "0x5451e3aa34aba5b9bd71b567e38be4d075915705d110a37a2d851945be2c4d43"
}

UpgradeApprovedBySecurityCouncil - Protocol Upgrade Handler v2.0

By Ethereum Governance • 10/13/2025

Event Details

Network: Ethereum Mainnet
Chain ID: 1
Block: 23568158
Timestamp: 10/13/2025, 10:20:47 AM

Governance Info

Governance Body: Ethereum Governance
Event Type: UpgradeApprovedBySecurityCouncil
Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3

Event Data

{
  "_id": "0x797ed4fb2a525632d25f0128840e8f684188c823fec6e0037410465d197610f9"
}

UpgradeApprovedBySecurityCouncil - Protocol Upgrade Handler v2.0

By Ethereum Governance • 10/13/2025

Event Details

Network: Ethereum Mainnet
Chain ID: 1
Block: 23567758
Timestamp: 10/13/2025, 8:59:23 AM

Governance Info

Governance Body: Ethereum Governance
Event Type: UpgradeExecuted
Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3

Event Data

{
  "_id": "0x6421bba58a13a6280796ba745b62249664fb9dd7d8c8b3769b54489b58c33710"
}

By Ethereum Governance • 10/12/2025

Event Details

Network: Ethereum Mainnet
Chain ID: 1
Block: 23560522
Timestamp: 10/12/2025, 8:42:59 AM

Governance Info

Governance Body: Ethereum Governance
Event Type: UpgradeApprovedBySecurityCouncil
Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3

Event Data

{
  "_id": "0x6421bba58a13a6280796ba745b62249664fb9dd7d8c8b3769b54489b58c33710"
}

ProposalExecuted - ZkProtocolGovernor

By ZKSync Governance • 10/10/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65169644
Timestamp: 10/10/2025, 7:09:17 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallScheduled
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0xbea83587cc39eb79da7a70ef2cf34a7b687ce2b2d98fef1c1ee975d16d1f5d4c",
  "index": "0",
  "target": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
  "value": "0",
  "data": "0xa9059cbb...b9000000",
  "predecessor": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "delay": "259200"
}

By ZKSync Governance • 10/6/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65089032
Timestamp: 10/6/2025, 5:35:41 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExecuted
Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
Proposal Link: View Proposal

Event Data

{
  "proposalId": "22471812359223094779541460804735287481991027375586193607912523407322605938475"
}

CallExecuted - ZkProtocolGovernor Timelock v2.0

By ZKSync Governance • 10/6/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65089032
Timestamp: 10/6/2025, 5:35:41 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallExecuted
Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714

Event Data

{
  "id": "0x5ed0e1b0b518c0968d33c5c027c03eca0d79b0a211511169c2b9ac0e30eb21c0",
  "index": "0",
  "target": "0x0000000000000000000000000000000000008008",
  "value": "0",
  "data": "0x62f84b24...00000000"
}

ProposalExecuted - ZkProtocolGovernor

By ZKSync Governance • 10/6/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65088924
Timestamp: 10/6/2025, 5:27:22 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExecuted
Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
Proposal Link: View Proposal

Event Data

{
  "proposalId": "40562439712311128665286075271414168289029475306445402072499591795343687723101"
}

CallExecuted - ZkProtocolGovernor Timelock v2.0

By ZKSync Governance • 10/6/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65088924
Timestamp: 10/6/2025, 5:27:22 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallExecuted
Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714

Event Data

{
  "id": "0x9b4b131ad0cc4e223f128019a535d12b51782067e85af0379562ecf1151566bf",
  "index": "0",
  "target": "0x0000000000000000000000000000000000008008",
  "value": "0",
  "data": "0x62f84b24...00000000"
}

CallScheduled - ZkProtocolGovernor Timelock v2.0

By ZKSync Governance • 10/6/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65088687
Timestamp: 10/6/2025, 5:15:45 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallScheduled
Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714

Event Data

{
  "id": "0x5ed0e1b0b518c0968d33c5c027c03eca0d79b0a211511169c2b9ac0e30eb21c0",
  "index": "0",
  "target": "0x0000000000000000000000000000000000008008",
  "value": "0",
  "data": "0x62f84b24...00000000",
  "predecessor": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "delay": "0"
}

CallScheduled - ZkProtocolGovernor Timelock v2.0

By ZKSync Governance • 10/6/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65088680
Timestamp: 10/6/2025, 5:15:30 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallScheduled
Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714

Event Data

{
  "id": "0x9b4b131ad0cc4e223f128019a535d12b51782067e85af0379562ecf1151566bf",
  "index": "0",
  "target": "0x0000000000000000000000000000000000008008",
  "value": "0",
  "data": "0x62f84b24...00000000",
  "predecessor": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "delay": "0"
}

By ZKSync Governance • 10/3/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65033108
Timestamp: 10/3/2025, 5:24:33 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExtended
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "15539336001504922041482045464843306651217071205321499428543388348391561812720",
  "extendedDeadline": "1760117073"
}

By ZKSync Governance • 10/2/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65017494
Timestamp: 10/2/2025, 9:17:02 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExecuted
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "3413588788305073197878658504162606756015331882899383310343250085297198101137"
}

By ZKSync Governance • 10/2/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65017494
Timestamp: 10/2/2025, 9:17:02 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallExecuted
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0x5d827e39efd4f9e83a5ba0e294c05c52de84d9695703d36d88b883d6e4155f7b",
  "index": "0",
  "target": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
  "value": "0",
  "data": "0x2f2ff15d...ca522238"
}

By ZKSync Governance • 10/2/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65008686
Timestamp: 10/2/2025, 11:58:33 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: ProposalExecuted
Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
Proposal Link: View Proposal

Event Data

{
  "proposalId": "19993014537746296636853362219247192671631735482612670856590540039176244970638"
}

By ZKSync Governance • 10/2/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 65008686
Timestamp: 10/2/2025, 11:58:33 AM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallExecuted
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0x0b6cb3569b553196b8e620e52ad7e79293d0979acd88e8fd7c841c3df8f02197",
  "index": "0",
  "target": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
  "value": "0",
  "data": "0xa9059cbb...94000000"
}

By ZKSync Governance • 9/29/2025

Event Details

Network: ZKSync
Chain ID: 324
Block: 64959354
Timestamp: 9/29/2025, 8:33:10 PM

Governance Info

Governance Body: ZKSync Governance
Event Type: CallScheduled
Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d

Event Data

{
  "id": "0x5d827e39efd4f9e83a5ba0e294c05c52de84d9695703d36d88b883d6e4155f7b",
  "index": "0",
  "target": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E",
  "value": "0",
  "data": "0x2f2ff15d...ca522238",
  "predecessor": "0x0000000000000000000000000000000000000000000000000000000000000000",
  "delay": "259200"
}