diff --git a/zip-0000.html b/zip-0000.html index b07b1760..e055222e 100644 --- a/zip-0000.html +++ b/zip-0000.html @@ -34,7 +34,7 @@ License: BSD-2-Clause

Once the Owner has asked the Zcash community as to whether an idea has any chance of acceptance, a draft ZIP should be presented to the Zcash Community Forum. This gives the Owner a chance to flesh out the draft ZIP to make it properly formatted, of high quality, and to address additional concerns about the proposal. Following a discussion, the proposal should be submitted to the ZIPs git repository as a pull request. This draft must be written in ZIP style as described below, and named with an alias such as zip-zatoshizakamoto-42millionzec until the ZIP Editors have assigned it a ZIP number (Owners MUST NOT self-assign ZIP numbers).

ZIP Owners are responsible for collecting community feedback on both the initial idea and the ZIP before submitting it for review. However, wherever possible, long open-ended discussions on forums should be avoided.

It is highly recommended that a single ZIP contain a single key proposal or new idea. The more focused the ZIP, the more successful it tends to be. If in doubt, split your ZIP into several well-focused ones.

-

When the ZIP draft is complete, the ZIP Editors will assign the ZIP a number, label it as Standards Track, Informational, or Process, and merge the pull request to the ZIPs git repository. The ZIP Editors will not unreasonably reject a ZIP. Reasons for rejecting ZIPs include duplication of effort, disregard for formatting rules, being too unfocused or too broad, being technically unsound, not providing proper motivation or not in keeping with the Zcash philosophy. For a ZIP to be accepted it must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement. The proposed implementation, if applicable, must be solid and must not complicate the protocol unduly.

+

When the ZIP draft is complete, the ZIP Editors will assign the ZIP a number (if that has not already been done) and one or more Categories, and merge the pull request to the ZIPs git repository. The ZIP Editors will not unreasonably reject a ZIP. Reasons for rejecting ZIPs include duplication of effort, disregard for formatting rules, being too unfocused or too broad, being technically unsound, not providing proper motivation or not in keeping with the Zcash philosophy. For a ZIP to be accepted it must meet certain minimum criteria. It must be a clear and complete description of the proposed enhancement. The enhancement must represent a net improvement. The proposed implementation, if applicable, must be solid and must not complicate the protocol unduly.

The ZIP Owner may update the draft as necessary in the git repository. Updates to drafts should also be submitted by the Owner as pull requests.

ZIP Numbering Conventions

The ZIP Editors currently use the following conventions when numbering ZIPs:

@@ -130,7 +130,6 @@ License: Original-Authors: Discussions-To: Pull-Request: -Network Upgrade: Obsoleted by: Updated by: Obsoletes: @@ -140,7 +139,7 @@ Updates:

If there are multiple Owners, each should be on a separate line.

While a ZIP is in public 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 Pull-Request header, if present, gives an URL to a Pull Request for the ZIP.

-

The Category header specifies the type of ZIP: Consensus, Standards Track, Informational, or Process.

+

The Category header specifies the type of ZIP, as described in ZIP categories. Multiple categories MAY be specified, separated by " / ".

The Created header records the date that the ZIP was submitted. Dates should be in yyyy-mm-dd format, e.g. 2001-08-14.

For ZIPs written in reStructuredText, URLs in header fields SHOULD be surrounded by < >; this ensures that the link is rendered correctly.

@@ -149,17 +148,30 @@ Updates:

ZIP categories

-

There are several kinds of ZIP:

- -

Consensus and Standards Track ZIPs consist of two parts: a design document and a reference implementation.

- +

Each ZIP is in one or more of the following categories, as specified in the Category header:

+
+
Consensus
+
Rules that affect the consensus protocol followed by all Zcash implementations.
+
Standards
+
Non-consensus changes affecting most or all Zcash implementations, or the interoperability of applications using Zcash.
+
Process
+
A Process ZIP describes a process surrounding Zcash, or proposes a change to (or an event in) a process. They may propose an implementation, but not to Zcash's codebase; they often require community consensus; unlike Informational ZIPs, they are more than recommendations, and users are typically not free to ignore them. Examples include procedures, guidelines, changes to the decision-making process, and changes to the tools or environment used in Zcash development.
+
Consensus Process
+
A subcategory of Process ZIP that specifies requirements and processes that are to be realized by one or more Consensus ZIPs, and/or by social consensus of the Zcash community.
+
Informational
+
An Informational ZIP describes non-consensus Zcash design issues, or general guidelines or information for the Zcash community. These ZIPs do not not necessarily represent a Zcash community consensus or recommendation, so users and implementors are free to ignore Informational ZIPs or follow their advice.
+
Network
+
Specifications of peer-to-peer networking behaviour.
+
RPC
+
Specifications of the RPC interface provided by zcashd nodes.
+
Wallet
+
Specifications affecting wallets (e.g. non-consensus changes to how transactions, addresses, etc. are constructed or interpreted).
+
Ecosystem
+
Specifications otherwise useful to the Zcash ecosystem.
+

New categories may be added by consensus among the ZIP Editors.

+

Consensus and Standards ZIPs SHOULD have a Reference Implementation section, which includes or (more often) links to an implementation.

+

Consensus ZIPs SHOULD have a Deployment section, describing how and when the consensus change is planned to be deployed (for example, in a particular network upgrade).

ZIP Status Field

More details on the status workflow are given in the section below.

Specification

Owners of a ZIP may decide on their own to change the status between Draft or Withdrawn.

-

