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 ZcashCommunity Discord chat 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, into the zips/ directory.
For example, if using reStructuredText, use a filename matching zips/draft-*.rst
. Use make
to check that you are using correct reStructuredText or Markdown syntax, and double-check the generated rendered/draft-*.html
file before filing a Pull Request. See here for the project dependencies.
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 .
These are works-in-progress that have been assigned ZIP numbers. These will eventually become either Proposed (and thus Released), or one of Withdrawn, Rejected, or Obsolete.
In some cases a ZIP number is reserved by the ZIP Editors before a draft is written.
These are works-in-progress, and may never be assigned ZIP numbers if their ideas become obsoleted or abandoned. Do not assume that these drafts will exist in perpetuity; instead assume that they will either move to a numbered ZIP, or be deleted.