diff --git a/zip-0000.rst b/zip-0000.rst index 36f03a2d..cac7dc3b 100644 --- a/zip-0000.rst +++ b/zip-0000.rst @@ -276,7 +276,9 @@ Each ZIP SHOULD have the following parts: this section consider `RFC 3552 `__. 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 generally need not be completed before the ZIP is accepted into Proposed. @@ -345,7 +347,7 @@ There are several kinds of ZIP: 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 +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 @@ -381,7 +383,7 @@ ZIP Status Field ZIP. * 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. * 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 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 +the specified network upgrade. (All ``Network Upgrade`` schedules will be distributed via the Zcash Ecosystem Developer list by the Editors.) A Standards Track ZIP may only change status from Proposed to