A ZIP may only change status from Draft (or Rejected) to Proposed, when the Owner deems it is complete and there is rough consensus on the forums, validated by both the Electric Coin Company and Zcash Foundation Editors. One Editor will not suffice -- there needs to be consensus among the Editors. If it's a Standards Track ZIP, upon changing status to Proposed the Editors will add the optional Network Upgrade header to the preamble, indicating the intent for the ZIP to be implemented in the specified network upgrade. (All Network Upgrade schedules will be distributed via the Zcash Community Forum by the Editors.)

-

A Standards Track ZIP may only change status from Proposed to Implemented once the Owner provides an associated reference implementation, typically in the period after the network upgrade's specification freeze but before the implementation audit. If the Owner misses this deadline, the Editors or Owner(s) may choose to update the Network Upgrade header to target another upgrade, at their discretion.

-

ZIPs should be changed from Draft or Proposed status, to Rejected status, upon request by any person, if they have not made progress in one year. Such a ZIP may be changed to Draft status if the Owner provides revisions that meaningfully address public criticism of the proposal, or to Proposed status if it meets the criteria required as described in the previous paragraph.

-

A Consensus or Standards Track ZIP becomes Final when its associated network upgrade or other protocol change is activated on Zcash's mainnet.

+

A ZIP may only change status from Draft (or Rejected) to Proposed, when the Owner deems it is complete and there is rough consensus on the forums, validated by both the Electric Coin Company and Zcash Foundation Editors. One Editor will not suffice — there needs to be consensus among the Editors. If it's a Consensus ZIP, a Deployment section MUST be present in order for the ZIP to change status to Proposed. Typically, although not necessarily, this will specify a network upgrade in which the consensus change is to activate.

+

A Standards ZIP may only change status from Proposed to Implemented once the Owners provide an associated reference implementation, typically in the period after the network upgrade's specification freeze but before the implementation audit. If the Owners miss this deadline, the Editors or Owners MAY choose to update the Deployment section of the ZIP to target another upgrade, at their discretion.

+

ZIPs should be changed from Draft or Proposed status, to Rejected status, upon request by any person, if they have not made progress in one year. Such a ZIP may be changed to Draft status if the Owner provides revisions that meaningfully address public criticism of the proposal, or to Proposed status if it meets the criteria required as described in the previous paragraphs.

+

A Consensus or Standards ZIP becomes Final when its associated network upgrade or other protocol change is activated on Zcash's mainnet.

A Process or Informational ZIP may change status from Draft to Active when it achieves rough consensus on the forum or PR. Such a proposal is said to have rough consensus if it has been open to discussion on the forum or GitHub PR for at least one month, and no person maintains any unaddressed substantiated objections to it. Addressed or obstructive objections may be ignored/overruled by general agreement that they have been sufficiently addressed, but clear reasoning must be given in such circumstances.

When an Active or Final ZIP is no longer relevant, its status may be changed to Obsolete. This change must also be objectively verifiable and/or discussed. Final ZIPs may be updated; the specification is still in force but modified by another specified ZIP or ZIPs (check the optional Updated-by header).

