zecfoundation
/
zips
mirror of https://github.com/ZcashFoundation/zips.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Regularize ZIP categories. 

Signed-off-by: Daira Hopwood <daira@jacaranda.org>
This commit is contained in:
Daira Hopwood 2020-11-14 22:06:46 +00:00
parent a3189affb2
commit 947f0b6649
68 changed files with 160 additions and 137 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

50
zip-0000.html
View File

@ -34,7 +34,7 @@ License: BSD-2-Clause</pre>
<p>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 <a href="https://forum.zcashcommunity.com/">Zcash Community Forum</a>. 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 <a href="https://github.com/zcash/zips">ZIPs git repository</a> as a pull request. This draft must be written in ZIP style as described below, and named with an alias such as <code>zip-zatoshizakamoto-42millionzec</code> until the ZIP Editors have assigned it a ZIP number (Owners MUST NOT self-assign ZIP numbers).</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<section id="zip-numbering-conventions"><h3><span class="section-heading">ZIP Numbering Conventions</span><span class="section-anchor"> <a rel="bookmark" href="#zip-numbering-conventions"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h3>
<p>The ZIP Editors currently use the following conventions when numbering ZIPs:</p>
@ -130,7 +130,6 @@ License:</pre>
Original-Authors:
Discussions-To:
Pull-Request:
Network Upgrade:
Obsoleted by:
Updated by:
Obsoletes:
@ -140,7 +139,7 @@ Updates:</pre>
<p>If there are multiple Owners, each should be on a separate line.</p>
<p>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.</p>
<p>The Pull-Request header, if present, gives an URL to a Pull Request for the ZIP.</p>
<p>The Category header specifies the type of ZIP: Consensus, Standards Track, Informational, or Process.</p>
<p>The Category header specifies the type of ZIP, as described in <a href="#zip-categories">ZIP categories</a>. Multiple categories MAY be specified, separated by " <code>/</code> ".</p>
<p>The Created header records the date that the ZIP was submitted. Dates should be in yyyy-mm-dd format, e.g. 2001-08-14.</p>
<p>For ZIPs written in reStructuredText, URLs in header fields SHOULD be surrounded by <code>&lt;</code> <code>&gt;</code>; this ensures that the link is rendered correctly.</p>
</section>
@ -149,17 +148,30 @@ Updates:</pre>
</section>
</section>
<section id="zip-categories"><h2><span class="section-heading">ZIP categories</span><span class="section-anchor"> <a rel="bookmark" href="#zip-categories"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
<p>There are several kinds of ZIP:</p>
<ul>
<li>A Consensus ZIP describes a change that affects the consensus protocol followed by all Zcash implementations.</li>
<li>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.</li>
</ul>
<p>Consensus and Standards Track ZIPs consist of two parts: a design document and a reference implementation.</p>
<ul>
<li>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.</li>
<li>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.</li>
</ul>
<p>Each ZIP is in one or more of the following categories, as specified in the Category header:</p>
<dl>
<dt>Consensus</dt>
<dd>Rules that affect the consensus protocol followed by all Zcash implementations.</dd>
<dt>Standards</dt>
<dd>Non-consensus changes affecting most or all Zcash implementations, or the interoperability of applications using Zcash.</dd>
<dt>Process</dt>
<dd>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.</dd>
<dt>Consensus Process</dt>
<dd>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.</dd>
<dt>Informational</dt>
<dd>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.</dd>
<dt>Network</dt>
<dd>Specifications of peer-to-peer networking behaviour.</dd>
<dt>RPC</dt>
<dd>Specifications of the RPC interface provided by zcashd nodes.</dd>
<dt>Wallet</dt>
<dd>Specifications affecting wallets (e.g. non-consensus changes to how transactions, addresses, etc. are constructed or interpreted).</dd>
<dt>Ecosystem</dt>
<dd>Specifications otherwise useful to the Zcash ecosystem.</dd>
</dl>
<p>New categories may be added by consensus among the ZIP Editors.</p>
<p>Consensus and Standards ZIPs SHOULD have a Reference Implementation section, which includes or (more often) links to an implementation.</p>
<p>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).</p>
</section>
<section id="zip-status-field"><h2><span class="section-heading">ZIP Status Field</span><span class="section-anchor"> <a rel="bookmark" href="#zip-status-field"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>
<ul>
@ -169,17 +181,17 @@ Updates:</pre>
<li>Active: Typically only used for Process/Informational ZIPs, achieved once rough consensus is reached in PR/forum posts from Draft Process ZIP.</li>
<li>Proposed: Typically the stage after Draft, added to a ZIP after consideration, feedback, and rough consensus from the community. The ZIP Editors must validate this change before it is approved.</li>
<li>Rejected: The status when progress hasn't been made on the ZIP in one year. Can revert back to Draft/Proposed if the Owner resumes work or resolves issues preventing consensus.</li>
<li>Implemented: When a Consensus or Standards Track ZIP has a working reference implementation but before activation on the Zcash network.</li>
<li>Final: When a Consensus or Standards Track ZIP is both implemented and activated on the Zcash network.</li>
<li>Implemented: When a Consensus or Standards ZIP has a working reference implementation but before activation on the Zcash network.</li>
<li>Final: When a Consensus or Standards ZIP is both implemented and activated on the Zcash network.</li>
<li>Obsolete: The status when a ZIP is no longer relevant (typically when superseded by another ZIP).</li>
</ul>
<p>More details on the status workflow are given in the section below.</p>
<section id="specification"><h3><span class="section-heading">Specification</span><span class="section-anchor"> <a rel="bookmark" href="#specification"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h3>
<p>Owners of a ZIP may decide on their own to change the status between Draft or Withdrawn.</p>
<p>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 <code>Network Upgrade</code> header to the preamble, indicating the intent for the ZIP to be implemented in the specified network upgrade. (All <code>Network Upgrade</code> schedules will be distributed via the Zcash Community Forum by the Editors.)</p>
<p>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 <code>Network Upgrade</code> header to target another upgrade, at their discretion.</p>
<p>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.</p>
<p>A Consensus or Standards Track ZIP becomes Final when its associated network upgrade or other protocol change is activated on Zcash's mainnet.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>A Consensus or Standards ZIP becomes Final when its associated network upgrade or other protocol change is activated on Zcash's mainnet.</p>
<p>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.</p>
<p>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).</p>
</section>

