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

Minor updates. 

Co-authored-by: str4d <thestr4d@gmail.com>
Co-authored-by: Josh Cincinnati <acityinohio@users.noreply.github.com>
This commit is contained in:
Daira Hopwood 2019-03-20 02:49:37 +00:00
parent ee74933826
commit 0105afc51f
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
zip-0000.rst
View File

@ -276,7 +276,9 @@ Each ZIP SHOULD have the following parts:
this section consider `RFC 3552 <https://tools.ietf.org/html/rfc3552>`__. this section consider `RFC 3552 <https://tools.ietf.org/html/rfc3552>`__.
as a starting point. as a starting point.
* Reference implementation -- The reference implementation must be * Reference implementation -- Literal code implementing the ZIP's
specification, and/or a link to the reference implementation of
the ZIP's specification. The reference implementation must be
completed before any ZIP is given status “Implemented”, but it completed before any ZIP is given status “Implemented”, but it
generally need not be completed before the ZIP is accepted into generally need not be completed before the ZIP is accepted into
Proposed. Proposed.
@ -345,7 +347,7 @@ There are several kinds of ZIP:
protocol, or any change or addition that affects the interoperability protocol, or any change or addition that affects the interoperability
of applications using Zcash. of applications using Zcash.
Consensus and Standards Track ZIPs consist of two parts, a design document Consensus and Standards Track ZIPs consist of two parts: a design document
and a reference implementation. and a reference implementation.
* An Informational ZIP describes Zcash design issues, or general * An Informational ZIP describes Zcash design issues, or general
@ -381,7 +383,7 @@ ZIP Status Field
ZIP. ZIP.
* Proposed: Typically the stage after Draft, added to a ZIP after * Proposed: Typically the stage after Draft, added to a ZIP after
consideration and feedback from the community. The ZIP Editors must consideration, feedback, and rough consensus from the community. The ZIP Editors must
validate this change before it is approved. validate this change before it is approved.
* Rejected: The status when progress hasn't been made on the ZIP in one * Rejected: The status when progress hasn't been made on the ZIP in one
@ -412,7 +414,7 @@ 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 among the Editors. If it's a Standards Track ZIP, upon changing status to
Proposed the Editors will add the optional ``Network Upgrade`` header Proposed the Editors will add the optional ``Network Upgrade`` header
to the preamble, indicating the intent for the ZIP to be implemented in to the preamble, indicating the intent for the ZIP to be implemented in
the specified network upgrade. (All \*Network Upgrade\* schedules will be the specified network upgrade. (All ``Network Upgrade`` schedules will be
distributed via the Zcash Ecosystem Developer list by the Editors.) distributed via the Zcash Ecosystem Developer list by the Editors.)
A Standards Track ZIP may only change status from Proposed to A Standards Track ZIP may only change status from Proposed to