diff --git a/zip-0214.html b/zip-0214.html
index a4f2c73b..3eec73f8 100644
--- a/zip-0214.html
+++ b/zip-0214.html
@@ -16,24 +16,28 @@ License: MIT
Discussions-To: <https://forum.zcashcommunity.com/t/community-sentiment-polling-results-nu4-and-draft-zip-1014/35560>
Terminology 
The key words "MUST", "MUST NOT", "SHALL", "SHALL NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119.
- The term "network upgrade" in this document is to be interpreted as described in ZIP 200 and the Zcash Trademark Donation and License Agreement ( or successor agreement).
- The terms "block subsidy" and "halving" in this document are to be interpreted as described in sections 3.9 and 7.7 of the Zcash Protocol Specification.
- The terms "Electric Coin Company" (or "ECC"), "Zcash Foundation" (or "ZF"), "Major Grants", "ECC slice", "ZF slice", and "MG slice" in this document are to be interpreted as described in ZIP 1014 .
+ The term "Zcash" in this document is to be interpreted as described in the Zcash Trademark Donation and License Agreement ( or successor agreement).
+ The term "network upgrade" in this document is to be interpreted as described in ZIP 200 and the Zcash Trademark Donation and License Agreement ( or successor agreement).
+ The terms "block subsidy" and "halving" in this document are to be interpreted as described in sections 3.9 and 7.7 of the Zcash Protocol Specification.
+ The terms "Electric Coin Company" (or "ECC"), "Zcash Foundation" (or "ZF"), "Major Grants", "ECC slice", "ZF slice", and "MG slice" in this document are to be interpreted as described in ZIP 1014 .
The terms below are to be interpreted as follows:
- ${NU4}
- Code-name for the fifth Zcash network upgrade, also known as Network Upgrade 4.
- Testnet
- - The Zcash test network, as defined in .
+ - The Zcash test network, as defined in .
- Mainnet
- - The Zcash production network, as defined in .
+ - The Zcash production network, as defined in .
Abstract
This ZIP describes consensus rule changes interpreting the proposed structure of the Zcash Development Fund, which is to be enacted in Network Upgrade 4 and last for 4 years.
+ Applicability
+ This ZIP concerns the Zcash Mainnet and Testnet, and is not intended to be applicable to other blockchains using Zcash technology.
+
Motivation
- Motivation for the Zcash Development Fund itself is considered in ZIP 1014 , which gives a high-level description of the intended structure of the fund.
+ Motivation for the Zcash Development Fund itself is considered in ZIP 1014 , which gives a high-level description of the intended structure of the fund.
An important motivation for describing the consensus rules in a separate ZIP is to avoid making unintended changes to ZIP 1014, which has already been agreed between ECC, ZF, and the Zcash community. This facilitates critically assessing whether the consensus rule changes accurately reflect the intent of ZIP 1014.
Requirements
@@ -44,9 +48,9 @@ Discussions-To: <https://forum.zcashcommunity.com/t/community-sentiment-polli
This ZIP is not required to enforce provisions of ZIP 1014 that fall outside what is implementable by Zcash consensus rules.
Specification
- The Blossom network upgrade changed the height of the first halving to block height 1046400 , as a consequence of reducing the block target spacing from 150 seconds to 75 seconds.
+ The Blossom network upgrade changed the height of the first halving to block height 1046400 , as a consequence of reducing the block target spacing from 150 seconds to 75 seconds.
Since ZIP 1014 specifies that the Zcash Development Fund starts at the first halving, the activation height of ${NU4} on Mainnet therefore SHALL be 1046400.
- ZIP 207 SHALL be activated in ${NU4}.
+ ZIP 207 SHALL be activated in ${NU4}.
The following funding streams are defined for Mainnet:
@@ -92,10 +96,10 @@ Discussions-To: <https://forum.zcashcommunity.com/t/community-sentiment-polli
ECC SHALL generate the addresses for the FS_ECC funding stream, which on Mainnet corresponds to the ECC slice;
ZF SHALL generate the addresses for the FS_ZF and FS_MG funding streams, which on Mainnet correspond to the ZF slice and MG slice respectively.
- Funds sent to each Mainnet funding stream SHALL be governed by all requirements on the corresponding slice specified in ZIP 1014 .
+ Funds sent to each Mainnet funding stream SHALL be governed by all requirements on the corresponding slice specified in ZIP 1014 .
No requirements are imposed on the use of funds sent to Testnet funding streams.
Direct-grant option
- ZIP 1014 specifies a "direct-grant option" by which, if agreed upon by both ECC and ZF before ${NU4} activation, some portion of the MG slice may be directly assigned to the grantee(s), rather than accepted and disbursed by ZF.
+ ZIP 1014 specifies a "direct-grant option" by which, if agreed upon by both ECC and ZF before ${NU4} activation, some portion of the MG slice may be directly assigned to the grantee(s), rather than accepted and disbursed by ZF.
The funding stream mechanism allows for this option by adding a funding stream corresponding to each direct grantee, with addresses generated by ZF. In this case the total amount of funding streams assigned to direct grantees MUST be subtracted from the funding stream for the remaining MG slice (or, if all Major Grants are direct, replace the funding stream for the MG slice).
For each network upgrade after ${NU4} requiring modifications to the set of direct grantees, a separate ZIP would be published specifying those modifications.
@@ -117,7 +121,7 @@ Discussions-To: <https://forum.zcashcommunity.com/t/community-sentiment-polli
Deployment
- This proposal is intended to be deployed with ${NU4}.
+ This proposal is intended to be deployed with ${NU4}.
References