ZKsync Proposal Guidelines
Last updated
Last updated
Proposals are submitted onchain on the (via Tally) or on other applications connected to ZKsync governance contracts.
To submit a proposal, Delegates must meet the proposal submission threshold of 0.1% or 21 million ZK of the total ZK token supply (21 billion). If a Delegate does not meet the threshold, or the author is not a Delegate, they can find a Delegate to sponsor and submit the proposal on their behalf. Delegate profiles can be viewed at .
ZKsync Governance Proposals pass a vote if delegates reach quorum, defined as 3% or 630 million ZK voting power in support of the proposal, AND have a simple majority of “For” votes (>50%). Each proposal must also be consistent with the values of the and support the sustainable development of the ZKsync protocol and must not violate applicable law. Otherwise, it may be vetoed by the ZKsync Guardians or may be removed from the ZKsync governance portal.
The ZKsync governance system has three types of proposals at inception:
ZKsync Improvement Proposals ("ZIPs"): These proposals outline changes to the ZKsync protocol contracts via the Protocol Upgrade Governor.
Token Program Proposals (”TPPs”): These proposals activate new mechanics through which the ZK token is minted and burned by participants who are actively developing the ZKsync ecosystem.
Governance Advisory Proposals (”GAPs”): These proposals specify offchain decisions and actions that require approval by the Token Assembly, but are not directly related to the ZKsync protocol or the ZK token. For example: ratifications, elections, or other decisions requiring onchain voting.
All proposals are managed by ZKsync governance smart contracts that operate directly onchain. The parameters of these governors, such as voting periods and timelocks, are specified in the .
Delegates should submit a proposal onchain after the idea has been shared widely with the ZKsync community. Delegates are encouraged to:
Refine the idea with a working group of 2-5 people.
Use the ZKsync Governance Forum, social media, and Delegates to gather feedback and create awareness of the proposal idea, draft, or full proposal.
You can add the necessary onchain actions on Tally as part of the onchain proposal. To do so, visit the “Actions” section of the proposal creation flow on Tally. Then select “Custom action” and upload the necessary Application Binary Interface (ABI) file. The ABI file describes the methods and variables within a smart contract that are accessible and callable by external users or other smart contracts.
ZKsync governance proposals can be viewed on the ZKsync Governance Portal powered by Tally. However, some proposals may be removed and become unavailable on the portal if the proposal:
is deemed illegal under Austrian law
enables access to ZK tokens by prohibited addresses, including those associated with sanctioned entities, individuals, or jurisdictions, as well as addresses linked to illicit activities like fraud, money laundering, terrorist financing, or other criminal enterprises.
Any proposal removed from the ZKsync Governance Portal powered by Tally may continue to be accessible via services not owned or managed by the ZKsync Association.
Develop a draft proposal, informed through conversations and research, and post it on the under the relevant category (will depend on proposal type).
Gather informal voting commitments from other Delegates in the ZKsync community. Delegate profiles can be viewed at .
Submit the proposal onchain via the , or an alternative application connected to ZKsync governance contracts.
You can read more about Tally’s onchain actions at
Delegates who have been delegated ZK token voting power can vote on proposals via the ZKsync Governance Portal on Tally (), other independent applications such as Boardroom (), or directly onchain via the ZKsync block explorer ().
to learn more about delegation.
to learn more about voting on proposals.
Yes. Follow to vote with a multisig.
