ZKsync Governance Feed
Monitor onchain ZKsync governance events
Last updated: 6/19/2025, 2:40:09 PM
View SourceBy Ethereum Governance • 6/19/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22739136
- Timestamp: 6/19/2025, 2:30:59 PM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeExecuted
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0x21cc8f34509885c0923943891a2ca035ee832e04dec4d5b2aaeb72200381510f"
}
}By Ethereum Governance • 6/19/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22739116
- Timestamp: 6/19/2025, 2:26:59 PM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeExecuted
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0x78e499d049cb780ca3d62ab0021c654f0cdd5e11941545c3c057023abb256c9b"
}
}By ZKSync Governance • 6/18/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 61869732
- Timestamp: 6/18/2025, 2:59:42 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalCanceled
- Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "62921954496791164991088292844527972033503604235062526266434445973055965160650"
}
}By Ethereum Governance • 6/18/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22731933
- Timestamp: 6/18/2025, 2:22:23 PM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeApprovedBySecurityCouncil
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0x21cc8f34509885c0923943891a2ca035ee832e04dec4d5b2aaeb72200381510f"
}
}By Ethereum Governance • 6/18/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22731930
- Timestamp: 6/18/2025, 2:21:47 PM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeApprovedBySecurityCouncil
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0x78e499d049cb780ca3d62ab0021c654f0cdd5e11941545c3c057023abb256c9b"
}
}By Ethereum Governance • 6/11/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22683665
- Timestamp: 6/11/2025, 8:20:35 PM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeExecuted
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0x3f9829a652062f0659c7a440ef7ed6a877f83dacdb1a221d2858890912f34f94"
}
}By Ethereum Governance • 6/10/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22673220
- Timestamp: 6/10/2025, 9:18:35 AM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeApprovedBySecurityCouncil
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0x3f9829a652062f0659c7a440ef7ed6a877f83dacdb1a221d2858890912f34f94"
}
}By ZKSync Governance • 6/9/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 61508783
- Timestamp: 6/9/2025, 10:15:58 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalCreated
- Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "62921954496791164991088292844527972033503604235062526266434445973055965160650"
},
"proposer": {
"value": "0xdEdD9b3214d422d7EFe71465A0915e6D164f360d"
},
"targets": {
"value": [
{
"value": "0x9c263585E7cEa3A89E61c491Dc02fF283906FbF0"
}
]
},
"values": {
"value": [
{
"value": "0"
}
]
},
"signatures": {
"value": [
{
"value": ""
}
]
},
"calldatas": {
"value": [
{
"value": "0x"
}
]
},
"voteStart": {
"value": "1750112158"
},
"voteEnd": {
"value": "1750716958"
},
"description": {
"value": "# [TEST-TPP] Guardian Veto Rehearsal 2025-Q2\n# \\[TEST-TPP] Guardian Veto Rehearsal 2025-Q2\n\n**Token Program Proposal Summary**\n\n| Item | Description |\n| -------------------- | ------------------------------------------------------------------------------------------------------- |\n| Title | Guardian Veto Rehearsal 2025-Q2 |\n| Proposal Type | TPP |\n| One Sentence Summary | This proposal forms part of a Guardian veto rehearsal to test a production Token Program Proposal veto. |\n| Proposal Author | ZKsync Association |\n| Proposal Sponsor | Keating, ScopeLift |\n| Date Created | 2025-JUNE-02 |\n| Version | 1.0 |\n| Summary of Action | This proposal has no onchain actions |\n| Link to Forum | https://forum.zknation.io/t/tpp-t1-guardian-veto-rehearsal-1-2025/695 |\n| Link to Contracts | Not Applicable |\n\n***\n\n### :::: NO VOTE FROM DELEGATES REQUIRED ::::

\n\n### Summary\n\nThis proposal coordinates a production onchain veto rehearsal for Guardians on the ZKsync Era Token Governor. It simulates a real-world scenario in which a Guardian veto is required, ensuring veto functionality, multisig coordination, and interfaces perform as expected.\n\n***\n\n### Abstract\n\nGuardian powers have been live since the launch of ZKsync governance in September 2024. As of today, no proposals have yet required a formal veto. To ensure operational readiness, the Governance Team is organizing regular rehearsals. This rehearsal will test the Guardian veto path on a **Token Program Proposal (TPP)**.\n\nThe rehearsal follows the complete process: proposal submission, veto initiation, multisig signature collection, execution, and validation via the Tally interface.\n\nThis exercise helps ensure ZKsync’s governance infrastructure is functional, transparent, and trustworthy in moments of real escalation.\n\n***\n\n### Impact\n\nThis rehearsal will validate the following:\n\n* Guardian veto functionality on the Token Governor contract\n* Signature gathering and quorum on the Guardian multisig\n* Execution reliability through the [verify.zknation.io](https://verify.zknation.io/) interface\n* Proper UI state change on Tally and governance dashboards\n\nIt also reinforces cross-role coordination between proposers, Guardians, and interfaces.\n\nNo ZK tokens will be minted, burned, or reallocated during this process. This is a simulation only.\n\n***\n\n### Plan\n\n* **June 2, 2025 – 15:00 CET**: Draft proposal posted on ZKsync Governance Forum\n* **June 9, 2025 – 15:00 CET**: Test proposal submitted on ZKsync Governance Portal\n* **June 20, 2025 – 18:00 CET**: Guardian veto execution deadline"
}
}By Ethereum Governance • 6/9/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22669101
- Timestamp: 6/9/2025, 7:28:11 PM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeExecuted
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0x05adc89edd6f69070a5902bfdd96e7d9052d8bb1d2b86bfcb0b3c2c7160141ef"
}
}By Ethereum Governance • 6/5/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22638611
- Timestamp: 6/5/2025, 1:09:35 PM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeApprovedBySecurityCouncil
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0x05adc89edd6f69070a5902bfdd96e7d9052d8bb1d2b86bfcb0b3c2c7160141ef"
}
}By ZKSync Governance • 5/29/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 61081894
- Timestamp: 5/29/2025, 9:11:33 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallExecuted
- Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714
Event Data
{
"id": {
"value": "0xd4d8e60acc73be7163cd8f658357f0faecdb2a640b98002805b57ec6a4854689"
},
"index": {
"value": "0"
},
"target": {
"value": "0x0000000000000000000000000000000000008008"
},
"value": {
"value": "0"
},
"data": {
"value": "0x62f84b24...00000000"
}
}By ZKSync Governance • 5/29/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 61081894
- Timestamp: 5/29/2025, 9:11:33 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExecuted
- Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "54063168049426383294336598998322383147338444177076559098597792110160570100155"
}
}By ZKSync Governance • 5/29/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 61081885
- Timestamp: 5/29/2025, 9:11:18 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExecuted
- Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "97689115420129047109255183628089175185608660755000395855946331923921270505453"
}
}By ZKSync Governance • 5/29/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 61081885
- Timestamp: 5/29/2025, 9:11:18 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallExecuted
- Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714
Event Data
{
"id": {
"value": "0x1301dc77ca2cc3cc78b43f01311e7cd3c6f28bb8fa340ce04a0bb2a311101966"
},
"index": {
"value": "0"
},
"target": {
"value": "0x0000000000000000000000000000000000008008"
},
"value": {
"value": "0"
},
"data": {
"value": "0x62f84b24...00000000"
}
}By ZKSync Governance • 5/29/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 61078376
- Timestamp: 5/29/2025, 7:09:54 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallScheduled
- Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714
Event Data
{
"id": {
"value": "0xd4d8e60acc73be7163cd8f658357f0faecdb2a640b98002805b57ec6a4854689"
},
"index": {
"value": "0"
},
"target": {
"value": "0x0000000000000000000000000000000000008008"
},
"value": {
"value": "0"
},
"data": {
"value": "0x62f84b24...00000000"
},
"predecessor": {
"value": "0x0000000000000000000000000000000000000000000000000000000000000000"
},
"delay": {
"value": "0"
}
}By ZKSync Governance • 5/29/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 61077711
- Timestamp: 5/29/2025, 6:48:54 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallScheduled
- Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714
Event Data
{
"id": {
"value": "0x1301dc77ca2cc3cc78b43f01311e7cd3c6f28bb8fa340ce04a0bb2a311101966"
},
"index": {
"value": "0"
},
"target": {
"value": "0x0000000000000000000000000000000000008008"
},
"value": {
"value": "0"
},
"data": {
"value": "0x62f84b24...00000000"
},
"predecessor": {
"value": "0x0000000000000000000000000000000000000000000000000000000000000000"
},
"delay": {
"value": "0"
}
}By ZKSync Governance • 5/27/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60969577
- Timestamp: 5/27/2025, 6:53:50 AM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExecuted
- Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "47039743821393144264923138033474021479144633689510868538815755013680786377936"
}
}By ZKSync Governance • 5/27/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60969577
- Timestamp: 5/27/2025, 6:53:50 AM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallExecuted
- Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d
Event Data
{
"id": {
"value": "0x7608f365d6e1e003a6951864ac58e6136f48d130f775bceda38cb4ad349eb3cb"
},
"index": {
"value": "1"
},
"target": {
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
"value": {
"value": "0"
},
"data": {
"value": "0x2f2ff15d...29be9db6"
}
}By ZKSync Governance • 5/26/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60943761
- Timestamp: 5/26/2025, 2:31:02 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExtended
- Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "97689115420129047109255183628089175185608660755000395855946331923921270505453"
},
"extendedDeadline": {
"value": "1748529062"
}
}By ZKSync Governance • 5/26/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60943678
- Timestamp: 5/26/2025, 2:28:10 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExtended
- Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "54063168049426383294336598998322383147338444177076559098597792110160570100155"
},
"extendedDeadline": {
"value": "1748528890"
}
}By ZKSync Governance • 5/25/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60910724
- Timestamp: 5/25/2025, 5:42:19 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExecuted
- Contract Address:0xEEEa...b1600xEEEa739a8b6fB1b8f703E23C9Be03CeeA643b160
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "103259976736823883300634095721999212673593591495252565610431467445162492146868"
}
}By ZKSync Governance • 5/25/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60910698
- Timestamp: 5/25/2025, 5:41:37 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExecuted
- Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "42065487101304397091733612230088767526898725546086370988745501935513610356311"
}
}By ZKSync Governance • 5/25/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60910698
- Timestamp: 5/25/2025, 5:41:37 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallExecuted
- Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d
Event Data
{
"id": {
"value": "0x630cadf3bad24c88f5445d5e7725a84b6667789cee4a6afb250c5362d9aab92e"
},
"index": {
"value": "3"
},
"target": {
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
"value": {
"value": "0"
},
"data": {
"value": "0xd547741f...0107d33a"
}
}By ZKSync Governance • 5/23/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60830845
- Timestamp: 5/23/2025, 5:06:00 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallScheduled
- Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d
Event Data
{
"id": {
"value": "0x7608f365d6e1e003a6951864ac58e6136f48d130f775bceda38cb4ad349eb3cb"
},
"index": {
"value": "0"
},
"target": {
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
"value": {
"value": "0"
},
"data": {
"value": "0x2f2ff15d...b601cfd8"
},
"predecessor": {
"value": "0x0000000000000000000000000000000000000000000000000000000000000000"
},
"delay": {
"value": "259200"
}
}By ZKSync Governance • 5/22/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60783261
- Timestamp: 5/22/2025, 4:14:59 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallScheduled
- Contract Address:0xe5d2...9c3d0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d
Event Data
{
"id": {
"value": "0x630cadf3bad24c88f5445d5e7725a84b6667789cee4a6afb250c5362d9aab92e"
},
"index": {
"value": "0"
},
"target": {
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
"value": {
"value": "0"
},
"data": {
"value": "0xd547741f...d30a82b0"
},
"predecessor": {
"value": "0x0000000000000000000000000000000000000000000000000000000000000000"
},
"delay": {
"value": "259200"
}
}By ZKSync Governance • 5/22/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60768701
- Timestamp: 5/22/2025, 9:16:47 AM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallScheduled
- Contract Address:0xC9E4...428a0xC9E442574958f96C026DeF9a50C3236cab17428a
Event Data
{
"id": {
"value": "0x803b0617b3e6780ae1d0f36a4fcc6f44e2f72a6f93d8490c43f144b47c9ab2e0"
},
"index": {
"value": "0"
},
"target": {
"value": "0xEa88046C61506480e8B69fFB4A5Dd8F80eC721b6"
},
"value": {
"value": "0"
},
"data": {
"value": "0x"
},
"predecessor": {
"value": "0x0000000000000000000000000000000000000000000000000000000000000000"
},
"delay": {
"value": "259200"
}
}By ZKSync Governance • 5/16/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60512795
- Timestamp: 5/16/2025, 6:58:41 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalCreated
- Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "97689115420129047109255183628089175185608660755000395855946331923921270505453"
},
"proposer": {
"value": "0xc11846203b0121C28285FA89EAd2249AafffaD2C"
},
"targets": {
"value": [
{
"value": "0x0000000000000000000000000000000000008008"
}
]
},
"values": {
"value": [
{
"value": "0"
}
]
},
"signatures": {
"value": [
{
"value": ""
}
]
},
"calldatas": {
"value": [
{
"value": "0x62f84b24...00000000"
}
]
},
"voteStart": {
"value": "1747681121"
},
"voteEnd": {
"value": "1748285921"
},
"description": {
"value": "# [ZIP-10] Activate ZK Gateway as a Settlement Layer\n| **Title** | Activate ZK Gateway as a Settlement Layer |\n| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Proposal Type** | ZIP |\n| **One Sentence Summary:** | This proposal aims to whitelist ZK Gateway chain as a settlement layer for the Elastic Network, paving the way to facilitate fast interop by providing a layer for cheap batch settlement and as well as quick communication between ZK Chains. |\n| **Proposal Author** | Matter Labs |\n| **Proposal Sponsor:** | Cyfrin |\n| **Date Created:** | May 2025 |\n| **Version** | v1 |\n| **Summary of Action** | This proposal will whitelist ZK Gateway chain as a settlement layer for Elastic Network. |\n| **Link to contracts** | https://github.com/matter-labs/era-contracts/tree/release-v27 |\n\n# **\\[ZIP-10] Activate ZK Gateway as a Settlement Layer**\n\n# **Abstract**\n\nZIP-10 builds on the groundwork laid by [ZIP-6 Prepare ZKsync for ZK Gateway](https://www.tally.xyz/gov/zksync/proposal/67712324710515983914473127418805437707715095849437613773846173900686148862581?govId=eip155:324:0x76705327e682F2d96943280D99464Ab61219e34f), which shipped V26 of ZKsync.\n\nZIP-10 approves ZK Gateway as an optional shared settlement layer for the Elastic Network. ZK Gateway aims to enhance the efficiency of batch settlements across ZK Chains, reducing settlement costs and stabilizing pricing for users, especially for ZK Chains that do not depend on Ethereum for DA. In addition, ZK Gateway will facilitate future interopability across the Elastic Network and provide even cheaper pricing in the future, once optimized precompiles are available in the next release.\n\n# **Motivation**\n\nThe motivations for this proposal are:\n\n1. **Cheaper settlement costs**. When settling on top of Gateway, ZK Chains are able to utilize cheaper settlement costs for settling their batches (i.e. committing, proving and executing those), which will translate into cheaper and more stable pricing for users, particularly in future releases when precompiles are available.\n2. **Future interop facilitations.** As a result of the above, ZK Chains will be able to settle batches faster, allowing for faster trustless interop. Also, ZK Gateway is able to serve as a communication layer between ZK Chains, paving the way to seamless interop with additional security requirements.\n\n# **Specification**\n\nZIP-10 is a continuation of efforts started with [ZIP-6](https://www.tally.xyz/gov/zksync/proposal/67712324710515983914473127418805437707715095849437613773846173900686148862581?govId=eip155:324:0x76705327e682F2d96943280D99464Ab61219e34f). With the approval of ZIP-6, V26 was implemented on the Elastic Network. The main feature of V26 was the support of shared settlement layers for the Elastic Network. ZIP-10 does not introduce new code changes in addition to ZIP-6. Instead, ZIP-10 focuses on whitelisting the ZK Gateway chain as an optional shared settlement layer.\n\n[Here](https://github.com/matter-labs/era-contracts/blob/release-v27/docs/gateway/overview.md) you can read more about how settlement layers as well as how the ZK Chains would be able to migrate on top of the ZK Gateway in the future.\n\nNote, the decision to migrate on top of ZK Gateway is an optional choice which can be made by each individual ZK ChainAdmin. Also, there is always an option to opt out of using Gateway.\n\nThe ZK Gateway has been deployed as a ZK Chain, with chainID 9075. ZK Gateway uses the ZK token as the base token and maintains the same security properties as ZKsync Era. ZK Gateway is also a permanent rollup, i.e. regardless of the actions of the ChainAdmin it will always use Ethereum as its DA layer.\n\nFor simplicity, in this release, the ZK Gateway is just a chain with the same capabilities as a standard ZK Chain. In the future, the chain can be upgraded to a more specialized version. To prevent unintended usage and to make this future migration easier, deploying of contracts inside the ZK Gateway will only be available under a whitelist.\n\nAs part of the ZIP execution, governance will complete the following actions:\n\n1. Call `Bridgehub.registerSettlementLayer` to register this chain as a valid settlement layer.\n2. Do an L1->GW transaction to whitelist a `ChainTypeManager` on top of Gateway to manage the ZK Chains that settle on top of it.\n3. Do the calls to [Bridgehub](https://etherscan.io/address/0x303a465B659cBB0ab36eE643eA362c509EEb5213) and [CTMDeploymentTracker](https://etherscan.io/address/0x6078F6B379f103de1Aa912dc46bb8Df0c8809860) to ensure that everything is set up to facilitate future [ZK chain migrations](https://github.com/matter-labs/era-contracts/blob/release-v27/docs/gateway/chain_migration.md) on top of ZK Gateway.\n\n# **Rationale**\n\nThis upgrade introduces a new shared settlement network in an incremental way, while already providing value for ZK Chains of the Elastic Network. It will give an opportunity for ZK Chains to receive more stable batch settling pricing, while allowing prices that are much cheaper than L1 starting with a future upgrade, that will introduce more efficient cryptographic precompiles.\n\nReusing an existing ZK Chain architecture for a shared settlement layer allows ZK Chains to enjoy the benefits faster while relying on already battle-tested codebase that is used by all ZK Chains.\n\n# **Backwards Compatibility**\n\nNo backwards compatibility issues.\n\n# **Security Considerations**\n\nAll the existing code has been audited as a part of the previous ZIPs.\n\nDuring the initial release Matter Labs will be the sole sequencer of the ZK Gateway with planned transition to a decentralized setting over time."
}
}By ZKSync Governance • 5/16/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60508832
- Timestamp: 5/16/2025, 4:50:21 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExtended
- Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "47039743821393144264923138033474021479144633689510868538815755013680786377936"
},
"extendedDeadline": {
"value": "1748019021"
}
}By ZKSync Governance • 5/15/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60460657
- Timestamp: 5/15/2025, 3:35:31 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExtended
- Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "42065487101304397091733612230088767526898725546086370988745501935513610356311"
},
"extendedDeadline": {
"value": "1747928131"
}
}By ZKSync Governance • 5/15/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60445689
- Timestamp: 5/15/2025, 8:12:48 AM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExtended
- Contract Address:0xEEEa...b1600xEEEa739a8b6fB1b8f703E23C9Be03CeeA643b160
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "103259976736823883300634095721999212673593591495252565610431467445162492146868"
},
"extendedDeadline": {
"value": "1747901568"
}
}By ZKSync Governance • 5/6/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60026326
- Timestamp: 5/6/2025, 4:08:05 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalCreated
- Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "42065487101304397091733612230088767526898725546086370988745501935513610356311"
},
"proposer": {
"value": "0x4e3D9399C28c724293dd545225Ec843Ac4c9e953"
},
"targets": {
"value": [
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
}
]
},
"values": {
"value": [
{
"value": "0"
},
{
"value": "0"
},
{
"value": "0"
},
{
"value": "0"
},
{
"value": "0"
},
{
"value": "0"
},
{
"value": "0"
},
{
"value": "0"
},
{
"value": "0"
},
{
"value": "0"
}
]
},
"signatures": {
"value": [
{
"value": ""
},
{
"value": ""
},
{
"value": ""
},
{
"value": ""
},
{
"value": ""
},
{
"value": ""
},
{
"value": ""
},
{
"value": ""
},
{
"value": ""
},
{
"value": ""
}
]
},
"calldatas": {
"value": [
{
"value": "0xd547741f...d30a82b0"
},
{
"value": "0xd547741f...3954c2ec"
},
{
"value": "0xd547741f...90ffc4ab"
},
{
"value": "0xd547741f...0107d33a"
},
{
"value": "0xd547741f...f8c2c392"
},
{
"value": "0xd547741f...8a58cbcc"
},
{
"value": "0xd547741f...c6e09ba9"
},
{
"value": "0xd547741f...174b8dcf"
},
{
"value": "0xd547741f...8d2f5964"
},
{
"value": "0xd547741f...edca40a9"
}
]
},
"voteStart": {
"value": "1747152485"
},
"voteEnd": {
"value": "1747757285"
},
"description": {
"value": "# [TPP-4] Deactivate Capped Minters for TPP-1 Ignite Program\n| Title | Deactivate Capped Minters for TPP-1 Ignite Program |\n| ------------------------ | ------------------------------------------------------------------------------------- |\n| **Proposal Type** | TPP |\n| **One Sentence Summary** | This proposal removes the minter role from all Ignite Program capped minters. |\n| **Proposal Author** | Baptiste (Merkl) |\n| **Proposal Sponsor** | Baki |\n| **Submitted onchain** | 2025-05-06 |\n| **Version** | v1 |\n| **Summary of Action** | Revoke Minter Role from all Ignite Program capped minters to prevent further minting. |\n| **Link to forum post** | https://forum.zknation.io/t/tpp-x-deactivate-capped-minters-for-tpp1-ignite/665 |\n| **Link to contracts** | n/a |\n\n### Simple Summary\n\nThis proposal removes the minter role from Ignite Program capped minters.\n\n### Abstract\n\nNow that the Ignite Program has concluded, the Token Assembly will ensure that no remaining unminted supply in the affiliated program or admin capped minters can be minted. This proposal includes the call data required to revoke the minter role from all capped minters linked to the Ignite Program.\n\n### Motivation\n\n[Cancellation of Token Programs](https://docs.zknation.io/zksync-governance-proposals/token-program-proposals-tpps#token-program-cancellation) using the ZkCappedMinterV1 can be done in one of two ways:\n\n1. Sending the admin multisig control to a burn address; or\n2. Revoking the Minter Role via a Token Assembly proposal.\n\nThe DSC multisig is required to remain active to complete unclaimed token reallocations. As such, a Token Assembly-approved proposal is necessary to revoke the Minter Role from Ignite capped minters.\n\nPlease note that the limitations considered here are specific to the Ignite Program deployed with ZkCappedMinterV1 contracts.\n\nFor future token programs, the ZkCappedMinterV2 contracts allow the deactivation of a ZkCappedMinterV2 through the admin controlled `cancel()` function. Please refer to the following [documentation](https://forum.zknation.io/t/zk-capped-minter-v2-nested-minters-start-time-expiration-pause-and-cancel/417) for more information.\n\n### Impact\n\nThis proposal ensures the safety and security of the remaining unminted supply in each capped minter. Neither the DeFi Steering Committee multisig or any other actor who would be able to gain access the multisig would be able to mint any further tokens from the Ignite Program Capped Minters.\n\n### Mechanic\n\nThis proposal would include the `revokeRole()` call on each of the following Ignite Program capped minters.\n\n| Capped Minter | Address | Total Cap (ZK) | Remaining Cap (ZK) |\n| ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | -------------- | ------------------ |\n| IP-ZK-Distro-Minter-1 | [0xe546AEaaC57584da7554e7F88154DeDAD30A82b0](https://explorer.zksync.io/address/0xe546AEaaC57584da7554e7F88154DeDAD30A82b0) | 50,000,000 | ~11,492,378 |\n| IP-ZK-Distro-Minter-2 | [0x11791c6249631555cEb75CB39128789E3954c2EC](https://explorer.zksync.io/address/0x11791c6249631555cEb75CB39128789E3954c2EC) | 50,000,000 | ~37,582,899 |\n| IP-ZK-Distro-Minter-3 | [0x3BC3f64d084bE6d3336f10340DC8424290FFc4ab](https://explorer.zksync.io/address/0x3BC3f64d084bE6d3336f10340DC8424290FFc4ab) | 50,000,000 | 50,000,000 |\n| IP-ZK-Distro-Minter-4 | [0xDa2fBE31Fd47Af741bdB3dBC4eb662dA0107D33a](https://explorer.zksync.io/address/0xDa2fBE31Fd47Af741bdB3dBC4eb662dA0107D33a) | 50,000,000 | 50,000,000 |\n| IP-ZK-Distro-Minter-5 | [0x6b689B93B368c7C25E6e5ecaeAb23C11F8C2c392](https://explorer.zksync.io/address/0x6b689B93B368c7C25E6e5ecaeAb23C11F8C2c392) | 50,000,000 | 50,000,000 |\n| IP-ZK-Distro-Minter-6 | [0x2CC6c7b1a59A23fB3faCAFe4A3791C5c8A58Cbcc](https://explorer.zksync.io/address/0x2CC6c7b1a59A23fB3faCAFe4A3791C5c8A58Cbcc) | 50,000,000 | 50,000,000 |\n| IP-ZK-Admin-Minter-OBL | [0xD375A20d93C2F7C6a83B19C5ae153cF2C6e09ba9](https://explorer.zksync.io/address/0xD375A20d93C2F7C6a83B19C5ae153cF2C6e09ba9) | 4,995,500 | 2,811,028 |\n| IP-ZK-Admin-Minter-Merkl | [0x2ADa5C15BC4FEE97EC2463ce4F8E4557174B8Dcf](https://explorer.zksync.io/address/0x2ADa5C15BC4FEE97EC2463ce4F8E4557174B8Dcf) | 4,634,500 | 3,707,600 |\n| IP-ZK-Admin-Minter-DSC | [0x4E86e74237Eb1f9432810eB5ab5861368d2f5964](https://explorer.zksync.io/address/0x4E86e74237Eb1f9432810eB5ab5861368d2f5964) | 3,250,000 | 2,890,000 |\n| IP-ZK-Admin-Minter-Supporting-Services | [0x178bFf5A197FB4499526D04Db602C45cEDCA40a9](https://explorer.zksync.io/address/0x178bFf5A197FB4499526D04Db602C45cEDCA40a9) | 12,120,000 | 18,230,349 |\n| **Total Amount of Unminted ZK Remaining in Capped Minters** | | 325,000,000 | ~276,714,254 |\n\n### Plan & Accountability\n\nIf the proposal is passed, there will be no further action or oversight required to prevent further minting from the Ignite Program capped minters.\n\n### Other Information\n\nOriginal Proposal: [\\[TPP-001\\] ZKsync Ignite Program: Creating a Liquidity Hub for ZKsync](https://vote.zknation.io/dao/proposal/61143334896738427838139044418897411872404555684850233057602201527014096413671?govId=eip155:324:0x10560f8B7eE37571AD7E3702EEb12Bc422036E89)\n\nProgram Cancellation: [ZKsync Ignite Cancellation](https://forum.zknation.io/t/zksync-ignite-cancellation/612)"
}
}By ZKSync Governance • 5/6/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 60021880
- Timestamp: 5/6/2025, 1:51:42 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalCreated
- Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "47039743821393144264923138033474021479144633689510868538815755013680786377936"
},
"proposer": {
"value": "0xc11846203b0121C28285FA89EAd2249AafffaD2C"
},
"targets": {
"value": [
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
}
]
},
"values": {
"value": [
{
"value": "0"
},
{
"value": "0"
}
]
},
"signatures": {
"value": [
{
"value": ""
},
{
"value": ""
}
]
},
"calldatas": {
"value": [
{
"value": "0x2f2ff15d...b601cfd8"
},
{
"value": "0x2f2ff15d...29be9db6"
}
]
},
"voteStart": {
"value": "1747144302"
},
"voteEnd": {
"value": "1747749102"
},
"description": {
"value": "# [TPP-3] ZIP Audit Reimbursement Program (ZARP)\n# \\[TPP-3] ZIP Audit Reimbursement Program (ZARP)\n\n| **Proposal Type** | TPP |\n| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **One Sentence Summary** | An annual program valued at $5m USD (89,285,714 ZK) to reimburse security audit costs for successfully executed ZKsync Improvement Proposals (ZIPs) in 2025, ensuring high security standards for ZKsync protocol development. |\n| **Proposal Author** | ZKsync Foundation |\n| **Proposal Sponsor** | Cyfrin |\n| **Submitted Onchain** | 2025-05-06 |\n| **Version** | v1 |\n| **Summary of Action** | This proposal establishes a ZIP Audit Reimbursement Program valued at $5m USD in ZK (89,285,714 ZK) to reimburse developers for audit costs associated with successfully implemented ZIPs. The program will be funded through the ZK token minter and payments will be distributed autonomously upon the successful execution of a given ZIP. |\n| **Total ZK Requested** | 89,285,714 ZK |\n| **Link to Forum Post** | https://forum.zknation.io/t/tpp-3-zip-audit-reimbursement-program-zarp/636 |\n| **Link to Contracts** | ZarpMain: [0x51E818785dEa065D392ac21F04E9cac5B601Cfd8](https://explorer.zksync.io/address/0x51E818785dEa065D392ac21F04E9cac5B601Cfd8#contract#read), ZarpRetro: [0x70F6998FC0c492d9DD08b1105259252329be9Db6](https://explorer.zksync.io/address/0x70F6998FC0c492d9DD08b1105259252329be9Db6#contract#read) |\n\n## Abstract\n\nThe ZIP Audit Reimbursement Program (ZARP) allocates $5m USD in ZK over the 2025 calendar year to increase security standards across the ZKsync protocol by reimbursing the costs associated with third-party audits of successful ZIPs. This program will ensure that ZIP developers strive for exceptional security audit standards, resulting in secure and robust contributions to the ZKsync protocol.\n\n## Motivation\n\nThis proposal aligns with [GAP 001: ZKsync Token Program Priorities 2025](https://www.tally.xyz/gov/zksync/proposal/13823050748058617424077595486689751986818771098977300222700522842013613046754?govId=eip155:324:0x496869a7575A1f907D1C5B1eca28e4e9E382afAb), which emphasizes the importance of accelerating ZKsync protocol development. As security is a foundational pillar of protocol integrity, this program directly supports the \"**Secure the Protocol**\" priority within GAP 001.\n\n## Impact\n\nThis program directly contributes to securing the ZKsync protocol, aligning with the [ZKsync Governance North Star](https://docs.zknation.io/zk-nation/zksync-governance-system-north-star) metric of protecting assets, builders, and the community from adversarial actors. By ensuring that all ZIPs undergo thorough security audits, the program mitigates vulnerabilities and strengthens the resilience of the protocol, removing the financial burden of security audits.\n\n### Primary Goals & Metrics\n\n| **Goal** | **Metric** | **Target** |\n| --------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------ |\n| Secure the Protocol | % of successfully implemented ZIPs that receive audits | 100% of eligible ZIPs audited |\n| Secure the Protocol | Number of security incidents related to newly implemented ZIPs that require an emergency upgrade to resolve | 0 incidents |\n| Public Accountability | Number of reimbursements publicly documented | 100% of reimbursements tracked |\n\n## Token Mechanic\n\nThis Token Program Proposal (TPP) approves the creation of two capped minters to fund audit reimbursements for ZIPs executed in 2025. The total value of the two capped minters is 89,285,714 ZK, which is the ZK token value of $5m USD based on the 30-day average from 27 April 2025. An overview of the two capped minters is set out below:\n\n1. `ZarpMain` – A general-purpose capped minter for ZIPs executed between May 1 and December 31, 2025. A total of 49,810,714 ZK may be minted from `ZarpMain`. Each ZIP will request its own allocation from this minter.\n2. `ZarpRetro` – A capped minter to reimburse audit costs for ZIPs approved by the Token Assembly between January 1 and April 30, 2025. A total of 39,475,000 ZK may be minted from `ZarpRetro`.\n\n\n\n## 1. `ZarpMain`: Future Audit Reimbursements (Q2 - Q4, 2025)\n\n`ZarpMain` is a capped minter that will fund audit reimbursements for any developer who submits a successfully executed ZIP on ZKsync between May 1, 2025 and December 31, 2025. Any ZIP author is eligible to claim audit reimbursements by following the outlined process, supporting the decentralization of protocol development. Developers will deploy a nested “child” capped minter to be able to draw from this main capped minter with successful protocol upgrade execution.\n\n### `ZarpMain` Capped Minter Parameters\n\n| Parameter | Value |\n| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |\n| **Name** | ZarpMain |\n| **Contract Address** | [0x51E818785dEa065D392ac21F04E9cac5B601Cfd8](https://explorer.zksync.io/address/0x51E818785dEa065D392ac21F04E9cac5B601Cfd8#contract#read) |\n| **Admin** | [Protocol Governor Timelock](https://explorer.zksync.io/address/0x085b8B6407f150D62adB1EF926F7f304600ec7149) |\n| **Target** | [ZK Token](https://explorer.zksync.io/address/0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E) |\n| **Cap** | 49,810,714 ZK |\n| **Start Time** | 19 May 2025 |\n| **End Time** | 31 January 2026 |\n| **Minter Role** | N/A (child minters who assume the MINTER role are deployed per ZIP) |\n\n### Eligibility Criteria\n\nTo be eligible for reimbursement:\n\n* The ZIP must be successfully executed on ZKsync between May 1 and December 31, 2025.\n* The ZIP must include a third-party audit from a recognized security firm.\n* Audit invoice(s) must be submitted for verification to the ZKsync Security Council via direct message on the governance forum, before the ZIP is submitted onchain.\n\nReimbursements cover audit fees, formal verification costs, and code competitions. They do not cover ZIP development labor, travel, or other indirect expenses. A given audit may only be reimbursed once.\n\n### Claim Process\n\nTo claim reimbursement through `ZarpMain`, ZIP authors must complete the following steps before onchain submission of the relevant ZIP:\n\n1. Deploy a child capped minter with the following parameters (see [Capped Minter V2](https://forum.zknation.io/t/zk-capped-minter-v2-nested-minters-start-time-expiration-pause-and-cancel/417) for deployment instructions):\n\n| Parameter | Value |\n| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Admin** | [Protocol Governor Timelock](https://explorer.zksync.io/address/0x085b8B6407f150D62adB1EF926F7f304600ec7149) |\n| **Target** | `ZarpMain` |\n| **Cap** | Amount of ZK matching the reimbursement request calculated using the 30-day average of the price from the date the child capped minter is deployed. |\n| **Start Time** | 30 days after the expected protocol upgrade approval date |\n| **End Time** | 31 January 2026 |\n\nPlease reach out to Gov Team for support creating child capped minters.\n\n2. In the ZIP draft posted on the governance forum, include:\n\n* Link to the audit report\n* Link to the deployed child capped minter contract\n\n3. In the onchain ZIP submission, include calldata to:\n\n* Grant MINTER role:\n 1. on the parent capped minter (`ZarpMain`) to the child capped minter; and\n 2. on the child capped minter to the ZIP developer\n* Grant PAUSER role on the child capped minter to the ZKsync Security Council on ZKsync Era ([0xfFB6126FF8401665081b771bB11cCD0e09f95D5A](https://explorer.zksync.io/address/0xfFB6126FF8401665081b771bB11cCD0e09f95D5A))\n\n\n\nIf the ZIP passes the Token Assembly vote, the child minter’s MINTER role will become active after a 30-day buffer. During this time, the Security Council will verify the audit details if it has not already done so. If necessary, the Security Council may pause the minter using their PAUSER role, preventing misuse of funds.\n\n## 2. `ZarpRetro`: Past Audit Reimbursement (Q1, 2025)\n\n`ZarpRetro` is a capped minter used to reimburse audit costs for ZIPs approved by the Token Assembly prior to April 30, 2025. Any ZIP author is eligible for retroactive reimbursement. Matter Labs has been the only developer to submit protocol upgrades to date. As a result, Matter Labs is the sole claimant under the `ZarpRetro` capped minter.\n\n### `ZarpRetro` Capped Minter Parameters\n\n| Parameter | Value |\n| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **Name** | ZarpRetro |\n| **Contract Address** | [`0x70F6998FC0c492d9DD08b1105259252329be9Db6`](https://explorer.zksync.io/address/0x70F6998FC0c492d9DD08b1105259252329be9Db6#contract#read) |\n| **Admin** | Matter Labs Multisig ([`0xb84cFd9EBA97d991afa2E7B76b900804eE911Ab7`](https://app.safe.global/settings/setup?safe=zksync:0xb84cFd9EBA97d991afa2E7B76b900804eE911Ab7)) |\n| **Target** | [ZK Token](https://explorer.zksync.io/address/0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E) |\n| **Cap** | 39,475,000 ZK |\n| **Start Time** | 19 May 2025 |\n| **End Time** | 31 January 2026 |\n| **Minter Role** | \\[Admin to confirm post-execution] |\n\nThe ZKsync Security Council has reviewed (or will review) the audit invoices and reports for ZIPs approved prior to 30 April 2025 to confirm eligibility.\n\nThe total value of the ZarpRetro Capped Minter is $2,210,600 USD. Using the 30-day average price of ZK from 27 April 2025, this amounts to 39,475,000 ZK tokens, which is the cap of the ZarpRetro Capped Minter.\n\n### Summary of Retro Audit Reimbursements\n\n| ZIP | Amount Claimed (USD) |\n| ----------------------------------------------------- | -------------------- |\n| ZIP-3 Protocol Defense | $91,440 |\n| ZIP-6 Gateway Prep | $1,490,540 |\n| ZIP-9 EVM Emulator | $628,620 |\n| **Total USD** | **$2,210,600** |\n| **Total ZK** <small>at 0.056 (30-day average)</small> | **39,475,000** |\n\n### Eligibility\n\nAll ZIPs approved by the Token Assembly prior to 30 April 2025 were developed by Matter Labs. As such, Matter Labs will define the MINTER address for the `ZARPRetro` capped minter.\n\nDetails of audit reimbursements being claimed by Matter Labs are set out in the tables below.\n\n| ZIP | Auditor | $USD Claimed | Audit Report(s) |\n| ----- | ------------ | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| ZIP-3 | OpenZeppelin | $91,440 | [Protocol Defense Report](https://github.com/matter-labs/era-contracts/blob/main/audits/ZKsync%20Protocol%20Defense%20Audit%20-%20Final%20Report%20\\(Sept%202024\\).pdf) |\n| ZIP-6 | OpenZeppelin | $510,540 | [ZKsync Custom Asset Bridge Audit](https://github.com/matter-labs/era-contracts/blob/release-v26/audits/ZKsync%20Custom%20Asset%20Bridge%20Audit%20\\(OpenZeppelin\\).pdf) + [ZKChain Upgrades and Libraries Diff Audit](https://github.com/matter-labs/era-contracts/blob/release-v26/audits/ZKChain%20Upgrades%20and%20Libraries%20Diff%20Audit%20\\(OpenZeppelin\\).pdf) + [ZKChain & Gateway Upgrade Audit](https://github.com/matter-labs/era-contracts/blob/release-v26/audits/ZKsync%20ZKChain%20and%20Gateway%20Upgrade%20Audit%20\\(OpenZeppelin\\).pdf) + [ZKChain Release Candidate Audit](https://github.com/matter-labs/era-contracts/blob/release-v26/audits/ZKChain%20Release%20Candidate%20Audit%20\\(OpenZeppelin\\).pdf) |\n| ZIP-6 | Audittens | $380,000 | [Gateway Security Competition](https://github.com/Audittens/Audittens/blob/main/audit-reports/ZKsync%20Gateway%20Audit.pdf) |\n| ZIP-6 | Audittens | $100,000 | [Hyperchains Security Competition](https://github.com/Audittens/Audittens/blob/main/audit-reports/ZKsync%20Shared%20Bridge%20\\(USDC\\)%20Audit.pdf) |\n| ZIP-6 | Cyfrin | $500,000 | [CodeHawks Security Competition](https://codehawks.cyfrin.io/c/2024-10-zksync/submissions) |\n| ZIP-9 | OpenZeppelin | $628,620 | [EVM Equivalence Audit](https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync%20EVM%20Equivalence%20Audit.pdf) + [FFLONK Verifier Audit](https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync%20FFLONK%20Verifier%20Audit.pdf) + [FFLONK & EVM Emulator Diff Audit](https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync%20FFLONK%20and%20EVM%20Equivalence%20Diff%20Audit.pdf) |\n\nAll reimbursements claimed from the ZarpRetro capped have been reviewed and approved by the Security Council.\n\n### Claim Process\n\nAs the admin of the `ZarpRetro` capped minter, Matter Labs will be able to assign the minter role at their discretion that will be able to mint tokens in the `ZarpRetro` capped minter. The tokens are available to mint at any time until 31 January 2026.\n\n## Plan\n\n### **Measurement & Reporting**\n\n* **On-chain tracking**: The `ZarpMain` Capped Minter will record all disbursements, ensuring transparency.\n* **Quarterly governance updates**: The Security Council will publish status reports tracking disbursements and participation.\n* **End-of-year report**: A detailed impact analysis will be presented to the community.\n\n## Accountability Framework\n\n* The Security Council will review all reimbursement requests.\n* Conflicts of interest will be managed via a recusal policy.\n* All reimbursements are publicly documented for transparency.\n* Program impact is evaluated annually with Token Assembly input.\n\n## Participants\n\n* Security Council (responsible for oversight and pausing ineligible distributions).\n* ZIP developers and/or contributors (subject to KYC/KYB as per ZKsync Association policy)."
}
}By ZKSync Governance • 5/5/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 59987813
- Timestamp: 5/5/2025, 4:38:23 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalCreated
- Contract Address:0xb83F...57460xb83FF6501214ddF40C91C9565d095400f3F45746
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "37336317904360891872634439686262641429380301134230744013571346123315862024472"
},
"proposer": {
"value": "0xc11846203b0121C28285FA89EAd2249AafffaD2C"
},
"targets": {
"value": [
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
},
{
"value": "0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E"
}
]
},
"values": {
"value": [
{
"value": "0"
},
{
"value": "0"
}
]
},
"signatures": {
"value": [
{
"value": ""
},
{
"value": ""
}
]
},
"calldatas": {
"value": [
{
"value": "0x2f2ff15d...921277e5"
},
{
"value": "0x2f2ff15d...8a86af52"
}
]
},
"voteStart": {
"value": "1747067903"
},
"voteEnd": {
"value": "1747672703"
},
"description": {
"value": "# [TPP-3] ZIP Audit Reimbursement Program (ZARP)\n## \\[TPP-3] ZIP Audit Reimbursement Program (ZARP)\n\n| **Proposal Type** | TPP |\n| ------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| **One Sentence Summary** | An annual program valued at $5m USD (~89m ZK) to reimburse security audit costs for successfully executed ZKsync Improvement Proposals (ZIPs) in 2025, ensuring high security standards for ZKsync protocol development. |\n| **Proposal Author** | ZKsync Foundation |\n| **Proposal Sponsor** | Cyfrin |\n| **Submitted Onchain** | 2025-05-05 |\n| **Version** | v1 |\n| **Summary of Action** | This proposal establishes a ZIP Audit Reimbursement Program valued at $5m USD in ZK (~89m ZK) to reimburse developers for audit costs associated with successfully implemented ZIPs. The program will be funded through the ZK token minter and payments will be distributed autonomously upon the successful execution of a given ZIP. |\n| **Link to Forum Post** | https://forum.zknation.io/t/tpp-3-zip-audit-reimbursement-program-zarp/636 |\n| **Link to Contracts** | ZarpMain: [0xc117c6A6ad15799ce8e6912132E76baA921277e5](https://explorer.zksync.io/address/0xc117c6A6ad15799ce8e6912132E76baA921277e5#contract#contract-info), ZarpRetro: [0xEdE7012A5Fd6CB04318b6F8ca9A6dd508a86AF52](https://explorer.zksync.io/address/0xEdE7012A5Fd6CB04318b6F8ca9A6dd508a86AF52#contract) |\n\n## Abstract\n\nThe ZIP Audit Reimbursement Program (ZARP) allocates $5m USD in ZK over the 2025 calendar year to increase security standards across the ZKsync protocol by reimbursing the costs associated with third-party audits of successful ZIPs. This program will ensure that ZIP developers strive for exceptional security audit standards, resulting in secure and robust contributions to the ZKsync protocol.\n\n## Motivation\n\nThis proposal aligns with [GAP 001: ZKsync Token Program Priorities 2025](https://www.tally.xyz/gov/zksync/proposal/13823050748058617424077595486689751986818771098977300222700522842013613046754?govId=eip155:324:0x496869a7575A1f907D1C5B1eca28e4e9E382afAb), which emphasizes the importance of accelerating ZKsync protocol development. As security is a foundational pillar of protocol integrity, this program directly supports the \"**Secure the Protocol**\" priority within GAP 001.\n\n## Impact\n\nThis program directly contributes to securing the ZKsync protocol, aligning with the [ZKsync Governance North Star](https://docs.zknation.io/zk-nation/zksync-governance-system-north-star) metric of protecting assets, builders, and the community from adversarial actors. By ensuring that all ZIPs undergo thorough security audits, the program mitigates vulnerabilities and strengthens the resilience of the protocol, removing the financial burden of security audits.\n\n### Primary Goals & Metrics\n\n| **Goal** | **Metric** | **Target** |\n| --------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------ |\n| Secure the Protocol | % of successfully implemented ZIPs that receive audits | 100% of eligible ZIPs audited |\n| Secure the Protocol | Number of security incidents related to newly implemented ZIPs that require an emergency upgrade to resolve | 0 incidents |\n| Public Accountability | Number of reimbursements publicly documented | 100% of reimbursements tracked |\n\n## Token Mechanic\n\nThis Token Program Proposal (TPP) approves the creation of two capped minters to fund audit reimbursements for ZIPs executed in 2025. The total value of the two capped minters is 88,759,019 ZK, which is the ZK token value of $5m USD based on the 30-day average from 27 April 2025. An overview of the two capped minters is set out below:\n\n1. `ZarpMain` – A general-purpose capped minter for ZIPs executed between May 1 and December 31, 2025. A total of 49,516,882 ZK may be minted from `ZarpMain`. Each ZIP will request its own allocation from this minter.\n2. `ZarpRetro` – A capped minter to reimburse audit costs for ZIPs approved by the Token Assembly between January 1 and April 30, 2025. A total of 39,242,138 ZK may be minted from `ZarpRetro`.\n\n\n\n## 1. `ZarpMain`: Future Audit Reimbursements (Q2 - Q4, 2025)\n\n`ZarpMain` is a capped minter that will fund audit reimbursements for any developer who submits a successfully executed ZIP on ZKsync between May 1, 2025 and December 31, 2025. Any ZIP author is eligible to claim audit reimbursements by following the outlined process, supporting the decentralization of protocol development. Developers will deploy a nested “child” capped minter to be able to draw from this main capped minter with successful protocol upgrade execution.\n\n### `ZarpMain` Capped Minter Parameters\n\n**Name**: ZarpMain\n\n**Contract Address**: [0xc117c6A6ad15799ce8e6912132E76baA921277e5](https://explorer.zksync.io/address/0xc117c6A6ad15799ce8e6912132E76baA921277e5#contract#contract-info)\n\n**Admin**: [Protocol Governor Timelock](https://explorer.zksync.io/address/0x085b8B6407f150D62adB1EF926F7f304600ec7149)\n\n**Target**: [ZK Token](https://explorer.zksync.io/address/0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E)\n\n**Cap**: 49,516,882 ZK\n\n**Start Time**: 19 May 2025\n\n**End Time**: 31 January 2026\n\n**Minter Role**: N/A (child minters who assume the MINTER role are deployed per ZIP)\n\n### Eligibility Criteria\n\nTo be eligible for reimbursement:\n\n* The ZIP must be successfully executed on ZKsync between April 1 and December 31, 2025.\n* The ZIP must include a third-party audit from a recognized security firm.\n* Audit invoice(s) must be submitted for verification to the ZKsync Security Council via direct message on the governance forum, before the ZIP is submitted onchain.\n\nReimbursements cover audit fees, formal verification costs, and code competitions. They do not cover ZIP development labor, travel, or other indirect expenses. A given audit may only be reimbursed once.\n\n### Claim Process\n\nTo claim reimbursement through `ZarpMain`, ZIP authors must complete the following steps before onchain submission of the relevant ZIP:\n\n1. Deploy a child capped minter with the following parameters (see [Capped Minter V2](https://forum.zknation.io/t/zk-capped-minter-v2-nested-minters-start-time-expiration-pause-and-cancel/417) for deployment instructions):\n\n**Admin**: [Protocol Governor Timelock](https://explorer.zksync.io/address/0x085b8B6407f150D62adB1EF926F7f304600ec7149)\n\n**Target**: `ZarpMain`\n\n**Cap**: Amount of ZK matching the reimbursement request calculated using either the 7-day, 30-day, or 60-day average of the price from the date the child capped minter is deployed.\n\n**Start Time**: 30 days after the expected protocol upgrade approval date\n\n**End Time**: 31 January 2026\n\n2. In the ZIP draft posted on the governance forum, include:\n\n* Link to the audit report\n* Link to the deployed child capped minter contract\n\n3. In the onchain ZIP submission, include calldata to:\n\n* Grant MINTER role:\n 1. on the parent capped minter (`ZarpMain`) to the child capped minter; and\n 2. on the child capped minter to the ZIP developer\n* Grant PAUSER role on the child capped minter to the ZKsync Security Council on ZKsync Era ([0xfFB6126FF8401665081b771bB11cCD0e09f95D5A](https://explorer.zksync.io/address/0xfFB6126FF8401665081b771bB11cCD0e09f95D5A))\n\n\n\nIf the ZIP passes the Token Assembly vote, the child minter’s MINTER role will become active after a 30-day buffer. During this time, the Security Council will verify the audit details if it has not already done so. If necessary, the Security Council may pause the minter using their PAUSER role, preventing misuse of funds.\n\n## 2. `ZarpRetro`: Past Audit Reimbursement (Q1, 2025)\n\n`ZarpRetro` is a capped minter used to reimburse audit costs for ZIPs approved by the Token Assembly prior to April 30, 2025. Any ZIP author is eligible for retroactive reimbursement. Matter Labs has been the only developer to submit protocol upgrades to date. As a result, Matter Labs is the sole claimant under the `ZarpRetro` capped minter.\n\n### `ZarpRetro` Capped Minter Parameters\n\n**Name**: `ZarpRetro`\n\n**Contract Address**: [0xEdE7012A5Fd6CB04318b6F8ca9A6dd508a86AF52](https://explorer.zksync.io/address/0xEdE7012A5Fd6CB04318b6F8ca9A6dd508a86AF52)\n\n**Admin**: Matter Labs Multisig ([0xb84cFd9EBA97d991afa2E7B76b900804eE911Ab7](https://app.safe.global/home?safe=zksync:0xb84cFd9EBA97d991afa2E7B76b900804eE911Ab7))\n\n**Target**: [ZK Token](https://explorer.zksync.io/address/0x5A7d6b2F92C77FAD6CCaBd7EE0624E64907Eaf3E)\n\n**Cap**: 39,242,138 ZK\n\n**Start Time**: 19 May 2025\n\n**End Time**: 31 January 2026\n\n**Minter Role**: \\[Admin to confirm post-execution]\n\nThe ZKsync Security Council has reviewed (or will review) the audit invoices and reports for ZIPs approved prior to 30 April 2025 to confirm eligibility.\n\nThe total value of the ZarpRetro Capped Minter is $1,230,600 USD. Using the 30-day average price of ZK, this amounts to 71,374 ZK tokens, which is the cap of the ZarpRetro Capped Minter.\n\n### Summary of Retro Audit Reimbursements\n\n| ZIP | Amount Claimed (USD) |\n| ----------------------------------------------------- | -------------------- |\n| ZIP-3 Protocol Defense | $91,440 |\n| ZIP-6 Gateway Prep | $1,490,540 |\n| ZIP-9 EVM Emulator | $628,620 |\n| **Total USD** | **$2,210,600** |\n| **Total ZK** <small>at 0.058 (30-day average)</small> | **39,242,138** |\n\n### Eligibility\n\nAll ZIPs approved by the Token Assembly prior to 30 April 2025 were developed by Matter Labs. As such, Matter Labs will define the MINTER address for the `ZARPRetro` capped minter.\n\nDetails of audit reimbursements being claimed by Matter Labs are set out in the tables below.\n\n| ZIP | Auditor | $USD Claimed | Audit Report(s) |\n| ----- | ------------ | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| ZIP-3 | OpenZeppelin | $91,440 | [Protocol Defense Report](https://github.com/matter-labs/era-contracts/blob/main/audits/ZKsync%20Protocol%20Defense%20Audit%20-%20Final%20Report%20\\(Sept%202024\\).pdf) |\n| ZIP-6 | OpenZeppelin | $510,540 | [ZKsync Custom Asset Bridge Audit](https://github.com/matter-labs/era-contracts/blob/release-v26/audits/ZKsync%20Custom%20Asset%20Bridge%20Audit%20\\(OpenZeppelin\\).pdf) + [ZKChain Upgrades and Libraries Diff Audit](https://github.com/matter-labs/era-contracts/blob/release-v26/audits/ZKChain%20Upgrades%20and%20Libraries%20Diff%20Audit%20\\(OpenZeppelin\\).pdf) + [ZKChain & Gateway Upgrade Audit](https://github.com/matter-labs/era-contracts/blob/release-v26/audits/ZKsync%20ZKChain%20and%20Gateway%20Upgrade%20Audit%20\\(OpenZeppelin\\).pdf) + [ZKChain Release Candidate Audit](https://github.com/matter-labs/era-contracts/blob/release-v26/audits/ZKChain%20Release%20Candidate%20Audit%20\\(OpenZeppelin\\).pdf) |\n| ZIP-6 | Audittens | $380,000 | [Gateway Security Competition](https://github.com/Audittens/Audittens/blob/main/audit-reports/ZKsync%20Gateway%20Audit.pdf) |\n| ZIP-6 | Audittens | $100,000 | [Hyperchains Security Competition](https://github.com/Audittens/Audittens/blob/main/audit-reports/ZKsync%20Shared%20Bridge%20\\(USDC\\)%20Audit.pdf) |\n| ZIP-6 | Cyfrin | $500,000 | [CodeHawks Security Competition](https://codehawks.cyfrin.io/c/2024-10-zksync/submissions) |\n| ZIP-9 | OpenZeppelin | $628,620 | [EVM Equivalence Audit](https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync%20EVM%20Equivalence%20Audit.pdf) + [FFLONK Verifier Audit](https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync%20FFLONK%20Verifier%20Audit.pdf) + [FFLONK & EVM Emulator Diff Audit](https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync%20FFLONK%20and%20EVM%20Equivalence%20Diff%20Audit.pdf) |\n\nAll reimbursements claimed from the ZarpRetro capped have been reviewed and approved by the Security Council.\n\n### Claim Process\n\nAs the admin of the `ZarpRetro` capped minter, Matter Labs will be able to assign the minter role at their discretion that will be able to mint tokens in the `ZarpRetro` capped minter. The tokens are available to mint at any time until 31 January 2026.\n\n## Plan\n\n### **Measurement & Reporting**\n\n* **On-chain tracking**: The `ZarpMain` Capped Minter will record all disbursements, ensuring transparency.\n* **Quarterly governance updates**: The Security Council will publish status reports tracking disbursements and participation.\n* **End-of-year report**: A detailed impact analysis will be presented to the community.\n\n## Accountability Framework\n\n* The Security Council will review all reimbursement requests.\n* Conflicts of interest will be managed via a recusal policy.\n* All reimbursements are publicly documented for transparency.\n* Program impact is evaluated annually with Token Assembly input.\n\n## Participants\n\n* Security Council (responsible for oversight and pausing ineligible distributions).\n* ZIP developers and/or contributors (subject to KYC/KYB as per ZKsync Association policy)."
}
}By ZKSync Governance • 5/1/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 59837118
- Timestamp: 5/1/2025, 1:13:59 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalCreated
- Contract Address:0xEEEa...b1600xEEEa739a8b6fB1b8f703E23C9Be03CeeA643b160
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "103259976736823883300634095721999212673593591495252565610431467445162492146868"
},
"proposer": {
"value": "0xc11846203b0121C28285FA89EAd2249AafffaD2C"
},
"targets": {
"value": [
{
"value": "0xEa88046C61506480e8B69fFB4A5Dd8F80eC721b6"
}
]
},
"values": {
"value": [
{
"value": "0"
}
]
},
"signatures": {
"value": [
{
"value": ""
}
]
},
"calldatas": {
"value": [
{
"value": "0x"
}
]
},
"voteStart": {
"value": "1746710039"
},
"voteEnd": {
"value": "1747314839"
},
"description": {
"value": "# [GAP-3] Authorization for Security Council to Convert Recovered ETH into ZK\n| Title | Authorization for Security Council to Convert Recovered ETH into ZK |\n| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |\n| Proposal Type | GAP |\n| One Sentence Summary | This proposal authorizes the ZKsync Security Council to convert ETH, recovered from the April 2025 exploit of unclaimed airdrop tokens, back into ZK tokens. |\n| Proposal Author | ZKsync Security Council |\n| Proposal Sponsor | Cyfrin |\n| Date Created | 1 May 2025 |\n| Version | 1.0 |\n| Summary of Action | Authorise Security Council to swap ETH to ZK, then transfer ZK to Token Governor Timelock. |\n| Link to contracts | Not Applicable |\n\n## Abstract\n\nThis proposal authorizes the ZKsync Security Council to convert ETH, recovered from the April 2025 exploit of unclaimed airdrop tokens, back into ZK tokens. The assets are currently in the custody of the Security Council following a [successful safe harbor resolution](https://x.com/TheZKNation/status/1915110305790660939) with the hacker.\n\nDue to the potential for arbitrage and market manipulation, the methods and timing of the ETH-to-ZK conversion will not be disclosed publicly in advance. By passing this proposal, the Token Assembly affirms its intent to restore the unminted airdrop token supply in ZK form and delegates execution authority to the Security Council, under conditions of post-trade transparency and governance oversight.\n\n## Motivation\n\nOn April 13th, 2025, a compromised admin key was used to mint ~111.8 million ZK tokens from expired airdrop distributor contracts ([see announcement](https://x.com/zksync/status/1912165357642473488)). Following incident response and investigation, the Security Council negotiated a 90% return of the exploited funds. The recovered funds are currently held in Security Council multisigs on ZKsync Era and Ethereum.\n\nThe following table summarises the returned funds:\n\n| Asset Type | Amount Returned | Chain | Receiving Address | Transaction Link |\n| ---------- | ------------------ | ----------- | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |\n| ZK Tokens | 44,687,278.5988 ZK | ZKsync Era | `0xfFB6126FF8401665081b771bB11cCD0e09f95D5A` | [View Transaction](https://explorer.zksync.io/tx/0x4d79d0ffcca0098e69f642930de90d58adcda42ee649870a68f9279fcfcd418e) |\n| ETH | 1,021.3 ETH | ZKsync Era | `0xfFB6126FF8401665081b771bB11cCD0e09f95D5A` | [View Transaction](https://explorer.zksync.io/tx/0xfb4ae0efd38aedee7712046317397fe695ab8b90e7169870875c611887dce166) |\n| ETH | 776 ETH | Ethereum L1 | `0xb13dF19C56a75f9087CC03b10D482B4a775daB47` | [View Transaction](https://etherscan.io/tx/0xa344a0e759652246e51b1def91c8081b3527bdbbcab92128100f8fbc11c204df) |\n\nThis proposal ensures that the recovered ETH is responsibly converted back into ZK to align with the original intent of ZKsync governance. The recommended action minimizes risk to the protocol and the token by allowing operational discretion to the Security Council, who is trusted with emergency mitigation.\n\n## Specification\n\nIf this proposal is approved, the ZKsync Security Council is authorized to convert the recovered ETH into ZK tokens, including bridging and/or transferring ETH to a destination that allows for this conversion. \n\nThe timing, venue, and method of conversion shall be at the discretion of the Security Council, guided by the best interests of the Token Assembly. Public disclosure of trade details in advance is not required in order to minimize the risk of arbitrage or market manipulation.\n\nOnce all recovered ETH has been converted to ZK, the Security Council will transfer the total amount of ZK tokens to governance custody by transferring the tokens to the Token Governor Timelock, which is controlled by the Token Assembly.\n\nA public report will be issued upon completion of the conversion, summarizing the trade method, execution outcomes, and custody details. The Security Council must confirm that no personal gain was derived by the Security Council entity or members of the Security Council from the execution of the trades.\n\nThis is a one-time authorization limited to the ETH recovered from the April 2025 exploit.\n\n## Other Information\n\n* [Incident Report: Compromised Admin Key to Unclaimed Airdrop Tokens](https://zksync.mirror.xyz/W5vPDZqEqf2NuwQ5x7SyFnIxqqpE1szAFD69iaaBFnI)\n* [Returned Funds Onchain Confirmation](https://x.com/TheZKNation/status/1915110305790660939)\n* [Security Council Safe Harbor Message](https://x.com/TheZKNation/status/1914338338804244511)"
}
}By Ethereum Governance • 4/28/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22367584
- Timestamp: 4/28/2025, 12:33:11 PM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeExecuted
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0x2d3883b5d936c6a3c8b4170c4735bbf437de601b3f5afaceeee27b6b52907574"
}
}By Ethereum Governance • 4/26/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22356518
- Timestamp: 4/26/2025, 7:31:59 PM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeApprovedBySecurityCouncil
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0x2d3883b5d936c6a3c8b4170c4735bbf437de601b3f5afaceeee27b6b52907574"
}
}By ZKSync Governance • 4/19/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 59347481
- Timestamp: 4/18/2025, 8:34:12 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallExecuted
- Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714
Event Data
{
"id": {
"value": "0x576ba7df7bf49594c02e1e376b2ddd26f038e9b4f6dbfa0bd2631b0ad5a0ada4"
},
"index": {
"value": "0"
},
"target": {
"value": "0x0000000000000000000000000000000000008008"
},
"value": {
"value": "0"
},
"data": {
"value": "0x62f84b24...00000000"
}
}By ZKSync Governance • 4/19/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 59347481
- Timestamp: 4/18/2025, 8:34:12 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExecuted
- Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "112142012854508751423955156601121618924383324119199970784935099214632480260394"
}
}By ZKSync Governance • 4/18/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 59342222
- Timestamp: 4/18/2025, 7:46:54 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallScheduled
- Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714
Event Data
{
"id": {
"value": "0x576ba7df7bf49594c02e1e376b2ddd26f038e9b4f6dbfa0bd2631b0ad5a0ada4"
},
"index": {
"value": "0"
},
"target": {
"value": "0x0000000000000000000000000000000000008008"
},
"value": {
"value": "0"
},
"data": {
"value": "0x62f84b24...00000000"
},
"predecessor": {
"value": "0x0000000000000000000000000000000000000000000000000000000000000000"
},
"delay": {
"value": "0"
}
}By ZKSync Governance • 4/15/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 59197015
- Timestamp: 4/15/2025, 3:36:59 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExtended
- Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "112142012854508751423955156601121618924383324119199970784935099214632480260394"
},
"extendedDeadline": {
"value": "1745005019"
}
}By ZKSync Governance • 4/7/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 58794464
- Timestamp: 4/7/2025, 10:57:01 AM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalCreated
- Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "112142012854508751423955156601121618924383324119199970784935099214632480260394"
},
"proposer": {
"value": "0xc11846203b0121C28285FA89EAd2249AafffaD2C"
},
"targets": {
"value": [
{
"value": "0x0000000000000000000000000000000000008008"
}
]
},
"values": {
"value": [
{
"value": "0"
}
]
},
"signatures": {
"value": [
{
"value": ""
}
]
},
"calldatas": {
"value": [
{
"value": "0x62f84b24...00000000"
}
]
},
"voteStart": {
"value": "1744297021"
},
"voteEnd": {
"value": "1744901821"
},
"description": {
"value": "# [ZIP-9] V27 EVM Emulation Upgrade\n| **Proposal Type** | ZIP |\n| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------ |\n| **One Sentence Summary** | ZIP-9 proposes the V27 upgrade for ZKsync with two key features: (1) EVM emulation, and (2) Fflonk verifier. |\n| **Proposal Author** | Matter Labs |\n| **Proposal Sponsor** | Cyfrin |\n| **Date Created** | 7-April-2025 |\n| **Version** | v1 |\n| **Summary of Action** | Upgrade ZKsync to V27 |\n| **Link to Contracts** | [https://github.com/matter-labs/era-contracts/tree/release-v27](https://github.com/matter-labs/era-contracts/tree/release-v27) |\n\n# \\[ZIP-9] V27 EVM Emulation Upgrade\n\n## Abstract\n\nZIP-9 proposes the V27 upgrade for ZKsync. The key features of V27 are:\n\n* The EVM emulation, enabling the direct deployment and execution of EVM contracts on ZKsync without recompilation;\n* Fflonk verifier, optimizations and security improvements.\n\n## Motivation\n\nThe pursuit of full EVM equivalence at the bytecode level is a cornerstone of ZKsync’s technical vision, [as outlined in the 2025 roadmap](https://zksync.mirror.xyz/QG2Xr4lQdJTbyjeKftPVc6-pj2t9-H9WEGnvCcnusck). This initiative is fundamental to ensuring that ZKsync can seamlessly support all tools and frameworks designed for Ethereum Layer 1, thus significantly enhancing the developer experience.\n\nThe primary motivation for the V27 upgrade is to integrate Ethereum-compatible smart contract development into ZKsync EraVM. By implementing an EVM emulator, ZKsync can offer developers the ability to use standard Solidity and Vyper compilers, as well as popular tooling such as Foundry, Hardhat, and Remix without modifications. This initiative supports the broader goal of making ZKsync a fully interoperable and user-friendly platform that maintains high performance and security standards of the underlying EraVM.\n\nAnother key aspect of the upgrade is support for verifying Fflonk proofs, which will significantly reduce the cost of on-chain proof verification on Ethereum. This is an important part of the overall initiative to minimize transaction costs on ZKsync.\n\n## Specification\n\nThe V27 upgrade contracts can be found in the [Era Contracts Github repo](https://github.com/matter-labs/era-contracts/tree/release-v27). Details of the V27 upgrade are listed below:\n\n### EVM emulation\n\nThis release adds an optional EVM emulation mode, allowing chains to deploy and execute EVM contracts without recompiling for EraVM. This is an important step towards full EVM equivalence, which will open up new possibilities for developers and various Web3 protocols. EVM emulation provides following features:\n\n* **Standard Compiler Support:** Allows the use of unmodified EVM compilers for Solidity, Vyper and other languages.\n* **Tooling Compatibility:** Supports existing Ethereum development environments and build tools without the need for plugins or adaptations.\n* **Consistent Address Derivation:** Opens the way to deploy contracts using `create` and `create2` consistently with Ethereum address derivation scheme.\n* **Emulated EVM equivalence**: For EVM contracts, the environment is compatible with EVM. This includes support for most opcodes and precompiles, as well as emulated EVM-equivalent gas cost of operations. More details on equivalence are provided in documentation page.\n* **Pre-Deployed EVM Contracts:** Includes essential contracts such as `create2` factories, `multicall3`, and `singletonFactory` (ERC2470) to facilitate common contract interactions.\n\nFor developer resources on the EVM emulator, please visit documentation: [EVM emulator overview](https://docs.zksync.io/zksync-era/unique-features/evm-emulator/evm-emulator) and [EVM emulator documentation](https://docs.zksync.io/zksync-protocol/evm-emulator/overview).\n\nNew system contracts:\n\n* [**EvmEmulator**](https://github.com/matter-labs/era-contracts/blob/release-v27/system-contracts/contracts/EvmEmulator.yul): EraVM invokes this contract every time a call to the computer contract happens. EvmEmulator loads the EVM contract’s bytecode and executes it in the runtime.\n* [**EvmGasManager**](https://github.com/matter-labs/era-contracts/blob/release-v27/system-contracts/contracts/EvmGasManager.yul): Technical system contract used to emulate EVM storage gas behavior including warm/cold accesses mechanics.\n* [**EvmHashesStorage**](https://github.com/matter-labs/era-contracts/blob/release-v27/system-contracts/contracts/EvmHashesStorage.sol): Separate system contract that stores EVM code hashes (keccak256 hash of EVM bytecode).\n* [**EvmPredeploysManager**](https://github.com/matter-labs/era-contracts/blob/release-v27/system-contracts/contracts/EvmPredeploysManager.sol): Contract used to deploy important ecosystem EVM contracts like Create2 factories.\n\nNew precompiles to enhance EVM compatibility:\n\n* [**Identity**](https://github.com/matter-labs/era-contracts/blob/release-v27/system-contracts/contracts/precompiles/Identity.yul) (0x04): Just returns the input data.\n\nThe EVM emulation feature also requires the following changes:\n\n* **VM and circuits**:\n * Remove additional EVM emulation gas stipend. This stipend was implemented in the past as part of preparations for the EVM emulation, but in the final implementation it is not needed: the caller pays for the emulation in full.\n * Increase memory stipend for EVM emulation frames. EVM emulator uses memory to store stack and bytecode. The initial free heap size has been adjusted to account for this.\n* **L1 ecosystem contracts**\n * EVM emulator hash is added to batch meta params (similar to DefaultAccount bytecode hash).\n * Admin facet: added function `allowEvmEmulation()` to enable EVM emulator on the chain.\n * Mailbox facet: added special service L1→L2 transaction functionality, which is necessary for the mechanism of enabling EVM emulator on the chain.\n* **System contracts**\n * Bootloader and DefaultAccount: support deployment of EVM contracts by EOAs (with tx without field `to`).\n * ContractDeployer: Add functionality to deploy EVM contracts using `create`, `create2` and forced deployments. This functionality is available if the chain has the EVM emulation feature enabled.\n * KnownCodesStorage: Add functionality to publish EVM bytecodes.\n * AccountCodeStorage: Add EVM-specific functionality.\n\nAlong with the EVM emulator, we provide a set of contracts that can be deployed to pre-defined addresses. This list includes important frequently used contracts that are typically deployed using keyless transactions:\n\n* Create2 proxy: `0x4e59b44847b379578588920cA78FbF26c0B4956C`\n [GitHub - Arachnid/deterministic-deployment-proxy: An Ethereum proxy contract that can be used for deploying contracts to a deterministic address on any chain.](https://github.com/Arachnid/deterministic-deployment-proxy)\n* Create2 deployer: `0x13b0D85CcB8bf860b6b79AF3029fCA081AE9beF2`\n [GitHub - pcaversaccio/create2deployer: Helper smart contract to make easier and safer usage of the \\`CREATE2\\` EVM opcode.](https://github.com/pcaversaccio/create2deployer)\n* ERC2470 singleton factory: `0xce0042B868300000d44A59004Da54A005ffdcf9f`\n [ERC-2470: Singleton Factory](https://eips.ethereum.org/EIPS/eip-2470)\n* Safe Singleton Factory: `0x914d7Fec6aaC8cd542e72Bca78B30650d45643d7`\n [safe-singleton-factory/source/deterministic-deployment-proxy.yul at main · safe-global/safe-singleton-factory · GitHub](https://github.com/safe-global/safe-singleton-factory/blob/main/source/deterministic-deployment-proxy.yul)\n* Create2 proxy: `0x7A0D94F55792C434d74a40883C6ed8545E406D12`\n [GitHub - Zoltu/deterministic-deployment-proxy: An Ethereum proxy contract that can be used for deploying contracts to a deterministic address on any chain.](https://github.com/Zoltu/deterministic-deployment-proxy)\n\nDetailed overview of EVM emulation can be read in the contracts repo: [era-contracts/docs/evm\\_emulation at release-v27 · matter-labs/era-contracts · GitHub](https://github.com/matter-labs/era-contracts/tree/release-v27/docs/evm_emulation)\n\nEVM gas model emulation explainer: [EVM gas emulation overview](https://github.com/matter-labs/era-contracts/blob/release-v27/docs/evm_emulation/evm_gas_emulation.md)\n\n### Fflonk verifier\n\nThe other feature of the V27 release is optional proof verification with Fflonk (previously, only the Plonk protocol was used). The new verifier contract implementation can accept both Plonk and Fflonk proofs, providing flexibility during the transition period. An important reason for this change is that on-chain verification of Fflonk proofs is approximately 30% cheaper than verification of Plonk proofs, while consuming roughly the same (or even fewer) resources to generate the proof.\n\nNew flexible dual verifier implementation: [DualVerifier.sol](https://github.com/matter-labs/era-contracts/blob/release-v27/l1-contracts/contracts/state-transition/verifiers/DualVerifier.sol)\nNew Fflonk verifier implementation: [L1VerifierFflonk.sol](https://github.com/matter-labs/era-contracts/blob/release-v27/l1-contracts/contracts/state-transition/verifiers/L1VerifierFflonk.sol)\n\n### Additional changes\n\nThe V27 update includes several optimizations, improvements, and fixes for EraVM and circuits that enhance the security and performance of the protocol. Improvements also affect Boojum’s gadgets and internal functions. For detailed info please read corresponding audit reports:\n\n* **EraVM changes and fixes audit:** [V27 security audit](https://github.com/matter-labs/zksync-protocol/blob/main/audits/ZKsync%20V27%20security%20audit%20report.pdf)\n* **EraVM changes and fixes audit #2:** [V27 security audit #2](https://github.com/matter-labs/zksync-protocol/blob/main/audits/ZKsync%20V27%20security%20audit%20report%202.pdf)\n\nSeveral minor changes and fixes in the contracts are listed in the changelog: [V27 changelog](https://github.com/matter-labs/era-contracts/blob/release-v27/docs/upgrade_history/v27_evm_emulation/v27-evm-emulation.md#changes)\n\n## Rationale\n\n### EVM emulation\n\nThe EVM emulator is designed as a translation layer that does not replace but enhances the EraVM execution environment. This approach allows ZKsync to leverage the robust security and performance of EraVM while extending compatibility with the broader Ethereum ecosystem. More specifically, the emulation of the EVM environment on top of EraVM minimizes the number of changes required in critical and battle-tested parts of the system, such as circuits, thereby significantly enhancing the security of new functionality for the ecosystem. As a result, the implementation of the emulator in the Yul language simplifies its development, testing and auditing, which in turn will make further updates and improvements a lot easier.\n\nAn important drawback of this approach is the increased cost of EVM contract execution compared to native EraVM contracts, due to the need to emulate the EVM environment. It is also important to note that the emulation cannot provide 100% equivalence with EVM; detailed information can be found in the list of differences: [differences from EVM (Cancun)](https://github.com/matter-labs/era-contracts/blob/release-v27/docs/evm_emulation/differences_from_cancun_evm.md). Despite the described shortcomings, emulation will open the way for a large number of use cases. A fully EVM-equivalent native execution environment is a key part of the [2025 roadmap](https://zksync.mirror.xyz/QG2Xr4lQdJTbyjeKftPVc6-pj2t9-H9WEGnvCcnusck).\n\n## Implementation & Backwards Compatibility\n\n### EVM emulation\n\nThe EVM emulator will be integrated into the ZKsync Era protocol as a system contract that intercepts and translates EVM bytecode to EraVM instructions dynamically. This system ensures that all Ethereum-compatible contracts can be executed without altering their original code.\n\nThis feature does not affect already deployed EraVM contracts. EVM emulation is an **optional** feature which can be enabled separately for each ZK Chain by the corresponding chain admin.\n\nTo test compatibility with EVM, a widely used canonical set of state tests was used: [ethereum/tests](https://github.com/ethereum/tests/tree/a0e848269dd2af2b061fe9a4749d40963c2bdb5c). Corresponding test runner infrastructure for the emulator: [era-evm-tester](https://github.com/matter-labs/era-evm-tester).\n\n### Fflonk verifier\n\nTo simplify upgrades and improve fault tolerance, the new Fflonk verifier will be added as an optional, second option for proving. This approach improves backward compatibility, but still requires changing the input data layout for zk-SNARK verification to distinguish between the two types of proofs. This should be taken into account when submitting proofs to the verifier. More detailed info: [DualVerifier contract](https://github.com/matter-labs/era-contracts/blob/81b5b7d5c4b83e7193962f9e12e0c7186e0b7202/l1-contracts/contracts/state-transition/verifiers/DualVerifier.sol#L36-L42).\n\n## Security Considerations\n\nThe introduction of an EVM emulator involves complex interactions between different virtual machine instructions sets and system contracts. The verifier is an absolutely critical part of the protocol, on which the correctness and verifiability of the ecosystem depends.\n\nRigorous security audits and testing have been completed to ensure that proposed changes do not introduce vulnerabilities. Audit reports:\n\n* **EVM emulator contracts audit**: [https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync EVM Equivalence Audit.pdf](https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync%20EVM%20Equivalence%20Audit.pdf)\n* **FFLONK verifier contracts audit**: [https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync FFLONK Verifier Audit.pdf](https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync%20FFLONK%20Verifier%20Audit.pdf)\n* **FFLONK and EVM emulator contracts diff audit**: [https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync FFLONK and EVM Equivalence Diff Audit.pdf](https://github.com/matter-labs/era-contracts/blob/release-v27/audits/ZKsync%20FFLONK%20and%20EVM%20Equivalence%20Diff%20Audit.pdf)\n* **EraVM changes and fixes audit:** [V27 security audit](https://github.com/matter-labs/zksync-protocol/blob/main/audits/ZKsync%20V27%20security%20audit%20report.pdf)\n* **EraVM changes and fixes audit #2:** [V27 security audit #2](https://github.com/matter-labs/zksync-protocol/blob/main/audits/ZKsync%20V27%20security%20audit%20report%202.pdf)"
}
}By Ethereum Governance • 3/27/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 1
- Block: 22137920
- Timestamp: 3/27/2025, 7:21:59 AM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeApprovedBySecurityCouncil
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0xeb2c2f18ce9b8fb6c3b5e127b31fe96e9c68f5ad9ab9881232fdda5c02d218a4"
}
}By Ethereum Governance • 3/26/2025
Event Details
- Network: Ethereum Mainnet
- Chain ID: 324
- Block: 22131475
- Timestamp: 3/26/2025, 9:47:35 AM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeApprovedBySecurityCouncil
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0xa21bc099ce1f3147a25f0ad48d5fffdb4a158a908c8cc535f4f429becd9a4c84"
}
}By Ethereum Governance • 3/26/2025
Event Details
- Network: ethereum
- Chain ID: 324
- Block: 22131475
- Timestamp: 3/26/2025, 9:47:35 AM
Governance Info
- Governance Body: Ethereum Governance
- Event Type: UpgradeApprovedBySecurityCouncil
- Contract Address:0xE30D...5Ab30xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3
Event Data
{
"_id": {
"value": "0xa21bc099ce1f3147a25f0ad48d5fffdb4a158a908c8cc535f4f429becd9a4c84"
}
}By ZKSync Governance • 3/17/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 57819893
- Timestamp: 3/17/2025, 7:36:29 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExecuted
- Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "98806622840077485421207653857298019081476009136539565020582912190689619102417"
}
}By ZKSync Governance • 3/17/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 57819893
- Timestamp: 3/17/2025, 3:36:29 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallExecuted
- Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714
Event Data
{
"id": {
"value": "0x853a09aaa86c7a014f88eefd34f8902051367e548f62ca77cc40a4a89f27d84d"
},
"index": {
"value": "0"
},
"target": {
"value": "0x0000000000000000000000000000000000008008"
},
"value": {
"value": "0"
},
"data": {
"value": "0x62f84b24...00000000"
}
}By ZKSync Governance • 3/17/2025
Event Details
- Network: ZKSync Era
- Chain ID: 324
- Block: 57819893
- Timestamp: 3/17/2025, 3:36:29 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallExecuted
- Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714
Event Data
{
"id": {
"value": "0x853a09aaa86c7a014f88eefd34f8902051367e548f62ca77cc40a4a89f27d84d"
},
"index": {
"value": "0"
},
"target": {
"value": "0x0000000000000000000000000000000000008008"
},
"value": {
"value": "0"
},
"data": {
"value": "0x62f84b24...00000000"
}
}By ZKSync Governance • 3/17/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 57819639
- Timestamp: 3/17/2025, 3:29:43 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallScheduled
- Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714
Event Data
{
"id": {
"value": "0x853a09aaa86c7a014f88eefd34f8902051367e548f62ca77cc40a4a89f27d84d"
},
"index": {
"value": "0"
},
"target": {
"value": "0x0000000000000000000000000000000000008008"
},
"value": {
"value": "0"
},
"data": {
"value": "0x62f84b24...00000000"
},
"predecessor": {
"value": "0x0000000000000000000000000000000000000000000000000000000000000000"
},
"delay": {
"value": "0"
}
}By ZKSync Governance • 3/17/2025
Event Details
- Network: ZKSync Era
- Chain ID: 324
- Block: 57819639
- Timestamp: 3/17/2025, 3:29:43 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: CallScheduled
- Contract Address:0x085b...c7140x085b8B6407f150D62adB1EF926F7f304600ec714
Event Data
{
"id": {
"value": "0x853a09aaa86c7a014f88eefd34f8902051367e548f62ca77cc40a4a89f27d84d"
},
"index": {
"value": "0"
},
"target": {
"value": "0x0000000000000000000000000000000000008008"
},
"value": {
"value": "0"
},
"data": {
"value": "0x62f84b24...00000000"
},
"predecessor": {
"value": "0x0000000000000000000000000000000000000000000000000000000000000000"
},
"delay": {
"value": "0"
}
}By ZKSync Governance • 3/14/2025
Event Details
- Network: ZKSync
- Chain ID: 324
- Block: 57667473
- Timestamp: 3/14/2025, 7:20:34 PM
Governance Info
- Governance Body: ZKSync Governance
- Event Type: ProposalExtended
- Contract Address:0x7670...e34f0x76705327e682F2d96943280D99464Ab61219e34f
- Proposal Link: View Proposal
Event Data
{
"proposalId": {
"value": "98806622840077485421207653857298019081476009136539565020582912190689619102417"
},
"extendedDeadline": {
"value": "1742239234"
}
}