Zcash in Simplified Technical English

This page is the Simplified Technical English version of ZIP 1014. The source ZIP is the normative text. Read the writing rules to understand the marked words.

ZIP 1014: Establishing a Dev Fund for ECC, ZF, and Major Grants

ZIP: 1014
Title: Establishing a Dev Fund for ECC, ZF, and Major Grants
Owners: Andrew Miller <socrates1024@gmail.com>
        Zooko Wilcox <zooko@shieldedlabs.net>
Original-Authors: Eran Tromer
Credits: Matt Luongo
         @aristarchus
         @dontbeevil
         Daira-Emma Hopwood
         George Tankersley
         Josh Cincinnati
         Andrew Miller
Status: Active
Category: Consensus Process
Created: 2019-11-10
License: MIT
Discussions-To: <https://forum.zcashcommunity.com/t/community-sentiment-polling-results-nu4-and-draft-zip-1014/35560>
Pull-Request: <https://github.com/zcash/zips/pull/308>

Terminology

On this page, STE words are in the place of the BCP 14 key words of the source. Refer to the key word table.

The term "network upgrade" on this page has the meaning in ZIP 200 [zip-0200] and in the Zcash Trademark Donation and License Agreement ([trademark] or a successor agreement).

The terms "block subsidy" and "halving" on this page have the meanings in sections 3.10 and 7.8 of the Zcash Protocol Specification [protocol].

The terms "Testnet" and "Mainnet" have the meanings in section 3.12 of the Zcash Protocol Specification [protocol-networks].

The other terms on this page have these meanings:

"Electric Coin Company", also called "ECC"
The Zerocoin Electric Coin Company, LLC.
"Bootstrap Project", also called "BP"
The 501(c)(3) nonprofit corporation of that name.
"Zcash Foundation", also called "ZF"
The 501(c)(3) nonprofit corporation of that name.
"Section 501(c)(3)"
That section of the U.S. Internal Revenue Code (Title 26 of the U.S. Code) [section501c3].
"Community Advisory Panel"
The panel of community members that the Zcash Foundation assembled. A description of the panel is in [zf-community].

Abstract

This ZIP contains a structure for the Zcash Development Fund. The Dev Fund is to be enacted in Network Upgrade 4, and it is to continue for 4 years. This Dev Fund consists of 20% of the block subsidies, split into 3 slices:

Governance and accountability are based on existing entities and legal mechanisms. Also, increasingly decentralized governance is encouraged.

Motivation

From the first halving of Zcash in October 2020, by default, 100% of the block subsidies will be allocated to miners. No further funds will be automatically allocated to other entities. Consequently, it is possible that no substantial new funding will be available to the existing teams that work to advance charitable, educational or scientific purposes. Examples of these purposes are research, development and outreach. These teams are:

It is necessary to find a balance between these two items:

It is also necessary to find a balance between these two items:

For these reasons, the Zcash Community wants to allocate and contribute a slice of the block subsidies as a donation. Otherwise, this slice is allocated to miners. The purpose of the donation is to support charitable, educational and scientific activities within the meaning of Section 501(c)(3).

Requirements

We recommend that the Dev Fund is used to encourage decentralization of the work and the funding, through support for new teams dedicated to Zcash.

Concrete opportunities to create even greater value for the Zcash ecosystem can occur. Unless and until they occur, we recommend that the Dev Fund is used to keep the existing teams and capabilities in the Zcash ecosystem.

We recommend that no single entity is a single point of failure. A single point of failure is an entity with this property: if the entity is captured or fails, then in effect the funds cannot be used effectively.

We recommend that major funding decisions are based, as much as possible, on inputs from domain experts and applicable stakeholders.

We recommend that the monetary emission curve is not changed by the Dev Fund mechanism. In particular, we recommend that coins are not irrevocably burned by the mechanism.

If the value of ZEC increases suddenly, we recommend that the Dev Fund recipients do not use excessive amounts of funds wastefully. Conversely, because of market volatility and the halvings that will eventually occur, it is desirable to create reserves for bad periods.

We recommend that the financial privacy or security of users is not decreased by the Dev Fund mechanism. In particular, we recommend that users do not have to expose their coin holdings because of the mechanism. Also, we recommend that users do not have to keep access to secret keys for much longer than they otherwise do because of the mechanism. (Because of this recommendation, some forms of voting are excluded. Some forms of disbursement of coins to past or future miners are excluded also.)