diff --git a/zip-0000.rst b/zip-0000.rst index 11c7ae9b..f06e9804 100644 --- a/zip-0000.rst +++ b/zip-0000.rst @@ -96,8 +96,8 @@ or new idea. The more focused the ZIP, the more successful it tends to be. If in doubt, split your ZIP into several well-focused ones. When the ZIP draft is complete, the ZIP Editors will assign the ZIP a -number, label it as Standards Track, Informational, or Process, and -merge the pull request to the ZIPs git repository. The ZIP Editors +number (if that has not already been done) and one or more Categories, +and merge the pull request to the ZIPs git repository. The ZIP Editors will not unreasonably reject a ZIP. Reasons for rejecting ZIPs include duplication of effort, disregard for formatting rules, being too unfocused or too broad, being technically unsound, not providing proper @@ -331,7 +331,6 @@ The following additional header fields are OPTIONAL:: Original-Authors: Discussions-To: Pull-Request: - Network Upgrade: Obsoleted by: Updated by: Obsoletes: @@ -352,8 +351,9 @@ discussed privately with the Owner. The Pull-Request header, if present, gives an URL to a Pull Request for the ZIP. -The Category header specifies the type of ZIP: Consensus, Standards Track, -Informational, or Process. +The Category header specifies the type of ZIP, as described in +`ZIP categories`_. Multiple categories MAY be specified, separated by +" ``/`` ". The Created header records the date that the ZIP was submitted. Dates should be in yyyy-mm-dd format, e.g. 2001-08-14. @@ -373,38 +373,52 @@ subdirectory named zip-XXXX. ZIP categories ============== -There are several kinds of ZIP: +Each ZIP is in one or more of the following categories, as specified +in the Category header: -* A Consensus ZIP describes a change that affects the consensus protocol - followed by all Zcash implementations. - -* A Standards Track ZIP describes any non-consensus change that affects - most or all Zcash implementations, such as a change to the network - protocol, or any change or addition that affects the interoperability - of applications using Zcash. - -Consensus and Standards Track ZIPs consist of two parts: a design document -and a reference implementation. - -* An Informational ZIP describes Zcash design issues, or general - guidelines or information for the Zcash community, that do not fall - into either of the above categories. Informational ZIPs do not - necessarily represent a Zcash community consensus or recommendation, - so users and implementers are free to ignore Informational ZIPs or - follow their advice. - -* A Process ZIP describes a process surrounding Zcash, or proposes a - change to (or an event in) a process. Process ZIPs are like Standards - Track ZIPs but apply to areas other than the Zcash protocol itself. - They may propose an implementation, but not to Zcash's codebase; they - often require community consensus; unlike Informational ZIPs, they - are more than recommendations, and users are typically not free to - ignore them. Examples include procedures, guidelines, changes to the - decision-making process, and changes to the tools or environment used - in Zcash development. +Consensus + Rules that affect the consensus protocol followed by all Zcash + implementations. +Standards + Non-consensus changes affecting most or all Zcash implementations, or + the interoperability of applications using Zcash. +Process + A Process ZIP describes a process surrounding Zcash, or proposes a + change to (or an event in) a process. They may propose an implementation, + but not to Zcash's codebase; they often require community consensus; + unlike Informational ZIPs, they are more than recommendations, and users + are typically not free to ignore them. Examples include procedures, + guidelines, changes to the decision-making process, and changes to the + tools or environment used in Zcash development. +Consensus Process + A subcategory of Process ZIP that specifies requirements and processes + that are to be realized by one or more Consensus ZIPs, and/or by social + consensus of the Zcash community. +Informational + An Informational ZIP describes non-consensus Zcash design issues, or + general guidelines or information for the Zcash community. These ZIPs + do not not necessarily represent a Zcash community consensus or + recommendation, so users and implementors are free to ignore + Informational ZIPs or follow their advice. +Network + Specifications of peer-to-peer networking behaviour. +RPC + Specifications of the RPC interface provided by zcashd nodes. +Wallet + Specifications affecting wallets (e.g. non-consensus changes to how + transactions, addresses, etc. are constructed or interpreted). +Ecosystem + Specifications otherwise useful to the Zcash ecosystem. New categories may be added by consensus among the ZIP Editors. +Consensus and Standards ZIPs SHOULD have a Reference Implementation section, +which includes or (more often) links to an implementation. + +Consensus ZIPs SHOULD have a Deployment section, describing how and when +the consensus change is planned to be deployed (for example, in a particular +network upgrade). + ZIP Status Field ================ @@ -430,10 +444,10 @@ ZIP Status Field year. Can revert back to Draft/Proposed if the Owner resumes work or resolves issues preventing consensus. -* Implemented: When a Consensus or Standards Track ZIP has a working +* Implemented: When a Consensus or Standards ZIP has a working reference implementation but before activation on the Zcash network. -* Final: When a Consensus or Standards Track ZIP is both implemented +* Final: When a Consensus or Standards ZIP is both implemented and activated on the Zcash network. * Obsolete: The status when a ZIP is no longer relevant (typically when @@ -450,30 +464,28 @@ Draft or Withdrawn. A ZIP may only change status from Draft (or Rejected) to Proposed, when the Owner deems it is complete and there is rough consensus on the forums, validated by both the Electric Coin Company and Zcash Foundation -Editors. One Editor will not suffice -- there needs to be consensus -among the Editors. If it's a Standards Track ZIP, upon changing status to -Proposed the Editors will add the optional ``Network Upgrade`` header -to the preamble, indicating the intent for the ZIP to be implemented in -the specified network upgrade. (All ``Network Upgrade`` schedules will be -distributed via the Zcash Community Forum by the Editors.) +Editors. One Editor will not suffice — there needs to be consensus +among the Editors. If it's a Consensus ZIP, a Deployment section MUST +be present in order for the ZIP to change status to Proposed. Typically, +although not necessarily, this will specify a network upgrade in which +the consensus change is to activate. -A Standards Track ZIP may only change status from Proposed to -Implemented once the Owner provides an associated reference -implementation, typically in the period after the network upgrade's -specification freeze but before the implementation audit. If the Owner -misses this deadline, the Editors or Owner(s) may choose to update -the ``Network Upgrade`` header to target another upgrade, at their -discretion. +A Standards ZIP may only change status from Proposed to Implemented once +the Owners provide an associated reference implementation, typically in +the period after the network upgrade's specification freeze but before +the implementation audit. If the Owners miss this deadline, the Editors +or Owners MAY choose to update the Deployment section of the ZIP to +target another upgrade, at their discretion. ZIPs should be changed from Draft or Proposed status, to Rejected status, upon request by any person, if they have not made progress in one year. Such a ZIP may be changed to Draft status if the Owner provides revisions that meaningfully address public criticism of the proposal, or to Proposed status if it meets the criteria required as -described in the previous paragraph. +described in the previous paragraphs. -A Consensus or Standards Track ZIP becomes Final when its associated -network upgrade or other protocol change is activated on Zcash's mainnet. +A Consensus or Standards ZIP becomes Final when its associated network +upgrade or other protocol change is activated on Zcash's mainnet. A Process or Informational ZIP may change status from Draft to Active when it achieves rough consensus on the forum or PR. Such a proposal is @@ -618,4 +630,3 @@ References .. [#conduct] `Zcash Code of Conduct `_ .. [#rst] `reStructuredText documentation `_ .. [#latex] `LaTeX — a document preparation system `_ - diff --git a/zip-0001.html b/zip-0001.html index 81c1bcc2..5068a86f 100644 --- a/zip-0001.html +++ b/zip-0001.html @@ -9,7 +9,7 @@ 
ZIP: 1
 Title: Network Upgrade Policy and Scheduling
 Status: Reserved
-Category: Process
+Category: Consensus Process
 Discussions-To: <https://github.com/zcash/zips/issues/343>
diff --git a/zip-0001.rst b/zip-0001.rst index fa61af20..35aec9ee 100644 --- a/zip-0001.rst +++ b/zip-0001.rst @@ -3,5 +3,5 @@ ZIP: 1 Title: Network Upgrade Policy and Scheduling Status: Reserved - Category: Process + Category: Consensus Process Discussions-To: diff --git a/zip-0022.html b/zip-0022.html index a16a40e6..feb2b7cd 100644 --- a/zip-0022.html +++ b/zip-0022.html @@ -9,7 +9,7 @@ 
ZIP: 22
 Title: Specification of getblocktemplate for Zcash
 Status: Reserved
-Category: Informational
+Category: RPC
 Discussions-To: <https://github.com/zcash/zips/issues/349>
diff --git a/zip-0022.rst b/zip-0022.rst index 02968b5f..fa94d99d 100644 --- a/zip-0022.rst +++ b/zip-0022.rst @@ -3,5 +3,5 @@ ZIP: 22 Title: Specification of getblocktemplate for Zcash Status: Reserved - Category: Informational + Category: RPC Discussions-To: diff --git a/zip-0032.html b/zip-0032.html index 913536a3..cb8dc5c6 100644 --- a/zip-0032.html +++ b/zip-0032.html @@ -15,7 +15,7 @@ Credits: Pieter Wuille Marek Palatinus Pavol Rusnak Status: Final -Category: Standards Track +Category: Standards / Wallet Created: 2018-05-22 License: MIT

diff --git a/zip-0032.rst b/zip-0032.rst index a953f7c4..4b68a03d 100644 --- a/zip-0032.rst +++ b/zip-0032.rst @@ -8,7 +8,7 @@ Marek Palatinus Pavol Rusnak Status: Final - Category: Standards Track + Category: Standards / Wallet Created: 2018-05-22 License: MIT diff --git a/zip-0173.html b/zip-0173.html index a87240e4..3865414a 100644 --- a/zip-0173.html +++ b/zip-0173.html @@ -14,7 +14,7 @@ Credits: Pieter Wuille <pieter.wuille@gmail.com> Rusty Russell Mark Friedenbach Status: Final -Category: Wallet +Category: Standards / Wallet Created: 2018-06-13 License: MIT

Terminology

diff --git a/zip-0173.rst b/zip-0173.rst index bcb1f063..5e93472b 100644 --- a/zip-0173.rst +++ b/zip-0173.rst @@ -8,7 +8,7 @@ Rusty Russell Mark Friedenbach Status: Final - Category: Wallet + Category: Standards / Wallet Created: 2018-06-13 License: MIT diff --git a/zip-0205.html b/zip-0205.html index e58a129f..e240b849 100644 --- a/zip-0205.html +++ b/zip-0205.html @@ -11,7 +11,7 @@ Title: Deployment of the Sapling Network Upgrade Owners: Daira Hopwood <daira@electriccoin.co> Credits: Simon Liu Status: Final -Category: Consensus +Category: Consensus / Network Created: 2018-10-08 License: MIT

Terminology

diff --git a/zip-0205.rst b/zip-0205.rst index ab7e32ab..a76a4871 100644 --- a/zip-0205.rst +++ b/zip-0205.rst @@ -5,7 +5,7 @@ Owners: Daira Hopwood Credits: Simon Liu Status: Final - Category: Consensus + Category: Consensus / Network Created: 2018-10-08 License: MIT diff --git a/zip-0206.html b/zip-0206.html index 8169c975..7950596d 100644 --- a/zip-0206.html +++ b/zip-0206.html @@ -11,7 +11,7 @@ Title: Deployment of the Blossom Network Upgrade Owners: Daira Hopwood <daira@electriccoin.co> Credits: Simon Liu Status: Final -Category: Consensus +Category: Consensus / Network Created: 2019-07-29 License: MIT

Terminology

diff --git a/zip-0206.rst b/zip-0206.rst index 31a8ee59..2a421776 100644 --- a/zip-0206.rst +++ b/zip-0206.rst @@ -5,7 +5,7 @@ Owners: Daira Hopwood Credits: Simon Liu Status: Final - Category: Consensus + Category: Consensus / Network Created: 2019-07-29 License: MIT diff --git a/zip-0250.html b/zip-0250.html index 0f9a89d7..cd4b237c 100644 --- a/zip-0250.html +++ b/zip-0250.html @@ -10,7 +10,7 @@ Title: Deployment of the Heartwood Network Upgrade Owners: Daira Hopwood <daira@electriccoin.co> Status: Final -Category: Consensus +Category: Consensus / Network Created: 2020-02-28 License: MIT

Terminology

diff --git a/zip-0250.rst b/zip-0250.rst index 4868d7ad..14f5bfd7 100644 --- a/zip-0250.rst +++ b/zip-0250.rst @@ -4,7 +4,7 @@ Title: Deployment of the Heartwood Network Upgrade Owners: Daira Hopwood Status: Final - Category: Consensus + Category: Consensus / Network Created: 2020-02-28 License: MIT diff --git a/zip-0251.html b/zip-0251.html index 85907bb4..05821596 100644 --- a/zip-0251.html +++ b/zip-0251.html @@ -10,7 +10,7 @@ Title: Deployment of the Canopy Network Upgrade Owners: Daira Hopwood <daira@electriccoin.co> Status: Implemented (zcashd) -Category: Consensus +Category: Consensus / Network Created: 2020-02-28 License: MIT

Terminology

diff --git a/zip-0251.rst b/zip-0251.rst index bf55fb74..8a80e111 100644 --- a/zip-0251.rst +++ b/zip-0251.rst @@ -4,7 +4,7 @@ Title: Deployment of the Canopy Network Upgrade Owners: Daira Hopwood Status: Implemented (zcashd) - Category: Consensus + Category: Consensus / Network Created: 2020-02-28 License: MIT diff --git a/zip-0252.html b/zip-0252.html index 79f72ccd..607c54ab 100644 --- a/zip-0252.html +++ b/zip-0252.html @@ -10,7 +10,7 @@ Title: Deployment of the NU5 Network Upgrade Owners: Daira Hopwood <daira@electriccoin.co> Status: Reserved -Category: Consensus +Category: Consensus / Network Discussions-To: <https://github.com/zcash/zips/issues/397>
diff --git a/zip-0252.rst b/zip-0252.rst index 1dfa4f0d..3308511e 100644 --- a/zip-0252.rst +++ b/zip-0252.rst @@ -4,5 +4,5 @@ Title: Deployment of the NU5 Network Upgrade Owners: Daira Hopwood Status: Reserved - Category: Consensus + Category: Consensus / Network Discussions-To: diff --git a/zip-0301.html b/zip-0301.html index 10238141..ef12f081 100644 --- a/zip-0301.html +++ b/zip-0301.html @@ -15,7 +15,7 @@ Credits: 5a1t Jelle Bourdeaud'hui (razakal) ocminer Status: Final -Category: Ecosystem +Category: Standards / Ecosystem Created: 2016-09-23 License: MIT

Terminology

diff --git a/zip-0301.rst b/zip-0301.rst index 86430d5d..07c10a32 100644 --- a/zip-0301.rst +++ b/zip-0301.rst @@ -9,7 +9,7 @@ Jelle Bourdeaud'hui (razakal) ocminer Status: Final - Category: Ecosystem + Category: Standards / Ecosystem Created: 2016-09-23 License: MIT diff --git a/zip-0302.html b/zip-0302.html index 1edcf17f..7bb02357 100644 --- a/zip-0302.html +++ b/zip-0302.html @@ -11,7 +11,7 @@ Title: Standardized Memo Field Format Owners: Jack Grigg <jack@electriccoin.co> Original-Authors: Jay Graber Status: Reserved -Category: Standards +Category: Standards / RPC / Wallet Discussions-To: <https://github.com/zcash/zips/issues/366> Pull-Request: <https://github.com/zcash/zips/pull/105>
diff --git a/zip-0302.rst b/zip-0302.rst index cd0dccea..913849f7 100644 --- a/zip-0302.rst +++ b/zip-0302.rst @@ -5,6 +5,6 @@ Owners: Jack Grigg Original-Authors: Jay Graber Status: Reserved - Category: Standards + Category: Standards / RPC / Wallet Discussions-To: Pull-Request: diff --git a/zip-0303.html b/zip-0303.html index b4fa937a..56d84250 100644 --- a/zip-0303.html +++ b/zip-0303.html @@ -11,7 +11,7 @@ Title: Sprout Payment Disclosure Owners: Deirdre Connolly <deirdre@zfnd.org> Original-Authors: Simon Liu Status: Reserved -Category: Informational +Category: Standards / RPC / Wallet Pull-Request: <https://github.com/zcash/zips/pull/119>
diff --git a/zip-0303.rst b/zip-0303.rst index 5054bb51..54e439e8 100644 --- a/zip-0303.rst +++ b/zip-0303.rst @@ -5,5 +5,5 @@ Owners: Deirdre Connolly Original-Authors: Simon Liu Status: Reserved - Category: Informational + Category: Standards / RPC / Wallet Pull-Request: diff --git a/zip-0304.html b/zip-0304.html index 70964418..b963db71 100644 --- a/zip-0304.html +++ b/zip-0304.html @@ -13,7 +13,7 @@ Owners: Jack Grigg <jack@electriccoin.co> Credits: Daira Hopwood <daira@electriccoin.co> Sean Bowe <sean@electriccoin.co> Status: Draft -Category: Wallet +Category: Standards / RPC / Wallet Created: 2020-06-01 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/345> diff --git a/zip-0304.rst b/zip-0304.rst index 069ee324..8db063aa 100644 --- a/zip-0304.rst +++ b/zip-0304.rst @@ -6,7 +6,7 @@ Credits: Daira Hopwood Sean Bowe Status: Draft - Category: Wallet + Category: Standards / RPC / Wallet Created: 2020-06-01 License: MIT Discussions-To: diff --git a/zip-0307.html b/zip-0307.html index 28383f7c..b83fd737 100644 --- a/zip-0307.html +++ b/zip-0307.html @@ -13,7 +13,7 @@ Owners: Jack Grigg <jack@electriccoin.co> Daira Hopwood <daira@electriccoin.co> Original-Authors: George Tankersley Credits: Matthew Green -Category: Standards Track +Category: Standards / Ecosystem Status: Draft Created: 2018-09-17 License: MIT diff --git a/zip-0307.rst b/zip-0307.rst index e0f9aae3..e44cf9fe 100644 --- a/zip-0307.rst +++ b/zip-0307.rst @@ -6,7 +6,7 @@ Daira Hopwood Original-Authors: George Tankersley Credits: Matthew Green - Category: Standards Track + Category: Standards / Ecosystem Status: Draft Created: 2018-09-17 License: MIT diff --git a/zip-0308.html b/zip-0308.html index 6c3e6387..59dd6117 100644 --- a/zip-0308.html +++ b/zip-0308.html @@ -12,7 +12,7 @@ Owner: Daira Hopwood <daira@electriccoin.co> Original-Authors: Daira Hopwood Eirik Ogilvie-Wigley Status: Final -Category: RPC/Wallet +Category: Standards / RPC / Wallet Created: 2018-11-27 License: MIT

Terminology

diff --git a/zip-0308.rst b/zip-0308.rst index fc2cfc7f..f4dfa8d5 100644 --- a/zip-0308.rst +++ b/zip-0308.rst @@ -6,7 +6,7 @@ Original-Authors: Daira Hopwood Eirik Ogilvie-Wigley Status: Final - Category: RPC/Wallet + Category: Standards / RPC / Wallet Created: 2018-11-27 License: MIT diff --git a/zip-0309.html b/zip-0309.html index fd671a8f..ae6f73f8 100644 --- a/zip-0309.html +++ b/zip-0309.html @@ -13,7 +13,7 @@ Owners: J. Ayo Akinyele <ayo@boltlabs.io> Credits: Ian Miers Matthew Green Status: Reserved -Category: Consensus +Category: Standards / Ecosystem Created: 2019-07-15 Discussions-To: <https://github.com/zcash/zips/issues/2353> Pull-Request: <https://github.com/zcash/zips/pull/216> diff --git a/zip-0309.rst b/zip-0309.rst index dc86bc80..bf5ca0d3 100644 --- a/zip-0309.rst +++ b/zip-0309.rst @@ -7,7 +7,7 @@ Credits: Ian Miers Matthew Green Status: Reserved - Category: Consensus + Category: Standards / Ecosystem Created: 2019-07-15 Discussions-To: Pull-Request: diff --git a/zip-0311.html b/zip-0311.html index ddc58708..9d6a86e9 100644 --- a/zip-0311.html +++ b/zip-0311.html @@ -10,7 +10,7 @@ Title: Sapling Payment Disclosure Owners: Deirdre Connolly <deirdre@zfnd.org> Status: Reserved -Category: Informational +Category: Standards / RPC / Wallet Discussions-To: <https://github.com/zcash/zips/issues/387>
diff --git a/zip-0311.rst b/zip-0311.rst index d2746e87..94b7b0e8 100644 --- a/zip-0311.rst +++ b/zip-0311.rst @@ -4,5 +4,5 @@ Title: Sapling Payment Disclosure Owners: Deirdre Connolly Status: Reserved - Category: Informational + Category: Standards / RPC / Wallet Discussions-To: diff --git a/zip-0312.html b/zip-0312.html index 841b2cc8..c5d670b1 100644 --- a/zip-0312.html +++ b/zip-0312.html @@ -9,7 +9,7 @@ 
ZIP: 312
 Title: Shielded Multisignatures using FROST
 Status: Reserved
-Category: Standards
+Category: Standards / RPC / Wallet
 Discussions-To: <https://github.com/zcash/zips/issues/382>
diff --git a/zip-0312.rst b/zip-0312.rst index dd472cb4..8f9c3c40 100644 --- a/zip-0312.rst +++ b/zip-0312.rst @@ -3,5 +3,5 @@ ZIP: 312 Title: Shielded Multisignatures using FROST Status: Reserved - Category: Standards + Category: Standards / RPC / Wallet Discussions-To: diff --git a/zip-0321.html b/zip-0321.html index d6eb4d4c..3030e4b4 100644 --- a/zip-0321.html +++ b/zip-0321.html @@ -11,7 +11,7 @@ Title: Payment Request URIs Owners: Kris Nuttycombe (kris@electriccoin.co) Daira Hopwood (daira@electriccoin.co) Status: Proposed -Category: Wallet +Category: Standards / Wallet Created: 2020-08-28 Discussions-To: <https://github.com/zcash/zips/issues/347> Pull-Request: <https://github.com/zcash/zips/pull/395> diff --git a/zip-0321.rst b/zip-0321.rst index 50c8ec47..8b12a74f 100644 --- a/zip-0321.rst +++ b/zip-0321.rst @@ -5,7 +5,7 @@ Owners: Kris Nuttycombe (kris@electriccoin.co) Daira Hopwood (daira@electriccoin.co) Status: Proposed - Category: Wallet + Category: Standards / Wallet Created: 2020-08-28 Discussions-To: Pull-Request: diff --git a/zip-1001.html b/zip-1001.html index 2acdee7a..8fabcb22 100644 --- a/zip-1001.html +++ b/zip-1001.html @@ -10,7 +10,7 @@ Title: Keep the Block Distribution as Initially Defined — 90% to Miners Owner: mistfpga (zcash forums) <steve@mistfpga.net> Status: Obsolete -Category: Consensus +Category: Consensus Process Created: 2019-08-01 License: CC BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0/> Discussions-To: <https://forum.zcashcommunity.com/t/zip-proposal-keep-the-block-distribution-as-initaly-defined-90-to-miners/33843> diff --git a/zip-1001.rst b/zip-1001.rst index c78f9529..a8e351bf 100644 --- a/zip-1001.rst +++ b/zip-1001.rst @@ -4,7 +4,7 @@ Title: Keep the Block Distribution as Initially Defined — 90% to Miners Owner: mistfpga (zcash forums) Status: Obsolete - Category: Consensus + Category: Consensus Process Created: 2019-08-01 License: CC BY-SA 4.0 Discussions-To: diff --git a/zip-1002.html b/zip-1002.html index af5c7157..c90fae45 100644 --- a/zip-1002.html +++ b/zip-1002.html @@ -10,7 +10,7 @@ Title: Opt-in Donation Feature Owner: mistfpga (zcash forums) <steve@mistfpga.net> Status: Obsolete -Category: Standards Track +Category: Consensus Process Created: 2019-07-17 License: CC BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0/> Discussions-To: <https://forum.zcashcommunity.com/t/zip-proposal-a-genuine-opt-in-protocol-level-development-donation-option/33846> diff --git a/zip-1002.rst b/zip-1002.rst index 05655532..169ebe16 100644 --- a/zip-1002.rst +++ b/zip-1002.rst @@ -4,7 +4,7 @@ Title: Opt-in Donation Feature Owner: mistfpga (zcash forums) Status: Obsolete - Category: Standards Track + Category: Consensus Process Created: 2019-07-17 License: CC BY-SA 4.0 Discussions-To: diff --git a/zip-1003.html b/zip-1003.html index a4427f47..37307c04 100644 --- a/zip-1003.html +++ b/zip-1003.html @@ -10,7 +10,7 @@ Title: 20% Split Evenly Between the ECC and the Zcash Foundation, and a Voting System Mandate Owner: aristarchus (zcash forums) Status: Obsolete -Category: Consensus / Process +Category: Consensus Process Created: 2019-06-19 License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/dev-fund-proposal-20-split-between-the-ecc-and-the-foundation/33862> diff --git a/zip-1003.rst b/zip-1003.rst index c60e4083..08cccc3f 100644 --- a/zip-1003.rst +++ b/zip-1003.rst @@ -4,7 +4,7 @@ Title: 20% Split Evenly Between the ECC and the Zcash Foundation, and a Voting System Mandate Owner: aristarchus (zcash forums) Status: Obsolete - Category: Consensus / Process + Category: Consensus Process Created: 2019-06-19 License: MIT Discussions-To: diff --git a/zip-1004.html b/zip-1004.html index 59013c64..6f9e164b 100644 --- a/zip-1004.html +++ b/zip-1004.html @@ -10,7 +10,7 @@ Title: Miner-Directed Dev Fund Owner: Andrew Miller (@amiller on zcash forums) Status: Obsolete -Category: Consensus +Category: Consensus Process Created: 2019-06-19 License: public domain Discussions-To: <https://forum.zcashcommunity.com/t/dev-fund-proposal-miner-directed-dev-fund-was-20-to-any-combination-of-ecc-zfnd-parity-or-burn/33864> diff --git a/zip-1004.rst b/zip-1004.rst index 4c459686..3e7e993d 100644 --- a/zip-1004.rst +++ b/zip-1004.rst @@ -4,7 +4,7 @@ Title: Miner-Directed Dev Fund Owner: Andrew Miller (@amiller on zcash forums) Status: Obsolete - Category: Consensus + Category: Consensus Process Created: 2019-06-19 License: public domain Discussions-To: diff --git a/zip-1005.html b/zip-1005.html index 3feb809b..2cc833e0 100644 --- a/zip-1005.html +++ b/zip-1005.html @@ -10,7 +10,7 @@ Title: Zcash Community Funding System Owner: Dimitris Apostolou <dimitris.apostolou@icloud.com> Status: Obsolete -Category: Consensus +Category: Consensus Process Created: 2019-06-23 License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/zip-proposal-zcfs-zcash-community-funding-system/33898> diff --git a/zip-1005.rst b/zip-1005.rst index 304de1fe..d7c1b570 100644 --- a/zip-1005.rst +++ b/zip-1005.rst @@ -4,7 +4,7 @@ Title: Zcash Community Funding System Owner: Dimitris Apostolou Status: Obsolete - Category: Consensus + Category: Consensus Process Created: 2019-06-23 License: MIT Discussions-To: diff --git a/zip-1006.html b/zip-1006.html index 7229ec63..515dabfc 100644 --- a/zip-1006.html +++ b/zip-1006.html @@ -13,7 +13,7 @@ Owners: James Todaro <james@blocktown.capital> Credits: Mario Laul Chris Burniske Status: Obsolete -Category: Consensus / Process +Category: Consensus Process Created: 2019-08-31 License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/blocktown-development-fund-proposal-10-to-a-2-of-3-multisig-with-community-involved-third-entity/34782> diff --git a/zip-1006.rst b/zip-1006.rst index 02bfda16..d54e17f9 100644 --- a/zip-1006.rst +++ b/zip-1006.rst @@ -7,7 +7,7 @@ Credits: Mario Laul Chris Burniske Status: Obsolete - Category: Consensus / Process + Category: Consensus Process Created: 2019-08-31 License: MIT Discussions-To: diff --git a/zip-1007.html b/zip-1007.html index f3b52edf..1f5c7089 100644 --- a/zip-1007.html +++ b/zip-1007.html @@ -11,7 +11,7 @@ Title: Enforce Development Fund Commitments with a Legal Charter Owners: @lex-node (zcash forums) @mistfpga (zcash forums) <steve@mistfpga.net> Status: Obsolete -Category: Process +Category: Concensus Process Created: 2019-08-24 License: CC BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0/> Discussions-To: <https://forum.zcashcommunity.com/t/dev-fund-supplemental-proposal-enforce-devfund-commitments-with-legal-charter/34709> diff --git a/zip-1007.rst b/zip-1007.rst index b32461a1..18619c96 100644 --- a/zip-1007.rst +++ b/zip-1007.rst @@ -5,7 +5,7 @@ Owners: @lex-node (zcash forums) @mistfpga (zcash forums) Status: Obsolete - Category: Process + Category: Concensus Process Created: 2019-08-24 License: CC BY-SA 4.0 Discussions-To: diff --git a/zip-1008.html b/zip-1008.html index c98c0fd6..018d567f 100644 --- a/zip-1008.html +++ b/zip-1008.html @@ -11,7 +11,7 @@ Title: Fund ECC for Two More Years Owners: @kek (zcash forums) @mistfpga (zcash forums) <steve@mistfpga.net> Status: Obsolete -Category: Consensus +Category: Consensus Process Created: 2019-09-02 License: CC BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0/> Discussions-To: <https://forum.zcashcommunity.com/t/kek-s-proposal-fund-ecc-for-2-more-years/34778> diff --git a/zip-1008.rst b/zip-1008.rst index 31b6a091..3f811faf 100644 --- a/zip-1008.rst +++ b/zip-1008.rst @@ -5,7 +5,7 @@ Owners: @kek (zcash forums) @mistfpga (zcash forums) Status: Obsolete - Category: Consensus + Category: Consensus Process Created: 2019-09-02 License: CC BY-SA 4.0 Discussions-To: diff --git a/zip-1009.html b/zip-1009.html index 702d2da2..51568426 100644 --- a/zip-1009.html +++ b/zip-1009.html @@ -10,7 +10,7 @@ Title: Five-Entity Strategic Council Owner: Avichal Garg <avichalgarg@electriccapital.com> Status: Obsolete -Category: Process +Category: Consensus Process Created: 2019-08-28 License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/dev-fund-proposal-5-entity-strategic-council-approach/34801> diff --git a/zip-1009.rst b/zip-1009.rst index b5e526bf..2320b3b7 100644 --- a/zip-1009.rst +++ b/zip-1009.rst @@ -4,7 +4,7 @@ Title: Five-Entity Strategic Council Owner: Avichal Garg Status: Obsolete - Category: Process + Category: Consensus Process Created: 2019-08-28 License: MIT Discussions-To: diff --git a/zip-1010.html b/zip-1010.html index 00d259a3..99b3f3d7 100644 --- a/zip-1010.html +++ b/zip-1010.html @@ -16,7 +16,7 @@ Credits: Matt Luongo lex-node and many others Status: Obsolete -Category: Consensus +Category: Consensus Process Created: 2019-08-31 License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/a-grand-compromise-synthesis-zip-proposal/34812/> diff --git a/zip-1010.rst b/zip-1010.rst index 1fce3bba..ee2f652f 100644 --- a/zip-1010.rst +++ b/zip-1010.rst @@ -10,7 +10,7 @@ lex-node and many others Status: Obsolete - Category: Consensus + Category: Consensus Process Created: 2019-08-31 License: MIT Discussions-To: diff --git a/zip-1011.html b/zip-1011.html index 1c8d9913..a0040d78 100644 --- a/zip-1011.html +++ b/zip-1011.html @@ -11,7 +11,7 @@ Title: Decentralize the Dev Fee Owner: Matt Luongo <matt@thesis.co> Status: Obsolete -Category: Process +Category: Consensus Process Created: 2019-09-27 License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/decentralizing-the-dev-fee/35252> diff --git a/zip-1011.rst b/zip-1011.rst index d1fa603f..dc5783d7 100644 --- a/zip-1011.rst +++ b/zip-1011.rst @@ -4,7 +4,7 @@ Title: Decentralize the Dev Fee Owner: Matt Luongo Status: Obsolete - Category: Process + Category: Consensus Process Created: 2019-09-27 License: MIT Discussions-To: diff --git a/zip-1012.html b/zip-1012.html index c52637d6..7d740148 100644 --- a/zip-1012.html +++ b/zip-1012.html @@ -10,7 +10,7 @@ Title: Dev Fund to ECC + ZF + Major Grants Owner: Eran Tromer <eran@tromer.org> Status: Obsolete -Category: Consensus / Process +Category: Consensus Process Created: 2019-11-10 License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/dev-fund-proposal-dev-fund-to-ecc-zfnd-major-grants/35364> diff --git a/zip-1012.rst b/zip-1012.rst index 41f386f8..b8a2c9be 100644 --- a/zip-1012.rst +++ b/zip-1012.rst @@ -4,7 +4,7 @@ Title: Dev Fund to ECC + ZF + Major Grants Owner: Eran Tromer Status: Obsolete - Category: Consensus / Process + Category: Consensus Process Created: 2019-11-10 License: MIT Discussions-To: diff --git a/zip-1013.html b/zip-1013.html index 331d65e5..6598b2ce 100644 --- a/zip-1013.html +++ b/zip-1013.html @@ -10,7 +10,7 @@ Title: Keep It Simple, Zcashers: 10% to ECC, 10% to ZF Owners: Gordon Mohr (@gojomo on relevant forums) Status: Obsolete -Category: Consensus / Process +Category: Consensus Process Created: 2019-11-14 License: Public Domain Discussions-To: <https://forum.zcashcommunity.com/t/zip-keep-it-simple-zcashers-kisz-10-to-ecc-10-to-zfnd/35425> diff --git a/zip-1013.rst b/zip-1013.rst index 544066aa..17cbb9e0 100644 --- a/zip-1013.rst +++ b/zip-1013.rst @@ -4,7 +4,7 @@ Title: Keep It Simple, Zcashers: 10% to ECC, 10% to ZF Owners: Gordon Mohr (@gojomo on relevant forums) Status: Obsolete - Category: Consensus / Process + Category: Consensus Process Created: 2019-11-14 License: Public Domain Discussions-To: diff --git a/zip-1014.html b/zip-1014.html index f8edf9ed..5fe83aae 100644 --- a/zip-1014.html +++ b/zip-1014.html @@ -19,7 +19,7 @@ Credits: Matt Luongo Josh Cincinnati Andrew Miller Status: Active -Category: Consensus / Process +Category: Consensus Process Created: 2019-11-10 License: MIT Discussions-To: <https://forum.zcashcommunity.com/t/community-sentiment-polling-results-nu4-and-draft-zip-1014/35560> diff --git a/zip-1014.rst b/zip-1014.rst index efb126be..4511ac35 100644 --- a/zip-1014.rst +++ b/zip-1014.rst @@ -13,7 +13,7 @@ Josh Cincinnati Andrew Miller Status: Active - Category: Consensus / Process + Category: Consensus Process Created: 2019-11-10 License: MIT Discussions-To: