This page is the Simplified Technical English version of ZIP 1006. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 1006: Development Fund of 10% to a 2-of-3 Multisig with Community-Involved Third Entity
ZIP: 1006
Title: Development Fund of 10% to a 2-of-3 Multisig with Community-Involved Third Entity
Owners: James Todaro <james@blocktown.capital>
Joseph Todaro <joseph@blocktown.capital>
Credits: Mario Laul
Chris Burniske
Status: Obsolete
Category: Consensus Process
Created: 2019-08-31
License: MIT
Discussions-To: <https://forum.zcashcommunity.com/t/blocktown-development-fund-proposal-10-to-a-2-of-3-multisig-with-community-involved-third-entity/34782>
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 additional terms that follow have these meanings:
- Mining
- The processing of transactions. If Zcash implements a Proof-of-Stake system or a hybrid Proof-of-Work/Proof-of-Stake system at a future date, mining includes the processing of transactions in that system.
- Mining software
- Pool software, local mining software or staking software.
- Mining rewards / Block rewards
- Network transaction fees, coinbase rewards, or both. An example of a coinbase reward is newly issued ZEC that is related to block generation.
- Network Upgrade
- Any change to a consensus rule of the Zcash protocol. The change can be a part of the standard Zcash Network Upgrade Pipeline [nu-pipeline], or it can come from a different process.
- Founder’s Reward
- The 20% of the ZEC from mined blocks that is allocated to some or all of these entities:
- The Electric Coin Company (ECC).
- The Zcash Foundation (ZF).
- Employees.
- Investors.
- Other entities.
- Zcash Development Fund
- One or more transparent addresses that these entities control jointly:
- The Electric Coin Company.
- The Zcash Foundation.
- A “Third Entity”.
- Research, development, maintenance and other technical work that is directly connected to the Zcash protocol.
- Non-technical initiatives that contribute to the long-term success of the Zcash network. These initiatives include these items:
- Design.
- Marketing.
- Events.
- Regulatory outreach.
- Education.
- Governance.
- Any other form of business or community development.
- Applicant
- Any individual, group or entity that asks for funding from the Zcash Development Fund.
- Recipient
- Any individual, group or entity that receives funding from the Zcash Development Fund.
Abstract
This ZIP contains the proposed financing mechanism and the fundamental rules of governance for the creation of a Zcash Development Fund.
Specification
Funding mechanism of the Zcash Development Fund
- This funding mechanism must be hard-coded. With this mechanism, 10% of newly issued ZEC from block rewards must go automatically to the transparent addresses of the Zcash Development Fund.
- The requirement above must be met between the first halving and the second halving. At the second halving, future governance decisions can result in a further decrease of the Zcash Development Fund. This decrease is to 5% of newly issued ZEC from block rewards. Alternatively, these decisions can result in a different percent allocation. One possible allocation is a system where 100% of block rewards go to miners.
- The two requirements above must stay in effect, independently of any additional Network Upgrades or changes to mining or mining software before the second halving.
- The Zcash Development Fund can continue after the period of its initial funding mechanism. Two possible causes are an increase in the price of ZEC and other funding sources at the second halving in 2024.
- The hard-coded transparent addresses of the Zcash Development Fund can be rotated periodically for operational security. The purpose is to decrease the risk of a possible loss of the funds at these addresses. Within the limits of this Specification section, we recommend that one or more of these entities take all possible precautions against a loss of funds:
- The ECC.
- The ZF.
- The “Third Entity”. The next section has information about the Third Entity.
Governance of the Zcash Development Fund
- The funds that go to the Zcash Development Fund must be used only for their intended purpose. This purpose is in the Rationale section of this ZIP.
- The ECC, the ZF and the Third Entity must jointly control the transparent addresses of the Zcash Development Fund. On this page, these three organizations are “the three entities”. The three entities must confirm each transfer of funds from the Zcash Development Fund by a majority decision. This confirmation must be public and official. The usual name for this method is “2-of-3 multisig”. That is, funding decisions must go to an officially documented vote. This vote must not pass unless a minimum of 2 of the 3 entities vote for approval.
- The ZF and the ECC must coordinate with each other and with the community to establish the Third Entity. They must do this before any movement of funds from the Zcash Development Fund. The Third Entity will have a part in the governance of the Zcash Development Fund. The process to determine the exact initial composition and governance rules of the Third Entity must include the Zcash community at large. This process must be similar to the process in the section "How the Foundation will select a particular proposal" of the ZF’s statement of August 6, 2019 [zfnd-guidance].
The governance rules of the Third Entity must include these items:
- All decision-making and other governing processes of the Third Entity must be independent of the ECC and the ZF. These processes must include the measures that are necessary to prevent conflicts of interest with the ECC and the ZF.
- At creation, the Third Entity must include an uneven number of individuals with independent previous affiliations, with a minimum of 5. Each of these individuals must have a single vote. For an approving vote of the Third Entity as a whole, each such decision must have majority support in the Third Entity.
- After the Third Entity is established, it can decide to change its rules of governance. (An example is the choice between simple majority rules and supermajority rules.) But the Zcash community at large must be involved before any such change. This involvement must be similar to the process in the ZF’s statement of August 6, 2019 [zfnd-guidance].
- After the Third Entity is established as a self-governing body, we recommend that it moves toward a system where ZEC holders have a direct role. In this system, ZEC holders have a direct role to determine the votes and the internal governance of the Third Entity.
- If its governing body decides that it is applicable, the Third Entity can apply for funding from the Zcash Development Fund. Such funding is subject to a majority vote of the three entities.
Before any transfer of funds from the Zcash Development Fund, the three entities must do these steps:
- Specify the final rules for applications and for receipt of funding from the Zcash Development Fund.
- Approve these rules.
- Make these rules public.
These rules must include the details of the decision-making process to approve or reject funding requests. These rules must apply equally to all Applicants, including the three entities. These rules must also include these items:
- Funding from the Zcash Development Fund must be available to the three entities and also to other individuals, groups or entities. These other individuals, groups or entities are the ones that can make technical contributions, non-technical contributions, or both, to Zcash. The Rationale section of this ZIP has a description of these contributions.
- To receive funding from the Zcash Development Fund, all Applicants must obey two sets of rules: the rules in the Specification section of this ZIP, and the final detailed rules of the three entities.
- As part of an application, each Applicant must make a public overview of the activities and the projected costs that it asks funds for.
- Before each funding decision, there must be a community review period of a reasonable length. The three entities determine this length. In this period, Zcash stakeholders and community members can learn about the request of the Applicant. They can also make suggestions or raise objections.
- This item applies to a request from an Applicant that has overwhelming opposition from Zcash stakeholders and community members. For such a request, we recommend that the three entities do not approve the request before they do these steps:
- Try to address the concerns of the stakeholders and the community.
- If applicable, change the request to decrease these concerns.
- With each funding decision, there must be a joint public statement from the three entities that is easy to refer to. This statement must include the final tally of the applicable vote. It must also include the votes of the three entities. In this statement, each of the three entities must give an explicit justification for its vote.
- The ZF must make sure that all votes of the Zcash Development Fund, and the justifications above, stay archived. The ZF must also make sure that these groups can easily access the votes and the justifications online:
- Zcash community members.
- Zcash stakeholders.
- The general public.
- The three entities can approve funding requests on a rolling basis. But all funding requests must be examined again and voted on a minimum of one time in each 6 months, to get renewed approval.
- Recipients must make progress updates public, a minimum of one time each quarter. These updates are about their activities that get funding from the Zcash Development Fund. For a short-term assignment (less than 6 months), a single report at the end of the project is sufficient. Before any approval of a request for funds from the Zcash Development Fund, the three entities must specify standard reporting requirements. Additional requirements can be introduced when necessary.
- Funds can be paid in a single payment or in increments, subject to objective milestones, other performance metrics, or both. This selection depends on the nature of each request.
The governance of the Zcash Development Fund is in this ZIP and in the final detailed rules of the three entities. Each decision to change this governance must involve the Zcash community at large. This involvement must be similar to the process in the ZF’s statement of August 6, 2019 [zfnd-guidance]. All transfers from the Zcash Development Fund must agree fully with the requirements of this ZIP.
Issues not addressed in this proposal/Out-of-Scope
These issues are out of the scope of this ZIP:
- The details of the decision-making process to support or reject this ZIP or other applicable proposals. The deciders in this process are one or more of these:
- The ECC.
- The ZF.
- Other Zcash stakeholders.
- Additional methods to measure community sentiment can include a way for ZEC holders to signal their support for specific proposals.
- The question if the ECC is to change into a non-profit organization or stay a for-profit organization. The ZF addressed this question in its statement of August 6, 2019 [zfnd-guidance]. This ZIP is neutral on this question. Funding from the Zcash Development Fund can go to non-profit entities, for-profit entities, or both. We consider that the governance rules of the Zcash Development Fund in the Specification section are adequate for transparency and accountability.
Motivation
According to the current protocol specifications, the first halving of the Zcash network is scheduled for October 2020. The Founder’s Reward is 20% of the ZEC from each block reward. According to the codebase, the Founder’s Reward will stop at the time of the first halving. If the codebase does not change, miners get 100% of block rewards after the first halving. An example of such a change is a change in the upcoming NU4 Network Upgrade.
At this time, two organizations lead the development and maintenance of the Zcash network. These organizations, the ECC and the ZF, receive funds from the Founder’s Reward. Recently, they asked for a source of funding after the first halving, to continue operations for the foreseeable future. In theory, this source can be a change to the codebase for a Zcash Development Fund from block rewards. Alternatively, it can be external sources. But the ECC stated that it prefers to “wind down or pivot” instead of accepting funding from any sources that give “special interests” control over the ECC [ecc-assessment].
Because of the demands of the ECC, the block reward appears to be the most agreeable source of resources for a Zcash Development Fund.
This ZIP was first published in the Zcash Community Forum on August 14, 2019 [blocktown-proposal]. It was then formalized further in a blog post on August 23, 2019 [blocktown-blog]. This ZIP contains an outline of the funding mechanism and the governance of such a Zcash Development Fund. In this ZIP, we propose a feature of NU4. With this feature, 10% of the ZEC from each new block reward goes directly into a Zcash Development Fund, between the first and second halvings.
From the launch of the Zcash network in 2016 until the first halving, a centralized 20% fee is taken from the block reward. The name of this fee is the Founder’s Reward. Other active ZIP drafts contain a proposal for a Zcash Development Fund of 20% from the block reward after the first halving. We believe that eight cumulative years of centralized fees from the block reward at the same rate of 20% will finally cause a narrow community. This community accepts the probability of a permanent 20% fee on the Zcash network.
With a Zcash Development Fund of only 10% of the block reward, there will be a precedent. The precedent is that a large centralized fund is temporary. Such a fund decreases faster than the rate of block reward halvings alone. This ZIP is specifically about the period between the first and second halving. But this proposed feature can be a precedent for a continuous decrease of the percent fee from block rewards for a Zcash Development Fund. In this precedent, the fee decreases at each halving, for example:
- 20% (FR) from 2016-2020.
- 10% from 2020-2024.
- 5% from 2024-2028.
- 2.5% from 2028-2032.
Thus the ZEC for a development fund effectively decreases to one quarter every four years. We believe that this social contract can restore the faith of the community in the decentralization of Zcash. The cause is that, over time, the network incentives become more similar to the incentives of Bitcoin. Alternatively, it is acceptable for the Zcash governance system to select a 0% allocation for the Zcash Development Fund at the second halving. For a more detailed exploration about the selection of 10%, read the blog post ‘Proposal for 10% Dev Fund in Zcash 2020 Network Upgrade’ [blocktown-10pc].
Note: we do not suggest or imply that the funding from the Founder’s Reward and a Zcash Development Fund have similar management or similar directives. With the Zcash Development Fund feature that we propose for NU4, no funds go to former angel investors, VCs or vested employees. Also, the Zcash Development Fund is subject to more explicit and transparent rules of governance. These rules are in the Specification section of this ZIP.
Rationale
The reasons for this ZIP are as follows:
- To supply financial resources for these items:
- Research, development and any other technical work that is connected to software upgrades or maintenance of the Zcash protocol.
- Non-technical initiatives that contribute to the success of the Zcash network. These initiatives include these items:
- Marketing.
- Design.
- Events.
- Regulatory outreach.
- Education.
- Governance.
- Any other form of business.
- To increase the decentralization and the network security of the Zcash network.
- To increase decentralization through more community involvement in Zcash governance and resource allocation.
- To establish basic rules of governance and accountability for the deployment of funds in the Zcash Development Fund.
- To encourage transparency and cooperation among Zcash stakeholders. Also, to make the governance capabilities of the community stronger in the future.
Discussion
Known objections to this ZIP include:
- This ZIP is not in agreement with the current Zcash protocol. The current Zcash protocol is programmed to allocate 100% of the coinbase to miners at the first halving in 2020. But we believe that a funded and dedicated development team is an advantage, at least during the next few years of the infancy of Zcash.
- The funding mechanism in this ZIP is a Zcash Development Fund of 10% of newly issued ZEC from block rewards after the first halving. In other proposals, 20% of the mining rewards goes to the Zcash Development Fund. This is probably a popular selection because the original Founder’s Reward was also 20%. We explored the reasons in depth [blocktown-10pc] and summarized them in [blocktown-summary]. For these reasons, we believe that 10% is better than 20% for these items:
- Network security.
- Decentralization.
- Unity of the Zcash community.
- Renewed interest in ZEC.
- The different parameters of governance for the approval of requests from Applicants for funding from the Zcash Development Fund.
- The inclusion of a Third Entity in governance. One important objection is the possibility of collusion between the Third Entity and the ECC or the ZF. The result of this collusion can be a “usurped” Zcash Development Fund. But we believe that the process for a Third Entity that the community elects will become more mature over time. With this process, the community and Zcash stakeholders get that important third opinion when they decide the correct allocation of funds. Well-formed communities usually resist any collusion with corporations and controlling entities that do not promote the direct success of the network. The resilience of the Bitcoin network and community is a demonstration of this. Also, the inclusion of a Third Entity has an advantage: a “tie-breaker” for one or both of these situations:
- A deadlock vote between the ECC and the ZF.
- A situation where one entity holds the other hostage. This situation is possible in a 2-of-2 multisig agreement.
- This ZIP does not have a clause that says that a Recipient must not vote. Suppose that a Recipient must not vote in a 2-of-3 multisig governance system. Then, as with a 2-of-2 multisig, the result can be that one entity holds another hostage. For example, suppose that the ECC refuses to fund the ZF until the ZF obeys the demands of the ECC. Then the ECC has the power to deadlock any vote to fund the ZF. For such a vote, approval from both the ECC and the Third Entity is necessary.
Acknowledgements
Some parts of this ZIP were adapted from definitions and concepts in Placeholder’s dev fund proposal of August 22, 2019 [placeholder-proposal]. These definitions and concepts were also expanded. These parts are mainly in the Terminology and Specification sections.
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"
- [zfnd-guidance]
- Zcash Foundation Guidance on Dev Fund Proposals. Zcash Foundation blog, August 6, 2019.
- [ecc-assessment]
- ECC Initial Assessment of Community Proposals. Electric Coin Company blog, August 26, 2019.
- [blocktown-proposal]
- Proposal for the Zcash 2020 Network Upgrade (topic on the Zcash community forum).
- [blocktown-blog]
- Blocktown Proposal for Zcash 2020 Network Upgrade. Blocktown Capital, August 23, 2019.
- [blocktown-10pc]
- Proposal for 10% Dev Fund in Zcash 2020 Network Upgrade. Blocktown Capital, August 14, 2019.
- [blocktown-summary]
- Executive Summary: Blocktown Proposal for Zcash 2020 Network Upgrade. Blocktown Capital, August 15, 2019.
- [placeholder-proposal]
- Dev Fund Proposal: 20% to a 2-of-3 multisig with community-involved governance (topic on the Zcash community forum).
- [nu-pipeline]
- The Zcash Network Upgrade Pipeline. Electric Coin Company blog, December 3, 2018.