We recommend that the new Dev Fund system is simple to understand and realistic to implement. In particular, we recommend that the execution of the system does not depend on the creation of new mechanisms (for example, election systems) or new entities (for governance or development). But after these mechanisms and entities are built, we recommend an effort to support them and use them in the system.

Obey the legal, regulatory and taxation constraints in the applicable jurisdictions.

Non-requirements

General on-chain governance is outside the scope of this ZIP.

Rigorous voting mechanisms are outside the scope of this ZIP. This applies to all of these types:

But this ZIP contains prescribed room to integrate these mechanisms when they become available.

Specification

The consensus changes that this specification implies apply to the Zcash Mainnet. We recommend that similar consensus changes are applied to the Zcash Testnet for testing purposes. These changes on the Testnet are not necessarily identical.

Dev Fund allocation

From the first Zcash halving in 2020 until the second halving in 2024, 20% of each block subsidy must be allocated to a "Dev Fund". The Dev Fund consists of these three slices:

  • 35% for the Bootstrap Project (the name of this slice is BP slice).
  • 25% for the Zcash Foundation, for general use (the name of this slice is ZF slice).
  • 40% for additional "Major Grants" for large-scale long-term projects (the name of this slice is MG slice).

More detail about the slices is in the sections that follow. The fund flow will be implemented at the consensus-rule layer. For each block, the corresponding ZEC will be sent to the designated address or addresses. This Dev Fund will end at the second halving, unless it is extended or changed by a future ZIP.

BP slice (Bootstrap Project)

This slice of the Dev Fund will go to the Bootstrap Project as charitable contributions from the Zcash Community. The Bootstrap Project is the newly formed parent organization of the Electric Coin Company. The Bootstrap Project is organized for exempt educational, charitable and scientific purposes, in compliance with Section 501(c)(3). These purposes include, but are not limited to, the advancement of these items, related to cryptocurrency and privacy, including Zcash:

  • Education.
  • Information.
  • Resources.
  • Advocacy.
  • Support.
  • Community.
  • Research.

The Bootstrap Project will use this slice at its discretion, within the limits of Section 501(c)(3). It can use the slice for any purpose within its mandate to support financial privacy and the Zcash platform. The BP slice will be treated as a charitable contribution from the Community. The purpose of this contribution is to support these educational, charitable and scientific purposes.

