What are ZIPs?

Zcash Improvement Proposals (ZIPs) are the way to:


The authors of a ZIP are responsible for building consensus within the community and documenting / addressing dissenting opinions.

Anyone can write a ZIP! We encourage community contributions and decentralization of work on the Zcash protocol. If you’d like to bounce ideas off people before formally writing a ZIP, we encourage it! Visit the community Discord channel to talk about your idea.

Participation in the Zcash project is subject to a Code of Conduct.

The Zcash protocol is documented in its Protocol Specification.

To start contributing, first read ZIP 0 which documents the ZIP process. Then clone this repo from GitHub, and start adding your draft ZIP, formatted either as reStructuredText or as Markdown.

For example, if using reStructuredText, use a filename matching draft-*.rst. Use make to check that you are using correct reStructuredText or Markdown syntax, and double-check the generated draft-*.html file before filing a Pull Request.

Heartwood ZIPs

This is the list of ZIPs included in Heartwood (Network Upgrade 3), due to activate on mainnet in mid-July 2020:


Unless otherwise stated in this repository’s individual files, the contents of this repository are released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT .

Index of ZIPs

ZIP Title Status
0 ZIP Process Active
32 Shielded Hierarchical Deterministic Wallets Final
143 Transaction Signature Validation for Overwinter Final
173 Bech32 Format Final
200 Network Upgrade Mechanism Final
201 Network Peer Management for Overwinter Final
202 Version 3 Transaction Format for Overwinter Final
203 Transaction Expiry Final
205 Deployment of the Sapling Network Upgrade Final
206 Deployment of the Blossom Network Upgrade Final
207 Funding Streams Proposed
208 Shorter Block Target Spacing Final
209 Prohibit Negative Shielded Value Pool Final
210 Sapling Anchor Deduplication within Transactions Draft
211 Disabling Addition of New Value to the Sprout Value Pool Implemented (zcashd)
212 Allow Recipient to Derive Sapling Ephemeral Secret from Note Plaintext Implemented (zcashd)
213 Shielded Coinbase Implemented (zcashd)
214 Consensus rules for a Zcash Development Fund Implemented (zcashd)
215 Explicitly Defining and Modifying Ed25519 Validation Rules Implemented (zcashd)
221 FlyClient - Consensus-Layer Changes Implemented (zcashd)
243 Transaction Signature Validation for Sapling Final
250 Deployment of the Heartwood Network Upgrade Implemented (zcashd)
251 Deployment of the Canopy Network Upgrade Proposed
301 Zcash Stratum Protocol Informational
304 Sapling Address Signatures Draft
307 Light Client Protocol for Payment Detection Draft
308 Sprout to Sapling Migration Final
310 Security Properties of Sapling Viewing Keys Draft
401 Addressing mempool denial-of-service Final
1001 Keep the Block Distribution as Initially Defined — 90% to Miners Obsolete
1002 Opt-in Donation Feature Obsolete
1003 20% Split Evenly Between the ECC and the Zcash Foundation, and a Voting System Mandate Obsolete
1004 Miner-Directed Dev Fund Obsolete
1005 Zcash Community Funding System Obsolete
1006 Development Fund of 10% to a 2-of-3 Multisig with Community-Involved Third Entity Obsolete
1007 Enforce Development Fund Commitments with a Legal Charter Obsolete
1008 Fund ECC for Two More Years Obsolete
1009 Five-Entity Strategic Council Obsolete
1010 Compromise Dev Fund Proposal With Diverse Funding Streams Obsolete
1011 Decentralize the Dev Fee Obsolete
1012 Dev Fund to ECC + ZF + Major Grants Obsolete
1013 Keep It Simple, Zcashers: 10% to ECC, 10% to ZF Obsolete
1014 Establishing a Dev Fund for ECC, ZF, and Major Grants Proposed
guide {Something Short and To the Point} Draft