zip-1003.html

<!DOCTYPE html>
<html>
<head>
    <title>ZIP 1003: 20% Split Evenly Between the ECC and the Zcash Foundation, and a Voting System Mandate</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: 1003
Title: 20% Split Evenly Between the ECC and the Zcash Foundation, and a Voting System Mandate
Owners: aristarchus (zcash forums)
Status: Obsolete
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>
        <section id="terminology"><h2><span class="section-heading">Terminology</span><span class="section-anchor"> <a rel="bookmark" href="#terminology"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h2>
            <p>The key words "MUST", "MUST NOT", "SHOULD", and "SHOULD NOT" in this document are to be interpreted as described in RFC 2119. <a id="footnote-reference-1" class="footnote_reference" href="#rfc2119">1</a></p>
            <p>For clarity in this ZIP I define these terms:</p>
            <dl>
                <dt>2nd Halvening period</dt>
                <dd>the 4-year period of time, roughly from October 2020 to October 2024, during which at most 5,250,000 ZEC will be minted.</dd>
                <dt>3rd Halvening period</dt>
                <dd>the 4-year period of time roughly from October 2024 to October 2028.</dd>
                <dt>DF%</dt>
                <dd>Dev Fund Percentage, the portion of newly minted ZEC in each block reserved for a development fund.</dd>
            </dl>
        </section>
        <section id="abstract"><h2><span class="section-heading">Abstract</span><span class="section-anchor"> <a rel="bookmark" href="#abstract"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h2>
            <p>This proposal would allocate a 20% Dev Fund Percentage to be split evenly between the Electric Coin Company (ECC) and the Zcash Foundation during the 2nd Halvening period. This proposal aims to be simple to implement, without a single point of failure, and comes with mandates for transparency, accountability and a mandate to build a development fund voting mechanism to be used during the 3rd Halvening period. This proposal is designed to strike a balance between ensuring that high quality development work can continue uninterrupted, with the need to further decentralize Zcash development funding as soon as possible.</p>
        </section>
        <section id="motivation"><h2><span class="section-heading">Motivation</span><span class="section-anchor"> <a rel="bookmark" href="#motivation"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h2>
            <p>Strengths of this proposal:</p>
            <ol type="1">
                <li>Simple to implement. I would rather developers spend time scaling Zcash rather than implementing the development funding mechanism.</li>
                <li>Developers will have several years to work on a great decentralized development funding voting mechanism.</li>
                <li>20% is a large enough percentage that there should be enough development funding for many different ZEC price scenarios. To those who want to decrease this percentage: Overpaying for security is a gift to miners, to the detriment of every other stakeholder in the Zcash community. I will even make the strong statement that intentionally overpaying the miners for security is stealing from the other stakeholders.</li>
                <li>With two entities receiving funds there is no single point of failure.</li>
            </ol>
        </section>
        <section id="requirements-and-specification"><h2><span class="section-heading">Requirements and Specification</span><span class="section-anchor"> <a rel="bookmark" href="#requirements-and-specification"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h2>
            <ol type="1">
                <li>DF% MUST be 20 percent, split evenly between ECC and the Zcash Foundation during the 2nd Halvening period.</li>
                <li>The Dev Fund MUST only be spent on research, development and adoption of Zcash.</li>
                <li>A voting system for development funding MUST be built and implemented in order to be used during the 3rd Halvening period.</li>
            </ol>
            <section id="voting-system-requirements"><h3><span class="section-heading">Voting System Requirements</span><span class="section-anchor"> <a rel="bookmark" href="#voting-system-requirements"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h3>
                <p>Here are the general properties of the mandated voting mechanism. I don’t want to specify the technical implementation details, since I believe this is a job suited for the engineers building this system.</p>
                <ol type="1">
                    <li>Voting SHOULD be private.</li>
                    <li>Only ZEC holders can vote.</li>
                    <li>Voting should happen on-chain.</li>
                    <li>In order to vote, you must lock your ZEC so it cannot be spent for a period of time. This is to force the voters to have ‘skin in the game’ and prevent someone nefarious from buying a lot of ZEC just before an election and then dumping it immediately after.</li>
                    <li>Voters can choose how long to lock their ZEC, and their voting power is proportional to the time that the ZEC is locked. For example, someone who votes with 10 ZEC and locks it for 6 months would have the same voting power as someone who votes with 20 ZEC and locks it for 3 months. Of course there must be a maximum lock time, perhaps a year, to prevent anyone from getting ‘infinite’ voting power by locking their ZEC permanently.</li>
                    <li>The final results of the vote should be transparent to and verifiable by everyone.</li>
                    <li>The system should be totally open and allow anyone/any organization to compete for funding to develop Zcash.</li>
                </ol>
            </section>
            <section id="transparency-and-accountability-for-the-ecc-and-the-zcash-foundation"><h3><span class="section-heading">Transparency and Accountability for the ECC and the Zcash Foundation</span><span class="section-anchor"> <a rel="bookmark" href="#transparency-and-accountability-for-the-ecc-and-the-zcash-foundation"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h3>
                <p>These requirements would apply to both ECC and the Zcash Foundation. The mandate is to adhere to these accountability requirements originally put forward by the Foundation:</p>
                <ul>
                    <li>Monthly public developer calls, detailing current technical roadmap and updates.</li>
                    <li>Quarterly technology roadmap reports and updates.</li>
                    <li>Quarterly financial reports, detailing spending levels/burn rate and cash/ZEC on hand.</li>
                    <li>A yearly, audited financial report akin to the Form 990 for US-based nonprofits.</li>
                    <li>Yearly reviews of organization performance, along the lines of the State of the Zcash Foundation report <a id="footnote-reference-2" class="footnote_reference" href="#zfnd-state">2</a>.</li>
                </ul>
            </section>
            <section id="requirements-specifically-for-the-ecc"><h3><span class="section-heading">Requirements Specifically for the ECC</span><span class="section-anchor"> <a rel="bookmark" href="#requirements-specifically-for-the-ecc"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h3>
                <p>Motivated by the Zcash Foundation’s proposal that the ECC become a non-profit <a id="footnote-reference-3" class="footnote_reference" href="#zfnd-guidance">3</a>, I am going to list general requirements for the ECC to abide by if they choose to receive funds and work on behalf of ZEC holders.</p>
                <ol type="1">
                    <li>Because I share the Foundation’s concern that the ECC could be “beholden to its shareholders”, I am mandating that the ECC should be working in the service of the Zcash community and <strong>shall serve no other masters</strong>. The original investors/founders who are not still working in the service of the Zcash community SHOULD NOT have control over the use of the new development funds.</li>
                    <li>The revenue received from the Dev Fund SHOULD NOT be used to give further rewards to, even indirectly, the investors, founders, or shareholders of the ECC, who are not working on Zcash after the first halving. <strong>They have already received the Founders’ Reward and this new development fund is not supposed to further benefit them.</strong></li>
                    <li>The ECC SHOULD offer competitive pay and <strong>a stake in upside of the success of Zcash as a way to attract the best and brightest</strong>. I do want the ECC be able to <strong>maintain a world class team</strong> capable of competing with the tech giants of the world (Google, Apple etc.).</li>
                    <li>The ECC SHOULD <strong>continue to engage with regulators</strong> and advocate for privacy preserving technology. The <strong>legal structure of the ECC must not hamper these critical efforts</strong> in any way.</li>
                </ol>
                <p>I am not mandating non-profit status for the ECC. Maybe that is the best legal structure, maybe something else is better.</p>
                <p>Finally, in the event that the voting system isn’t implemented by the start of the 3rd Halvening period, the 20% of funds intended to go to the ‘voting development fund’ should instead not be minted.</p>
            </section>
        </section>
        <section id="references"><h2><span class="section-heading">References</span><span class="section-anchor"> <a rel="bookmark" href="#references"><img width="24" height="24" class="section-anchor" 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">RFC 2119: Key words for use in RFCs to Indicate Requirement Levels</a></td>
                    </tr>
                </tbody>
            </table>
            <table id="zfnd-state" class="footnote">
                <tbody>
                    <tr>
                        <th>2</th>
                        <td><a href="https://www.zfnd.org/blog/foundation-in-2019/">The State of the Zcash Foundation in 2019. Zcash Foundation blog, January 31, 2019.</a></td>
                    </tr>
                </tbody>
            </table>
            <table id="zfnd-guidance" class="footnote">
                <tbody>
                    <tr>
                        <th>3</th>
                        <td><a href="https://www.zfnd.org/blog/dev-fund-guidance-and-timeline/">Zcash Foundation Guidance on Dev Fund Proposals. Zcash Foundation blog, August 6, 2019.</a></td>
                    </tr>
                </tbody>
            </table>
        <br></section>
        <section id="change-log"><h2><span class="section-heading">Change Log</span><span class="section-anchor"> <a rel="bookmark" href="#change-log"><img width="24" height="24" class="section-anchor" src="assets/images/section-anchor.png" alt=""></a></span></h2>
            <ul>
                <li>2019-06-19 Initial post</li>
                <li>2019-26-07 Listed three strengths of this proposal</li>
                <li>2019-08-13 Voting System Requirements</li>
                <li>2019-08-20 Requirements Specifically for the ECC</li>
                <li>2019-08-29 Update to be more like a ZIP draft.</li>
            </ul>
        </section>
    </section>
</body>
</html>