-
Notifications
You must be signed in to change notification settings - Fork 156
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Daira Hopwood <[email protected]>
- Loading branch information
Showing
6 changed files
with
798 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,198 @@ | ||
| <!DOCTYPE html> | ||
| <html> | ||
| <head> | ||
| <title>ZIP 214: Consensus rules for a Zcash Development Fund</title> | ||
| <meta charset="utf-8" /> | ||
| <meta name="viewport" content="width=device-width, initial-scale=1"><link rel="stylesheet" href="css/style.css"></head> | ||
| <body> | ||
| <section> | ||
| <pre>ZIP: 214 | ||
| Title: Consensus rules for a Zcash Development Fund | ||
| Owners: Daira Hopwood <[email protected]> | ||
| Status: Draft | ||
| Category: Consensus | ||
| Created: 2020-02-28 | ||
| License: MIT | ||
| Discussions-To: <https://forum.zcashcommunity.com/t/community-sentiment-polling-results-nu4-and-draft-zip-1014/35560></pre> | ||
| <section id="terminology"><h2><span class="section-heading">Terminology</span><span class="section-anchor"> <a href="#terminology"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2> | ||
| <p>The key words "MUST", "MUST NOT", "SHALL", "SHALL NOT", "SHOULD", and "MAY" in this document are to be interpreted as described in RFC 2119. <a id="id1" class="footnote_reference" href="#rfc2119">1</a></p> | ||
| <p>The term "network upgrade" in this document is to be interpreted as described in ZIP 200 <a id="id2" class="footnote_reference" href="#zip-0200">5</a> and the Zcash Trademark Donation and License Agreement (<a id="id3" class="footnote_reference" href="#trademark">3</a> or successor agreement).</p> | ||
| <p>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. <a id="id4" class="footnote_reference" href="#protocol">2</a></p> | ||
| <p>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 <a id="id5" class="footnote_reference" href="#zip-1014">9</a>.</p> | ||
| <p>The terms below are to be interpreted as follows:</p> | ||
| <dl> | ||
| <dt>${NU4}</dt> | ||
| <dd>Code-name for the fifth Zcash network upgrade, also known as Network Upgrade 4.</dd> | ||
| <dt>Testnet</dt> | ||
| <dd>The Zcash test network, as defined in <a id="id6" class="footnote_reference" href="#protocol">2</a>.</dd> | ||
| <dt>Mainnet</dt> | ||
| <dd>The Zcash production network, as defined in <a id="id7" class="footnote_reference" href="#protocol">2</a>.</dd> | ||
| </dl> | ||
| </section> | ||
| <section id="abstract"><h2><span class="section-heading">Abstract</span><span class="section-anchor"> <a href="#abstract"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2> | ||
| <p>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.</p> | ||
| </section> | ||
| <section id="motivation"><h2><span class="section-heading">Motivation</span><span class="section-anchor"> <a href="#motivation"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2> | ||
| <p>Motivation for the Zcash Development Fund itself is considered in ZIP 1014 <a id="id8" class="footnote_reference" href="#zip-1014">9</a>, which gives a high-level description of the intended structure of the fund.</p> | ||
| <p>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.</p> | ||
| </section> | ||
| <section id="requirements"><h2><span class="section-heading">Requirements</span><span class="section-anchor"> <a href="#requirements"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2> | ||
| <p>The primary requirement of this ZIP is to make changes to consensus rules necessary and sufficient to implement the intent of ZIP 1014.</p> | ||
| <p>The Zcash Development Fund distributes funding in ZEC obtained from block subsidies on Mainnet. This ZIP should also specify corresponding rules, addresses, and activation height for Testnet, in order to allow testing and auditing of the design and implementation within sufficient lead time before activation on Mainnet.</p> | ||
| </section> | ||
| <section id="non-requirements"><h2><span class="section-heading">Non-requirements</span><span class="section-anchor"> <a href="#non-requirements"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2> | ||
| <p>This ZIP is not required to enforce provisions of ZIP 1014 that fall outside what is implementable by Zcash consensus rules.</p> | ||
| </section> | ||
| <section id="specification"><h2><span class="section-heading">Specification</span><span class="section-anchor"> <a href="#specification"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2> | ||
| <p>The Blossom network upgrade changed the height of the first halving to block height 1046400 <a id="id9" class="footnote_reference" href="#zip-0208">7</a>, as a consequence of reducing the block target spacing from 150 seconds to 75 seconds.</p> | ||
| <p>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.</p> | ||
| <p>ZIP 207 <a id="id10" class="footnote_reference" href="#zip-0207">6</a> SHALL be activated in ${NU4}.</p> | ||
| <p>The following funding streams are defined for Mainnet:</p> | ||
| <blockquote> | ||
| <table> | ||
| <thead> | ||
| <tr> | ||
| <th>Stream</th> | ||
| <th>Numerator</th> | ||
| <th>Denominator</th> | ||
| <th>Start height</th> | ||
| <th>End height</th> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td><code>FS_ECC</code></td> | ||
| <td>7</td> | ||
| <td>100</td> | ||
| <td>1046400</td> | ||
| <td>2726400</td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>FS_ZF</code></td> | ||
| <td>5</td> | ||
| <td>100</td> | ||
| <td>1046400</td> | ||
| <td>2726400</td> | ||
| </tr> | ||
| <tr> | ||
| <td><code>FS_MG</code></td> | ||
| <td>8</td> | ||
| <td>100</td> | ||
| <td>1046400</td> | ||
| <td>2726400</td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| </blockquote> | ||
| <p>The funding streams are defined for Testnet are identical except that the start height of each stream is the activation height of ${NU4} on Testnet, i.e. xxxxxxx.</p> | ||
| <p>Note: on Testnet, the activation height of ${NU4} will be before the first halving. Therefore, the consequence of the above rules for Testnet is that the amount sent to each Zcash Development Fund recipient address will initially (before Testnet block height 1046400) be double the corresponding initial amount on Mainnet. This reduces to the same amount as on Mainnet, from Testnet block heights 1046400 (inclusive) to 2726400 (exclusive).</p> | ||
| <section id="dev-fund-recipient-addresses"><h3><span class="section-heading">Dev Fund Recipient Addresses</span><span class="section-anchor"> <a href="#dev-fund-recipient-addresses"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h3> | ||
| <p>For each of Testnet and Mainnet, before deploying this ZIP in a node implementation with the activation height set for that network, each of the parties (ECC and ZF) SHALL generate sequences of independent recipient addresses to be used for each stream in each funding period:</p> | ||
| <ul> | ||
| <li>ECC SHALL generate the addresses for the <code>FS_ECC</code> funding stream, which on Mainnet corresponds to the <strong>ECC slice</strong>;</li> | ||
| <li>ZF SHALL generate the addresses for the <code>FS_ZF</code> and <code>FS_MG</code> funding streams, which on Mainnet correspond to the <strong>ZF slice</strong> and <strong>MG slice</strong> respectively.</li> | ||
| </ul> | ||
| <p>Funds sent to each Mainnet funding stream SHALL be governed by all requirements on the corresponding slice specified in ZIP 1014 <a id="id11" class="footnote_reference" href="#zip-1014">9</a>.</p> | ||
| <p>No requirements are imposed on the use of funds sent to Testnet funding streams.</p> | ||
| <section id="direct-grant-option"><h4><span class="section-heading">Direct-grant option</span><span class="section-anchor"> <a href="#direct-grant-option"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h4> | ||
| <p>ZIP 1014 specifies a "direct-grant option" by which, if agreed upon by both ECC and ZF before ${NU4} activation, some portion of the <strong>MG slice</strong> may be directly assigned to the grantee(s), rather than accepted and disbursed by ZF. <a id="id12" class="footnote_reference" href="#zip-1014">9</a></p> | ||
| <p>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 <strong>MG slice</strong> (or, if all Major Grants are direct, replace the funding stream for the <strong>MG slice</strong>).</p> | ||
| <p>For each network upgrade after ${NU4} requiring modifications to the set of direct grantees, a separate ZIP would be published specifying those modifications.</p> | ||
| </section> | ||
| </section> | ||
| <section id="mainnet-recipient-addresses"><h3><span class="section-heading">Mainnet Recipient Addresses</span><span class="section-anchor"> <a href="#mainnet-recipient-addresses"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h3> | ||
| <blockquote> | ||
| <dl> | ||
| <dt>FS_ECC_Addresses[0..47] = [</dt> | ||
| <dd>"TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO" ]</dd> | ||
| <dt>FS_ZF_Addresses[0..47] = [</dt> | ||
| <dd>"TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO" ]</dd> | ||
| <dt>FS_MG_Addresses[0..47] = [</dt> | ||
| <dd>"TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO", "TODO" ]</dd> | ||
| </dl> | ||
| </blockquote> | ||
| </section> | ||
| <section id="testnet-recipient-addresses"><h3><span class="section-heading">Testnet Recipient Addresses</span><span class="section-anchor"> <a href="#testnet-recipient-addresses"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h3> | ||
| <p>TODO</p> | ||
| </section> | ||
| </section> | ||
| <section id="deployment"><h2><span class="section-heading">Deployment</span><span class="section-anchor"> <a href="#deployment"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2> | ||
| <p>This proposal is intended to be deployed with ${NU4}. <a id="id13" class="footnote_reference" href="#zip-0251">8</a></p> | ||
| </section> | ||
| <section id="references"><h2><span class="section-heading">References</span><span class="section-anchor"> <a href="#references"><img width="24" height="24" src="assets/images/section-anchor.png" alt=""></a></span></h2> | ||
| <table id="rfc2119" class="footnote"> | ||
| <tbody> | ||
| <tr> | ||
| <th>1</th> | ||
| <td><a href="https://www.rfc-editor.org/rfc/rfc2119.html">Key words for use in RFCs to Indicate Requirement Levels</a></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| <table id="protocol" class="footnote"> | ||
| <tbody> | ||
| <tr> | ||
| <th>2</th> | ||
| <td><a href="protocol/protocol.pdf">Zcash Protocol Specification [Overwinter+Sapling+Blossom]</a></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| <table id="trademark" class="footnote"> | ||
| <tbody> | ||
| <tr> | ||
| <th>3</th> | ||
| <td><a href="https://www.zfnd.org/about/contracts/2019_ECC_ZFND_TM_agreement.pdf">Zcash Trademark Donation and License Agreement</a></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| <table id="osd" class="footnote"> | ||
| <tbody> | ||
| <tr> | ||
| <th>4</th> | ||
| <td><a href="https://opensource.org/osd">The Open Source Definition</a></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| <table id="zip-0200" class="footnote"> | ||
| <tbody> | ||
| <tr> | ||
| <th>5</th> | ||
| <td><a href="zip-0200">ZIP 200: Network Upgrade Mechanism</a></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| <table id="zip-0207" class="footnote"> | ||
| <tbody> | ||
| <tr> | ||
| <th>6</th> | ||
| <td><a href="zip-0207">ZIP 207: Funding Streams</a></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| <table id="zip-0208" class="footnote"> | ||
| <tbody> | ||
| <tr> | ||
| <th>7</th> | ||
| <td><a href="zip-0208">ZIP 208: Shorter Block Target Spacing</a></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| <table id="zip-0251" class="footnote"> | ||
| <tbody> | ||
| <tr> | ||
| <th>8</th> | ||
| <td><a href="zip-0251">ZIP 251: Deployment of the ${NU4} Network Upgrade</a></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| <table id="zip-1014" class="footnote"> | ||
| <tbody> | ||
| <tr> | ||
| <th>9</th> | ||
| <td><a href="zip-1014">ZIP 1014: Establishing a Dev Fund for ECC, ZF, and Major Grants</a></td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| </section> | ||
| </section> | ||
| </body> | ||
| </html> |
Oops, something went wrong.