ZF slice (Zcash Foundation's general use)

This slice of the Dev Fund will go to ZF as charitable contributions from the Zcash Community. ZF will use the slice at its discretion, subject to the requirements of Section 501(c)(3). It can use the slice for any purpose within its mandate to support financial privacy and the Zcash platform. These purposes include:

  • Development.
  • Education.
  • Support for community communication, online and through events.
  • The collection of community sentiment.
  • External grants for all of the above.

The ZF slice will be treated as a charitable contribution from the Community. The purpose of this contribution is to support these educational, charitable and scientific purposes.

MG slice (Major Grants)

This slice of the Dev Fund is intended to fund independent teams that enter the Zcash ecosystem. These teams are to do major ongoing development (or other work) for the public good of the Zcash ecosystem. This intention applies to the extent that such teams are available and effective.

ZF must receive and administer the funds. ZF must disburse them for "Major Grants" and expenses reasonably related to the administration of Major Grants, but subject to these additional constraints:

  1. These funds must only be used for these two purposes:

    • To issue Major Grants to external parties that are independent of ZF.
    • To pay for expenses reasonably related to the administration of Major Grants.

    ZF must not use them for its internal operations and direct expenses that are not related to the administration of Major Grants. Also, BP, ECC and ZF are not eligible to receive Major Grants.

  2. We recommend that Major Grants are for well-specified work that the grantee proposes, at reasonable market-rate costs. A Major Grant can be of any duration, or it can continue with no duration limit. We recommend that grants of indefinite duration have semiannual review points for continuation of funding.

  3. Some teams have a substantial continual existence (current or prospective). We recommend that priority is given to Major Grants that strengthen these teams and prepare them for long-term success. This priority is subject to the usual considerations for grant awards (impact, ability, risks, team, cost-effectiveness and other items).

    We recommend that priority is given to Major Grants that are for the growth of the ecosystem. Examples are mentorship, coaching, technical resources, the creation of entrepreneurial opportunities and other items.

    Two proposals can have substantially the same plans. In that case, we recommend priority for the originator of the plans.

  4. We recommend that Major Grants are restricted to the advancement of the Zcash cryptocurrency and its ecosystem, within the limits of Section 501(c)(3). (This restriction is more specific than the advancement of financial privacy in general.)

  5. Major Grants awards are subject to approval by a five-seat Major Grant Review Committee. The Major Grant Review Committee must be selected by the ZF's Community Advisory Panel or successor process.

  6. The funding decisions of the Major Grant Review Committee will be final. No approval from the ZF Board is necessary for them. But they are subject to veto if the Foundation judges that they violate one of these:

    • U.S. law.
    • The reporting requirements and other (current or future) obligations of the ZF under U.S. IRS 501(c)(3).
  7. Major Grant Review Committee members must have a one-year term. They can be candidates for reelection.

    The Major Grant Review Committee is subject to the same conflict of interest policy that applies to the ZF Board of Directors. (That is, the members must recuse themselves when they vote on proposals where they have a financial interest.)

    A maximum of one person with association with the BP/ECC can sit on the Major Grant Review Committee. Also, a maximum of one person with association with the ZF can sit on it. "Association" here means one of these:

    • A financial interest.
    • Full-time employment.
    • A position as an officer.
    • A position as a director.
    • An immediate family relationship with any of the above.

    The ZF must continue to operate the Community Advisory Panel. Also, we recommend that the ZF works to make the panel more representative and independent. (More about this is in a section below.)

  8. From 1st January 2022, a portion of the MG Slice must be allocated to a Discretionary Budget. The Discretionary Budget can be disbursed for expenses reasonably related to the administration of Major Grants. The amount of funds allocated to the Discretionary Budget must be decided by the ZF's Community Advisory Panel or successor process. The Major Grant Review Committee must approve any disbursement of funds from the Discretionary Budget.

    Expenses related to the administration of Major Grants include, without limitation, these items:

    • Payments to third party vendors for services related to domain name registration.
    • Payments to third party vendors for services related to the design, website hosting and administration of websites for the Major Grant Review Committee.
    • Payments to independent consultants to develop requests for proposals that are aligned with the Major Grants program.
    • Payments to independent consultants for expert review of grant applications.
    • Payments for sales and marketing services to promote the Major Grants program.
    • Payments to third party consultants to do activities that are for the purpose of the Major Grants program.
    • Reimbursement to members of the Major Grant Review Committee for reasonable travel expenses, including transportation, hotel and meals allowance.

    The decisions of the Major Grant Review Committee about the allocation and disbursement of funds from the Discretionary Budget will be final. No approval from the ZF Board is necessary for them. But they are subject to veto if the Foundation judges that they violate one of these:

    • U.S. law.
    • The reporting requirements and other (current or future) obligations of the ZF under U.S. IRS 501(c)(3).

ZF must recognize the MG slice of the Dev Fund as a Restricted Fund donation under the above constraints (suitably formalized). ZF must also keep separate accounting of the balance and usage of the MG slice, under its Transparency and Accountability obligations below.

ZF must try hard to define target metrics and key performance indicators. We recommend that the Major Grant Review Committee uses these in its funding decisions.

Direct-grant option

Operationally or legally, it can be considered better to assign the Major Grant funds directly to the grantees, with no acceptance and disbursement by ZF. If ECC and ZF both agree before Network Upgrade 4 (Canopy) activation, this mechanism can thus be used in perpetuity for some or all grantees:

Before each network upgrade, the Foundation must publish a list that contains these items:

  • The addresses of the grantees.
  • The total number of Dev Fund ZEC per block that each grantee is to receive.

ECC and ZF must implement this list in any implementations of the Zcash consensus rules that they maintain. Then, in effect, the miners will ratify this decision at the activation of the network upgrade.

Transparency and Accountability

Obligations

BP, ECC, ZF and Major Grant recipients must all accept the obligations in this section. (For Major Grant recipients, this applies during their award period and in the period that leads to it.)

These are the ongoing requirements for public reports:

  • Quarterly reports, with details of future plans, of the execution of previous plans and of finances. The details of finances are the balances, and the spending broken down by major categories.
  • Monthly developer calls, or a brief report, about recent and future tasks. (Developer calls can be shared.)
  • An annual detailed review of the performance and the future plans of the organization.
  • An annual financial report (IRS Form 990, or substantially similar information).

These reports can be of one of these two types:

  • Organization-wide.
  • Restricted to the income, expenses and work associated with the receipt of Dev Fund.

BP is the parent organization of ECC. Thus it is expected that BP and ECC can publish joint reports.

It is expected that ECC, ZF and Major Grant recipients will focus primarily on Zcash, with their attention and resources. Thus they must promptly disclose these items:

  • Any major activity that they do (even if it is not supported by the Dev Fund) that is not in the interest of the general Zcash ecosystem.
  • Any conflict of interest with the general success of the Zcash ecosystem.

BP, ECC, ZF and grant recipients must promptly disclose any security or privacy risks that can have an effect on users of Zcash. (Where applicable, they do this by responsible disclosure under confidence to the applicable developers.)

We recommend that each of these reports is at least as detailed as the grant proposals and reports that other funded parties send:

  • The reports of BP.
  • The reports of ECC.
  • The annual report of ZF on its non-grant operations.

We also recommend that these reports satisfy similar levels of public scrutiny.

We recommend that all substantial software whose development was funded by the Dev Fund is released under an Open Source license. (The Open Source Initiative defines this term [osd].) The preferred license is the MIT license.

Enforcement

For grant recipients, we recommend that these conditions are included in their contract with ZF. With these conditions, a substantial violation that is not promptly corrected will cause the forfeiture of the grant funds. Then the funds will go back to ZF.

BP, ECC and ZF must make a contractual commitment to each other to obey these conditions and the prescribed use of funds. Assume that one party does a substantial violation and does not promptly correct it. Under this commitment, the other party will then have the right to do these two things:

  • Issue a modified version of Zcash node software, with no Dev Fund slice for the violating party.
  • Use the Zcash trademark for this modified version.

The funds of that slice will be reassigned to MG. (The integrity of MG is legally protected by the Restricted Fund treatment.)

Future Community Governance

In this ZIP, decentralized community governance is used through the Community Panel. The Community Panel gives input to the Major Grant Review Committee. The Major Grant Review Committee governs the MG slice (Major Grants).

It is highly desirable to develop robust means of decentralized community voting and governance. (This is possible through an expansion of the Community Advisory Panel, or through a successor mechanism.) It is also highly desirable to integrate these means into this process by the end of 2021. We recommend that BP, ECC and ZF give high priority to such development and its deployment, in their activities and grant selection.

ZF Board Composition

Except under the grace period below, ZF Board members must not hold ECC equity or have current business or employment relationships with ECC.

Grace period: this rule is for members of the ZF board who hold ECC equity, but have no other current relationships to ECC. These members can dispose of their equity, or leave the Board, by 1 November 2021. (One purpose of the grace period is an orderly replacement. Another purpose is time for ECC corporate reorganization related to Dev Fund receipt. This reorganization can have an effect on how the disposition of equity is done.)

We recommend that the Zcash Foundation tries to use the Community Advisory Panel (or a successor mechanism) as advisory input for future board elections.

Acknowledgements

This ZIP is a limited modification of the ZIP 1012 of Eran Tromer [zip-1012]. The Zcash Foundation and the ECC made this modification. Then more changes were made because of feedback from the community and the results of the latest Helios poll.

The proposal of Eran is most closely based on the Matt Luongo 'Decentralize the Dev Fee' proposal (ZIP 1011) [zip-1011]. Relative to ZIP 1011, there are substantial changes. Also, elements from these sources are mixed in:

The authors are grateful to all of the above for their excellent ideas and any insightful discussions. The authors are also grateful to the forum users @aristarchus and @dontbeevil for valuable initial comments on ZIP 1012.

References

[BCP14]
Information on BCP 14 — "RFC 2119: Key words for use in RFCs to Indicate Requirement Levels" and "RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words"
[protocol]
Zcash Protocol Specification, Version 2021.2.16 or later
[protocol-networks]
Zcash Protocol Specification, Version 2021.2.16. Section 3.12: Mainnet and Testnet
[trademark]
Zcash Trademark Donation and License Agreement
[osd]
The Open Source Definition
[zip-0200]
ZIP 200: Network Upgrade Mechanism
[zip-1003]
ZIP 1003: 20% Split Evenly Between the ECC and the Zcash Foundation, and a Voting System Mandate
[zip-1010]
ZIP 1010: Compromise Dev Fund Proposal With Diverse Funding Streams
[zip-1011]
ZIP 1011: Decentralize the Dev Fee
[zip-1012]
ZIP 1012: Dev Fund to ECC + ZF + Major Grants
[zf-community]
ZF Community Advisory Panel
[section501c3]
U.S. Code, Title 26, Section 501(c)(3)