ZIP: 0 @@ -81,27 +81,27 @@ License: BSD-2-Clause
The ZIP editors monitor ZIP changes and update ZIP headers as appropriate.
The ZIP Editors MAY reject a proposed ZIP or update to an existing ZIP for any of the following reasons:
The ZIP Editors MUST NOT unreasonably deny publication of a ZIP proposal or update that does not violate any of these criteria. If they refuse a proposal or update, they MUST give an explanation of which of the criteria were violated, with the exception that spam may be deleted without an explanation.
Note that it is not the primary responsibility of the ZIP Editors to review proposals for security, correctness, or implementability.
@@ -136,13 +136,13 @@ License:Credits: Original-Authors: Discussions-To: -Network Upgrade: -Obsoleted by: -Updated by: +Network Upgrade: +Obsoleted by: +Updated by: Obsoletes: Updates:
The Owners header lists the names and email addresses of all the Owners of the ZIP. The format of the Owners header value SHOULD be:
-Random J. User <address@dom.ain>+
Random J. User <address@dom.ain>
If there are multiple Owners, each should be on a separate line.
While a ZIP is in private discussions (usually during the initial Draft phase), a Discussions-To header will indicate the URL where the ZIP is being discussed. No Discussions-To header is necessary if the ZIP is being discussed privately with the Owner.
The Category header specifies the type of ZIP: Consensus, Standards Track, Informational, or Process.
@@ -199,8 +199,8 @@ Updates:New ZIPs may be accepted with the following licenses. Each new ZIP MUST identify at least one acceptable license in its preamble. Each license MUST be referenced by their respective abbreviation given below.
For example, a preamble might include the following License header:
-License: BSD-2-Clause - GNU-All-Permissive+
License: BSD-2-Clause + GNU-All-Permissive
In this case, the ZIP text is fully licensed under both the OSI-approved BSD 2-clause license as well as the GNU All-Permissive License, and anyone may modify and redistribute the text provided they comply with the terms of either license. In other words, the license list is an "OR choice", not an "AND also" requirement.
It is also possible to license source code differently from the ZIP text. This case SHOULD be indicated in the Reference Implementation section of the ZIP. Again, each license MUST be referenced by its respective abbreviation given below.
Statements of code licenses in ZIPs are only advisory; anyone intending to use the code should look for license statements in the code itself.
diff --git a/zip-0000.rst b/zip-0000.rst index 726153e5..396ae554 100644 --- a/zip-0000.rst +++ b/zip-0000.rst @@ -205,42 +205,42 @@ appropriate. The ZIP Editors MAY reject a proposed ZIP or update to an existing ZIP for any of the following reasons: -* it violates the Zcash Code of Conduct [#conduct]_ ; -* it appears too unfocused or broad; -* it duplicates effort in other ZIPs without sufficient technical justification - (however, alternative proposals to address similar or overlapping problems - are not excluded for this reason); -* it has manifest security flaws (including being unrealistically dependent - on user vigilance to avoid security weaknesses); -* it disregards compatibility with the existing Zcash blockchain or ecosystem; -* it is manifestly unimplementable; -* it includes buggy code, pseudocode, or algorithms; -* it manifestly violates common expectations of a significant portion of the - Zcash community; -* it updates a Draft ZIP to Released when there is significant community - opposition to its content (however, Draft ZIPs explicitly may describe - proposals to which there is, or could be expected, significant community +* it violates the Zcash Code of Conduct [#conduct]_ ; +* it appears too unfocused or broad; +* it duplicates effort in other ZIPs without sufficient technical justification + (however, alternative proposals to address similar or overlapping problems + are not excluded for this reason); +* it has manifest security flaws (including being unrealistically dependent + on user vigilance to avoid security weaknesses); +* it disregards compatibility with the existing Zcash blockchain or ecosystem; +* it is manifestly unimplementable; +* it includes buggy code, pseudocode, or algorithms; +* it manifestly violates common expectations of a significant portion of the + Zcash community; +* it updates a Draft ZIP to Released when there is significant community + opposition to its content (however, Draft ZIPs explicitly may describe + proposals to which there is, or could be expected, significant community opposition); -* in the case of a Released ZIP, the update makes a substantive change to - which there is significant community opposition; -* it is dependent on a patent that could potentially be an obstacle to - adoption of the ZIP; -* it includes commercial advertising or spam; -* it disregards formatting rules; -* it makes non-editorial edits to previous entries in a ZIP's Change history; -* an update to an existing ZIP extends or changes its scope to an extent - that would be better handled as a separate ZIP; -* a new ZIP has been proposed for a category that does not reflect its content, - or an update would change a ZIP to an inappropriate category; -* it updates a Released ZIP to Draft when the specification is already - implemented and has been in common use; +* in the case of a Released ZIP, the update makes a substantive change to + which there is significant community opposition; +* it is dependent on a patent that could potentially be an obstacle to + adoption of the ZIP; +* it includes commercial advertising or spam; +* it disregards formatting rules; +* it makes non-editorial edits to previous entries in a ZIP's Change history; +* an update to an existing ZIP extends or changes its scope to an extent + that would be better handled as a separate ZIP; +* a new ZIP has been proposed for a category that does not reflect its content, + or an update would change a ZIP to an inappropriate category; +* it updates a Released ZIP to Draft when the specification is already + implemented and has been in common use; * it violates any specific "MUST" or "MUST NOT" rule in this document; -* the expressed political views of a Owner of the document are inimical - to the Zcash Code of Conduct [#conduct]_ (except in the case of an update - removing that Owner); -* it is not authorized by the stated ZIP Owners; -* it removes an Owner without their consent (unless the reason for removal - is directly related to a breach of the Code of Conduct by that Owner). +* the expressed political views of a Owner of the document are inimical + to the Zcash Code of Conduct [#conduct]_ (except in the case of an update + removing that Owner); +* it is not authorized by the stated ZIP Owners; +* it removes an Owner without their consent (unless the reason for removal + is directly related to a breach of the Code of Conduct by that Owner). The ZIP Editors MUST NOT unreasonably deny publication of a ZIP proposal or update that does not violate any of these criteria. If they refuse a @@ -314,29 +314,29 @@ ZIP header preamble Each ZIP must begin with an RFC 822-style header preamble. The following header fields are REQUIRED:: - ZIP: - Title: - Owners: - Status: - Category: + ZIP: + Title: + Owners: + Status: + Category: Created: - License: + License: The following additional header fields are OPTIONAL:: Credits: Original-Authors: Discussions-To: - Network Upgrade: - Obsoleted by: - Updated by: + Network Upgrade: + Obsoleted by: + Updated by: Obsoletes: Updates: The Owners header lists the names and email addresses of all the Owners of the ZIP. The format of the Owners header value SHOULD be:: - Random J. User + Random J. User If there are multiple Owners, each should be on a separate line. @@ -493,8 +493,8 @@ MUST be referenced by their respective abbreviation given below. For example, a preamble might include the following License header:: - License: BSD-2-Clause - GNU-All-Permissive + License: BSD-2-Clause + GNU-All-Permissive In this case, the ZIP text is fully licensed under both the OSI-approved BSD 2-clause license as well as the GNU All-Permissive License, and diff --git a/zip-0032.html b/zip-0032.html index 1e2c2e7f..a097974f 100644 --- a/zip-0032.html +++ b/zip-0032.html @@ -3,7 +3,7 @@ZIP: 32 diff --git a/zip-0143.html b/zip-0143.html index b0eb8436..ce57459f 100644 --- a/zip-0143.html +++ b/zip-0143.html @@ -3,7 +3,7 @@ZIP 143: Transaction Signature Verification for Overwinter - + ZIP: 143 diff --git a/zip-0200.html b/zip-0200.html index eb528b7f..8db936c5 100644 --- a/zip-0200.html +++ b/zip-0200.html @@ -3,7 +3,7 @@ZIP 200: Network Upgrade Mechanism - + ZIP: 200 diff --git a/zip-0201.html b/zip-0201.html index f7f4abbc..7c034200 100644 --- a/zip-0201.html +++ b/zip-0201.html @@ -3,7 +3,7 @@ZIP 201: Network Peer Management for Overwinter - + ZIP: 201 diff --git a/zip-0202.html b/zip-0202.html index 99761ab5..f938ac41 100644 --- a/zip-0202.html +++ b/zip-0202.html @@ -3,7 +3,7 @@ZIP 202: Version 3 Transaction Format for Overwinter - + ZIP: 202 diff --git a/zip-0203.html b/zip-0203.html index 3e1308ef..66024139 100644 --- a/zip-0203.html +++ b/zip-0203.html @@ -3,7 +3,7 @@ZIP 203: Transaction Expiry - + ZIP: 203 diff --git a/zip-0205.html b/zip-0205.html index 0866bca7..b5e9ef75 100644 --- a/zip-0205.html +++ b/zip-0205.html @@ -3,7 +3,7 @@ZIP 205: Deployment of the Sapling Network Upgrade - + ZIP: 205 diff --git a/zip-0206.html b/zip-0206.html index 07db122d..e4cfbccf 100644 --- a/zip-0206.html +++ b/zip-0206.html @@ -3,7 +3,7 @@ZIP 206: Deployment of the Blossom Network Upgrade - + ZIP: 206 diff --git a/zip-0207.html b/zip-0207.html index d1bde966..024860f4 100644 --- a/zip-0207.html +++ b/zip-0207.html @@ -3,7 +3,7 @@ZIP 207: Split Founders' Reward - + ZIP: 207 diff --git a/zip-0208.html b/zip-0208.html index f2e6bd1a..5415e51f 100644 --- a/zip-0208.html +++ b/zip-0208.html @@ -3,7 +3,7 @@ZIP 208: Shorter Block Target Spacing - + ZIP: 208 diff --git a/zip-0209.html b/zip-0209.html index 41560e76..621d952c 100644 --- a/zip-0209.html +++ b/zip-0209.html @@ -3,7 +3,7 @@ZIP 209: Prohibit Negative Shielded Value Pool - + ZIP: 209 diff --git a/zip-0210.html b/zip-0210.html index d229b1af..18dca770 100644 --- a/zip-0210.html +++ b/zip-0210.html @@ -3,7 +3,7 @@ZIP 210: Sapling Anchor Deduplication within Transactions - + ZIP: 210 diff --git a/zip-0243.html b/zip-0243.html index a1c6ac77..83fbc504 100644 --- a/zip-0243.html +++ b/zip-0243.html @@ -3,7 +3,7 @@ZIP 243: Transaction Signature Verification for Sapling - + ZIP: 243 diff --git a/zip-0308.html b/zip-0308.html index 2bc60f27..99be5105 100644 --- a/zip-0308.html +++ b/zip-0308.html @@ -3,7 +3,7 @@ZIP 308: Sprout to Sapling Migration - + ZIP: 308 diff --git a/zip-0401.html b/zip-0401.html index a2ee5d93..e4a6e136 100644 --- a/zip-0401.html +++ b/zip-0401.html @@ -3,7 +3,7 @@ZIP 401: Addressing mempool denial-of-service - + ZIP: 401 diff --git a/zip-1001.html b/zip-1001.html index 1f4971df..840cbd3d 100644 --- a/zip-1001.html +++ b/zip-1001.html @@ -3,7 +3,7 @@ZIP 1001: Keep the Block Distribution as Initially Defined — 90% to Miners - + ZIP: 1001 diff --git a/zip-1002.html b/zip-1002.html index 5793cfff..587d846e 100644 --- a/zip-1002.html +++ b/zip-1002.html @@ -3,7 +3,7 @@ZIP 1002: Opt-in Donation Feature - + ZIP: 1002 diff --git a/zip-1003.html b/zip-1003.html index 9aa4f9b0..59182560 100644 --- a/zip-1003.html +++ b/zip-1003.html @@ -3,7 +3,7 @@ZIP 1003: 20% Split Evenly Between the ECC and the Zcash Foundation, and a Voting System Mandate - + ZIP: 1003 diff --git a/zip-1004.html b/zip-1004.html index dad2e93a..65922a65 100644 --- a/zip-1004.html +++ b/zip-1004.html @@ -3,7 +3,7 @@ZIP 1004: Miner-Directed Dev Fund - + ZIP: 1004 diff --git a/zip-1005.html b/zip-1005.html index 7965895a..3c452de5 100644 --- a/zip-1005.html +++ b/zip-1005.html @@ -3,7 +3,7 @@ZIP 1005: Zcash Community Funding System - + ZIP: 1005 diff --git a/zip-1006.html b/zip-1006.html index 3a20e178..d533a8ab 100644 --- a/zip-1006.html +++ b/zip-1006.html @@ -3,7 +3,7 @@ZIP 1006: Development Fund of 10% to a 2-of-3 Multisig with Community-Involved Third Entity - + ZIP: 1006 diff --git a/zip-1007.html b/zip-1007.html index 5ad88cf3..56ac92b6 100644 --- a/zip-1007.html +++ b/zip-1007.html @@ -3,7 +3,7 @@ZIP 1007: Enforce Development Fund Commitments with a Legal Charter - + ZIP: 1007 diff --git a/zip-1008.html b/zip-1008.html index 67272362..e45b5cd0 100644 --- a/zip-1008.html +++ b/zip-1008.html @@ -3,7 +3,7 @@ZIP 1008: Fund ECC for Two More Years - + ZIP: 1008 diff --git a/zip-1009.html b/zip-1009.html index 328477c4..4fcc51b5 100644 --- a/zip-1009.html +++ b/zip-1009.html @@ -3,7 +3,7 @@ZIP 1009: Five-Entity Strategic Council - + ZIP: 1009 diff --git a/zip-1010.html b/zip-1010.html index f49804e0..ba371192 100644 --- a/zip-1010.html +++ b/zip-1010.html @@ -3,7 +3,7 @@ZIP 1010: Compromise Dev Fund Proposal With Diverse Funding Streams - + ZIP: 1010 diff --git a/zip-1011.html b/zip-1011.html index 9a9904f6..52595717 100644 --- a/zip-1011.html +++ b/zip-1011.html @@ -4,7 +4,7 @@ZIP 1011: Decentralize the Dev Fee - + ZIP: 1011 diff --git a/zip-1012.html b/zip-1012.html index 786f4688..b563e6e0 100644 --- a/zip-1012.html +++ b/zip-1012.html @@ -3,7 +3,7 @@ZIP 1012: Dev Fund to ECC + ZF + Major Grants - + ZIP: 1012 diff --git a/zip-1013.html b/zip-1013.html index 3840404b..05078dd0 100644 --- a/zip-1013.html +++ b/zip-1013.html @@ -3,7 +3,7 @@ZIP 1013: Keep It Simple, Zcashers: 10% to ECC, 10% to ZF - + ZIP: 1013 diff --git a/zip-1014.html b/zip-1014.html index d7b9e5e6..7ad1da6e 100644 --- a/zip-1014.html +++ b/zip-1014.html @@ -3,7 +3,7 @@ZIP 1014: Dev Fund to ECC + ZF + Major Grants - + ZIP: 1014 diff --git a/zip-guide.html b/zip-guide.html index dbc136da..73f65de7 100644 --- a/zip-guide.html +++ b/zip-guide.html @@ -3,7 +3,7 @@ZIP guide: {Something Short and To the Point} - + ZIP: Unassigned {numbers are assigned by ZIP editors}