115
zip-0000.rst
View File

@ -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 <https://github.com/zcash/zcash/blob/master/code_of_conduct.md>`_
.. [#rst] `reStructuredText documentation <http://docutils.sourceforge.net/rst.html>`_
.. [#latex] `LaTeX — a document preparation system <https://www.latex-project.org/>`_

2
zip-0001.html
View File

@ -9,7 +9,7 @@
<pre>ZIP: 1
Title: Network Upgrade Policy and Scheduling
Status: Reserved
Category: Process
Category: Consensus Process
Discussions-To: &lt;<a href="https://github.com/zcash/zips/issues/343">https://github.com/zcash/zips/issues/343</a>&gt;</pre>
</section>
</body>

2
zip-0001.rst
View File

@ -3,5 +3,5 @@
ZIP: 1
Title: Network Upgrade Policy and Scheduling
Status: Reserved
Category: Process
Category: Consensus Process
Discussions-To: <https://github.com/zcash/zips/issues/343>

2
zip-0022.html
View File

@ -9,7 +9,7 @@
<pre>ZIP: 22
Title: Specification of getblocktemplate for Zcash
Status: Reserved
Category: Informational
Category: RPC
Discussions-To: &lt;<a href="https://github.com/zcash/zips/issues/349">https://github.com/zcash/zips/issues/349</a>&gt;</pre>
</section>
</body>

2
zip-0022.rst
View File

@ -3,5 +3,5 @@
ZIP: 22
Title: Specification of getblocktemplate for Zcash
Status: Reserved
Category: Informational
Category: RPC
Discussions-To: <https://github.com/zcash/zips/issues/349>

2
zip-0032.html
View File

@ -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</pre>
<p>

2
zip-0032.rst
View File

@ -8,7 +8,7 @@
Marek Palatinus
Pavol Rusnak
Status: Final
Category: Standards Track
Category: Standards / Wallet
Created: 2018-05-22
License: MIT

2
zip-0173.html
View File

@ -14,7 +14,7 @@ Credits: Pieter Wuille &lt;pieter.wuille@gmail.com&gt;
Rusty Russell
Mark Friedenbach
Status: Final
Category: Wallet
Category: Standards / Wallet
Created: 2018-06-13
License: MIT</pre>
<section id="terminology"><h2><span class="section-heading">Terminology</span><span class="section-anchor"> <a rel="bookmark" href="#terminology"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>

2
zip-0173.rst
View File

@ -8,7 +8,7 @@
Rusty Russell
Mark Friedenbach
Status: Final
Category: Wallet
Category: Standards / Wallet
Created: 2018-06-13
License: MIT

2
zip-0205.html
View File

@ -11,7 +11,7 @@ Title: Deployment of the Sapling Network Upgrade
Owners: Daira Hopwood &lt;daira@electriccoin.co&gt;
Credits: Simon Liu
Status: Final
Category: Consensus
Category: Consensus / Network
Created: 2018-10-08
License: MIT</pre>
<section id="terminology"><h2><span class="section-heading">Terminology</span><span class="section-anchor"> <a rel="bookmark" href="#terminology"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>

2
zip-0205.rst
View File

@ -5,7 +5,7 @@
Owners: Daira Hopwood <daira@electriccoin.co>
Credits: Simon Liu
Status: Final
Category: Consensus
Category: Consensus / Network
Created: 2018-10-08
License: MIT

2
zip-0206.html
View File

@ -11,7 +11,7 @@ Title: Deployment of the Blossom Network Upgrade
Owners: Daira Hopwood &lt;daira@electriccoin.co&gt;
Credits: Simon Liu
Status: Final
Category: Consensus
Category: Consensus / Network
Created: 2019-07-29
License: MIT</pre>
<section id="terminology"><h2><span class="section-heading">Terminology</span><span class="section-anchor"> <a rel="bookmark" href="#terminology"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>

2
zip-0206.rst
View File

@ -5,7 +5,7 @@
Owners: Daira Hopwood <daira@electriccoin.co>
Credits: Simon Liu
Status: Final
Category: Consensus
Category: Consensus / Network
Created: 2019-07-29
License: MIT

2
zip-0250.html
View File

@ -10,7 +10,7 @@
Title: Deployment of the Heartwood Network Upgrade
Owners: Daira Hopwood &lt;daira@electriccoin.co&gt;
Status: Final
Category: Consensus
Category: Consensus / Network
Created: 2020-02-28
License: MIT</pre>
<section id="terminology"><h2><span class="section-heading">Terminology</span><span class="section-anchor"> <a rel="bookmark" href="#terminology"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>

2
zip-0250.rst
View File

@ -4,7 +4,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

2
zip-0251.html
View File

@ -10,7 +10,7 @@
Title: Deployment of the Canopy Network Upgrade
Owners: Daira Hopwood &lt;daira@electriccoin.co&gt;
Status: Implemented (zcashd)
Category: Consensus
Category: Consensus / Network
Created: 2020-02-28
License: MIT</pre>
<section id="terminology"><h2><span class="section-heading">Terminology</span><span class="section-anchor"> <a rel="bookmark" href="#terminology"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>

2
zip-0251.rst
View File

@ -4,7 +4,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

2
zip-0252.html
View File

@ -10,7 +10,7 @@
Title: Deployment of the NU5 Network Upgrade
Owners: Daira Hopwood &lt;daira@electriccoin.co&gt;
Status: Reserved
Category: Consensus
Category: Consensus / Network
Discussions-To: &lt;<a href="https://github.com/zcash/zips/issues/397">https://github.com/zcash/zips/issues/397</a>&gt;</pre>
</section>
</body>

2
zip-0252.rst
View File

@ -4,5 +4,5 @@
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>

2
zip-0301.html
View File

@ -15,7 +15,7 @@ Credits: 5a1t
Jelle Bourdeaud'hui (razakal)
ocminer
Status: Final
Category: Ecosystem
Category: Standards / Ecosystem
Created: 2016-09-23
License: MIT</pre>
<section id="terminology"><h2><span class="section-heading">Terminology</span><span class="section-anchor"> <a rel="bookmark" href="#terminology"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>

2
zip-0301.rst
View File

@ -9,7 +9,7 @@
Jelle Bourdeaud'hui (razakal)
ocminer
Status: Final
Category: Ecosystem
Category: Standards / Ecosystem
Created: 2016-09-23
License: MIT

2
zip-0302.html
View File

@ -11,7 +11,7 @@ Title: Standardized Memo Field Format
Owners: Jack Grigg &lt;jack@electriccoin.co&gt;
Original-Authors: Jay Graber
Status: Reserved
Category: Standards
Category: Standards / RPC / Wallet
Discussions-To: &lt;<a href="https://github.com/zcash/zips/issues/366">https://github.com/zcash/zips/issues/366</a>&gt;
Pull-Request: &lt;<a href="https://github.com/zcash/zips/pull/105">https://github.com/zcash/zips/pull/105</a>&gt;</pre>
</section>

2
zip-0302.rst
View File

@ -5,6 +5,6 @@
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>

2
zip-0303.html
View File

@ -11,7 +11,7 @@ Title: Sprout Payment Disclosure
Owners: Deirdre Connolly &lt;deirdre@zfnd.org&gt;
Original-Authors: Simon Liu
Status: Reserved
Category: Informational
Category: Standards / RPC / Wallet
Pull-Request: &lt;<a href="https://github.com/zcash/zips/pull/119">https://github.com/zcash/zips/pull/119</a>&gt;</pre>
</section>
</body>

2
zip-0303.rst
View File

@ -5,5 +5,5 @@
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>

2
zip-0304.html
View File

@ -13,7 +13,7 @@ Owners: Jack Grigg &lt;jack@electriccoin.co&gt;
Credits: Daira Hopwood &lt;daira@electriccoin.co&gt;
Sean Bowe &lt;sean@electriccoin.co&gt;
Status: Draft
Category: Wallet
Category: Standards / RPC / Wallet
Created: 2020-06-01
License: MIT
Discussions-To: &lt;<a href="https://github.com/zcash/zips/issues/345">https://github.com/zcash/zips/issues/345</a>&gt;

2
zip-0304.rst
View File

@ -6,7 +6,7 @@
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>

2
zip-0307.html
View File

@ -13,7 +13,7 @@ Owners: Jack Grigg &lt;jack@electriccoin.co&gt;
Daira Hopwood &lt;daira@electriccoin.co&gt;
Original-Authors: George Tankersley
Credits: Matthew Green
Category: Standards Track
Category: Standards / Ecosystem
Status: Draft
Created: 2018-09-17
License: MIT</pre>

2
zip-0307.rst
View File

@ -6,7 +6,7 @@
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

2
zip-0308.html
View File

@ -12,7 +12,7 @@ Owner: Daira Hopwood &lt;daira@electriccoin.co&gt;
Original-Authors: Daira Hopwood
Eirik Ogilvie-Wigley
Status: Final
Category: RPC/Wallet
Category: Standards / RPC / Wallet
Created: 2018-11-27
License: MIT</pre>
<section id="terminology"><h2><span class="section-heading">Terminology</span><span class="section-anchor"> <a rel="bookmark" href="#terminology"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2>

2
zip-0308.rst
View File

@ -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

2
zip-0309.html
View File

@ -13,7 +13,7 @@ Owners: J. Ayo Akinyele &lt;ayo@boltlabs.io&gt;
Credits: Ian Miers
Matthew Green
Status: Reserved
Category: Consensus
Category: Standards / Ecosystem
Created: 2019-07-15
Discussions-To: &lt;<a href="https://github.com/zcash/zips/issues/2353">https://github.com/zcash/zips/issues/2353</a>&gt;
Pull-Request: &lt;<a href="https://github.com/zcash/zips/pull/216">https://github.com/zcash/zips/pull/216</a>&gt;</pre>

2
zip-0309.rst
View File

@ -7,7 +7,7 @@
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>

2
zip-0311.html
View File

@ -10,7 +10,7 @@
Title: Sapling Payment Disclosure
Owners: Deirdre Connolly &lt;deirdre@zfnd.org&gt;
Status: Reserved
Category: Informational
Category: Standards / RPC / Wallet
Discussions-To: &lt;<a href="https://github.com/zcash/zips/issues/387">https://github.com/zcash/zips/issues/387</a>&gt;</pre>
</section>
</body>

2
zip-0311.rst
View File

@ -4,5 +4,5 @@
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>

2
zip-0312.html
View File

@ -9,7 +9,7 @@
<pre>ZIP: 312
Title: Shielded Multisignatures using FROST
Status: Reserved
Category: Standards
Category: Standards / RPC / Wallet
Discussions-To: &lt;<a href="https://github.com/zcash/zips/issues/382">https://github.com/zcash/zips/issues/382</a>&gt;</pre>
</section>
</body>

2
zip-0312.rst
View File

@ -3,5 +3,5 @@
ZIP: 312
Title: Shielded Multisignatures using FROST
Status: Reserved
Category: Standards
Category: Standards / RPC / Wallet
Discussions-To: <https://github.com/zcash/zips/issues/382>

2
zip-0321.html
View File

@ -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: &lt;<a href="https://github.com/zcash/zips/issues/347">https://github.com/zcash/zips/issues/347</a>&gt;
Pull-Request: &lt;<a href="https://github.com/zcash/zips/pull/395">https://github.com/zcash/zips/pull/395</a>&gt;

2
zip-0321.rst
View File

@ -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: <https://github.com/zcash/zips/issues/347>
Pull-Request: <https://github.com/zcash/zips/pull/395>

2
zip-1001.html
View File

@ -10,7 +10,7 @@
Title: Keep the Block Distribution as Initially Defined — 90% to Miners
Owner: mistfpga (zcash forums) &lt;steve@mistfpga.net&gt;
Status: Obsolete
Category: Consensus
Category: Consensus Process
Created: 2019-08-01
License: CC BY-SA 4.0 &lt;<a href="https://creativecommons.org/licenses/by-sa/4.0/">https://creativecommons.org/licenses/by-sa/4.0/</a>&gt;
Discussions-To: &lt;<a href="https://forum.zcashcommunity.com/t/zip-proposal-keep-the-block-distribution-as-initaly-defined-90-to-miners/33843">https://forum.zcashcommunity.com/t/zip-proposal-keep-the-block-distribution-as-initaly-defined-90-to-miners/33843</a>&gt;</pre>

2
zip-1001.rst
View File

@ -4,7 +4,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>

2
zip-1002.html
View File

@ -10,7 +10,7 @@
Title: Opt-in Donation Feature
Owner: mistfpga (zcash forums) &lt;steve@mistfpga.net&gt;
Status: Obsolete
Category: Standards Track
Category: Consensus Process
Created: 2019-07-17
License: CC BY-SA 4.0 &lt;<a href="https://creativecommons.org/licenses/by-sa/4.0/">https://creativecommons.org/licenses/by-sa/4.0/</a>&gt;
Discussions-To: &lt;<a href="https://forum.zcashcommunity.com/t/zip-proposal-a-genuine-opt-in-protocol-level-development-donation-option/33846">https://forum.zcashcommunity.com/t/zip-proposal-a-genuine-opt-in-protocol-level-development-donation-option/33846</a>&gt;</pre>

2
zip-1002.rst
View File

@ -4,7 +4,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>

2
zip-1003.html
View File

@ -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: &lt;<a href="https://forum.zcashcommunity.com/t/dev-fund-proposal-20-split-between-the-ecc-and-the-foundation/33862">https://forum.zcashcommunity.com/t/dev-fund-proposal-20-split-between-the-ecc-and-the-foundation/33862</a>&gt;</pre>

2
zip-1003.rst
View File

@ -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: <https://forum.zcashcommunity.com/t/dev-fund-proposal-20-split-between-the-ecc-and-the-foundation/33862>

2
zip-1004.html
View File

@ -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: &lt;<a href="https://forum.zcashcommunity.com/t/dev-fund-proposal-miner-directed-dev-fund-was-20-to-any-combination-of-ecc-zfnd-parity-or-burn/33864">https://forum.zcashcommunity.com/t/dev-fund-proposal-miner-directed-dev-fund-was-20-to-any-combination-of-ecc-zfnd-parity-or-burn/33864</a>&gt;</pre>

2
zip-1004.rst
View File

@ -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: <https://forum.zcashcommunity.com/t/dev-fund-proposal-miner-directed-dev-fund-was-20-to-any-combination-of-ecc-zfnd-parity-or-burn/33864>

2
zip-1005.html
View File

@ -10,7 +10,7 @@
Title: Zcash Community Funding System
Owner: Dimitris Apostolou &lt;dimitris.apostolou@icloud.com&gt;
Status: Obsolete
Category: Consensus
Category: Consensus Process
Created: 2019-06-23
License: MIT
Discussions-To: &lt;<a href="https://forum.zcashcommunity.com/t/zip-proposal-zcfs-zcash-community-funding-system/33898">https://forum.zcashcommunity.com/t/zip-proposal-zcfs-zcash-community-funding-system/33898</a>&gt;</pre>

2
zip-1005.rst
View File

@ -4,7 +4,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>

2
zip-1006.html
View File

@ -13,7 +13,7 @@ Owners: James Todaro &lt;james@blocktown.capital&gt;
Credits: Mario Laul
Chris Burniske
Status: Obsolete
Category: Consensus / Process
Category: Consensus Process
Created: 2019-08-31
License: MIT
Discussions-To: &lt;<a href="https://forum.zcashcommunity.com/t/blocktown-development-fund-proposal-10-to-a-2-of-3-multisig-with-community-involved-third-entity/34782">https://forum.zcashcommunity.com/t/blocktown-development-fund-proposal-10-to-a-2-of-3-multisig-with-community-involved-third-entity/34782</a>&gt;</pre>

2
zip-1006.rst
View File

@ -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: <https://forum.zcashcommunity.com/t/blocktown-development-fund-proposal-10-to-a-2-of-3-multisig-with-community-involved-third-entity/34782>

2
zip-1007.html
View File

@ -11,7 +11,7 @@ Title: Enforce Development Fund Commitments with a Legal Charter
Owners: @lex-node (zcash forums)
@mistfpga (zcash forums) &lt;steve@mistfpga.net&gt;
Status: Obsolete
Category: Process
Category: Concensus Process
Created: 2019-08-24
License: CC BY-SA 4.0 &lt;<a href="https://creativecommons.org/licenses/by-sa/4.0/">https://creativecommons.org/licenses/by-sa/4.0/</a>&gt;
Discussions-To: &lt;<a href="https://forum.zcashcommunity.com/t/dev-fund-supplemental-proposal-enforce-devfund-commitments-with-legal-charter/34709">https://forum.zcashcommunity.com/t/dev-fund-supplemental-proposal-enforce-devfund-commitments-with-legal-charter/34709</a>&gt;</pre>

2
zip-1007.rst
View File

@ -5,7 +5,7 @@
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>

2
zip-1008.html
View File

@ -11,7 +11,7 @@ Title: Fund ECC for Two More Years
Owners: @kek (zcash forums)
@mistfpga (zcash forums) &lt;steve@mistfpga.net&gt;
Status: Obsolete
Category: Consensus
Category: Consensus Process
Created: 2019-09-02
License: CC BY-SA 4.0 &lt;<a href="https://creativecommons.org/licenses/by-sa/4.0/">https://creativecommons.org/licenses/by-sa/4.0/</a>&gt;
Discussions-To: &lt;<a href="https://forum.zcashcommunity.com/t/kek-s-proposal-fund-ecc-for-2-more-years/34778">https://forum.zcashcommunity.com/t/kek-s-proposal-fund-ecc-for-2-more-years/34778</a>&gt;</pre>

2
zip-1008.rst
View File

@ -5,7 +5,7 @@
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>

2
zip-1009.html
View File

@ -10,7 +10,7 @@
Title: Five-Entity Strategic Council
Owner: Avichal Garg &lt;avichalgarg@electriccapital.com&gt;
Status: Obsolete
Category: Process
Category: Consensus Process
Created: 2019-08-28
License: MIT
Discussions-To: &lt;<a href="https://forum.zcashcommunity.com/t/dev-fund-proposal-5-entity-strategic-council-approach/34801">https://forum.zcashcommunity.com/t/dev-fund-proposal-5-entity-strategic-council-approach/34801</a>&gt;</pre>

2
zip-1009.rst
View File

@ -4,7 +4,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>

2
zip-1010.html
View File

@ -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: &lt;<a href="https://forum.zcashcommunity.com/t/a-grand-compromise-synthesis-zip-proposal/34812/">https://forum.zcashcommunity.com/t/a-grand-compromise-synthesis-zip-proposal/34812/</a>&gt;</pre>

2
zip-1010.rst
View File

@ -10,7 +10,7 @@
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/>

2
zip-1011.html
View File

@ -11,7 +11,7 @@
Title: Decentralize the Dev Fee
Owner: Matt Luongo &lt;matt@thesis.co&gt;
Status: Obsolete
Category: Process
Category: Consensus Process
Created: 2019-09-27
License: MIT
Discussions-To: &lt;<a href="https://forum.zcashcommunity.com/t/decentralizing-the-dev-fee/35252">https://forum.zcashcommunity.com/t/decentralizing-the-dev-fee/35252</a>&gt;

2
zip-1011.rst
View File

@ -4,7 +4,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>

2
zip-1012.html
View File

@ -10,7 +10,7 @@
Title: Dev Fund to ECC + ZF + Major Grants
Owner: Eran Tromer &lt;eran@tromer.org&gt;
Status: Obsolete
Category: Consensus / Process
Category: Consensus Process
Created: 2019-11-10
License: MIT
Discussions-To: &lt;<a href="https://forum.zcashcommunity.com/t/dev-fund-proposal-dev-fund-to-ecc-zfnd-major-grants/35364">https://forum.zcashcommunity.com/t/dev-fund-proposal-dev-fund-to-ecc-zfnd-major-grants/35364</a>&gt;

2
zip-1012.rst
View File

@ -4,7 +4,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>

2
zip-1013.html
View File

@ -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: &lt;<a href="https://forum.zcashcommunity.com/t/zip-keep-it-simple-zcashers-kisz-10-to-ecc-10-to-zfnd/35425">https://forum.zcashcommunity.com/t/zip-keep-it-simple-zcashers-kisz-10-to-ecc-10-to-zfnd/35425</a>&gt;

2
zip-1013.rst
View File

@ -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: <https://forum.zcashcommunity.com/t/zip-keep-it-simple-zcashers-kisz-10-to-ecc-10-to-zfnd/35425>

2
zip-1014.html
View File

@ -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: &lt;<a href="https://forum.zcashcommunity.com/t/community-sentiment-polling-results-nu4-and-draft-zip-1014/35560">https://forum.zcashcommunity.com/t/community-sentiment-polling-results-nu4-and-draft-zip-1014/35560</a>&gt;

2
zip-1014.rst
View File

@ -13,7 +13,7 @@
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>