| Proposal information | Details |
|---|---|
| Title | ZKsync Security Council 2026–2027 Funding |
| Proposal Type | TPP |
| One Sentence Summary | This proposal funds ZKsync Security Council operations from 1 August 2026 to 31 July 2027 using ZK already held in the treasury. |
| Proposal Author | ZKsync Security Council |
| Proposal Sponsor | TBC |
| Date Created | August 2026 |
| Version | v1.0 |
| Summary of Action | Approve the transfer of 59,714,286 ZK ($418k USD at 0.007) to the Security Council multisig for the funding period specified in this proposal from Token Governor Timelock. |
| Link to Proposal Discussion | TBC |
Abstract
This Token Program Proposal seeks approval to fund the ZKsync Security Council for 12 months from 1 August 2026 to 31 July 2027 with ZK tokens currently held in the Token Govenor Timelock. A total of 59,714,286 ZK is requested ($418k USD at 0.007) to fund an eight-member Security Council along with the entity’s legal, administrative and operational obligations.
This proposal does not approve a capped minter, confer any minting rights or result in the minting of additional ZK.
Motivation
The ZKsync Security Council provides an independent technical check within the ZKsync governance system.
Its core responsibilities, as set out in the Governance Procedures, are:
- Reviewing and approving protocol upgrades during the Risk Review period, including verification of the relevant ZKsync Improvement Proposal specifications; and
- Responding to time-sensitive protocol security matters in accordance with the ZKsync Governance Procedures.
The Security Council must maintain the technical capability, secure signing infrastructure, organizational coordination and member availability required to perform these responsibilities. This standing capability must be maintained throughout the funding period, regardless of the number of upgrades or security matters that arise.
ZIP-15, passed in May 2026, established the current eight-member structure and the terms under which its members serve. The Security Council also requires an operating entity through which member agreements, payments, director responsibilities, accounting, compliance and other administrative obligations can be managed.
The proposed funding reflects the Council’s current size and operating requirements. It is intended to preserve the Security Council’s essential functions through a lean and sustainable structure that recognizes current market conditions.
Specification
Funding Parameters
| Parameter | Value |
|---|---|
| Annual operating budget | $418,000 USD |
| Funding source | ZK already held in the Token Govenor Timelock |
| Reference price used to calculate the allocation | $0.007 per ZK |
| Allocation | 59,714,286 ZK |
| Token Governor Timelock | 0xe5d21A9179CA2E1F0F327d598D464CcF60d89c3d |
| Security Council Multisig | 0xB5edBf47fC5eF24a7b7FE1F31f24fD2768Ea2C67 |
Budget Allocation
| Budget component | Basis | Annual amount |
|---|---|---|
| Member fees | Eight members at 3k USDC/month, as approved under ZIP-15 | $288,000 |
| Director fees | Governance and oversight of the operating entity | $80,000 |
| Entity fees | Legal, accounting, compliance, administration and operations | $50,000 |
Member fees support the protocol review, signing, availability and response responsibilities associated with serving on the Security Council. The remaining costs support the entity required to administer and maintain the Council.
Token Mechanic
No capped minter will be deployed and no minter role will be granted for this proposal.
This proposal approves a direct transfer of ZK already held in the treasury, subject to the funding parameters above.
The allocation was calculated using the stated reference price. The budget and the Security Council’s underlying obligations are denominated in USD, while the realized value of the transferred ZK may change with the market price.
The Security Council may convert the allocated ZK into USDC or another suitable operating asset as reasonably required to meet the obligations approved under this proposal.
Rationale
This proposal continues funding for the Security Council structure approved under ZIP-15. It does not expand the Council’s mandate, membership or existing member terms.
The request is limited to maintaining the Council’s technical review, signing and response capabilities and the entity required to support those functions. It represents a materially lower annual operating budget than the previous funding period and reflects the need for careful management of token resources under current market conditions.
Accountability
The allocation will be transferred to the Security Council multisig.
- The multisig balance and transaction history will be publicly visible onchain.
- Any funds remaining at the end of the funding period will be returned to the Token Assembly.