ZIP Process

• Some ZIPs, especially in the Consensus category, may include literal code in the ZIP itself which may not be available under the exact license terms of the ZIP.
• Despite this, not all software licenses would be acceptable for content included in ZIPs.

Why are GPL/AGPL/LGPL-style licenses not included?

• No existing ZIP had used these licenses.
• There is no reason to use such licenses for documentation, and including literal code under these licenses in a ZIP could undesirably affect the distribution terms of the ZIP as a whole.
• If necessary, code under such licenses can be linked for informational purposes, or as long as its incompatibility with the zebra, zcashd, Zallet, and/or Zaino licenses is noted.

See Also

• RFC 7282: On Consensus and Humming in the IETF
• Zcash Network Upgrade Pipeline

Acknowledgements

We thank George Tankersley, Deirdre Connolly, Teor, Aditya Bharadwaj, and Conrado Gouvêa for their past contributions as ZIP Editors.

References

---

1. Information on BCP 14 — "RFC 2119: Key words for use in RFCs to Indicate Requirement Levels" and "RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"↩︎

2. ZIP 200: Network Upgrade Mechanism↩︎

3. ZIPs git repository↩︎

4. ZIPs git repository↩︎

5. reStructuredText documentation↩︎

6. The Markdown Guide↩︎

7. ZIPs git repository↩︎

8. ZIPs git repository↩︎

9. ZIPs git repository↩︎

10. Zcash Code of Conduct↩︎

11. Zcash Code of Conduct↩︎

12. Zcash Code of Conduct↩︎

13. reStructuredText documentation↩︎

14. The Markdown Guide↩︎

15. LaTeX — a document preparation system↩︎

16. ZIPs git repository↩︎