This page is the Simplified Technical English version of ZIP 1007. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 1007: Enforce Development Fund Commitments with a Legal Charter
ZIP: 1007 Title: Enforce Development Fund Commitments with a Legal Charter Owners: @lex-node (zcash forums) @mistfpga (zcash forums) <steve@mistfpga.net> Status: Obsolete Category: Consensus Process Created: 2019-08-24 License: CC BY-SA 4.0 <https://creativecommons.org/licenses/by-sa/4.0/> Discussions-To: <https://forum.zcashcommunity.com/t/dev-fund-supplemental-proposal-enforce-devfund-commitments-with-legal-charter/34709>
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.
For clarity, this ZIP contains a definition of this term:
- Covenant
- A legally binding agreement. In this agreement, a specific aspect of the development of the Zcash protocol, of adoption, or of both, is scheduled and agreed.
Abstract
This ZIP is a supplemental proposal. Its purpose is to make sure that the selection of features and the work are community-driven.
We hope that this ZIP will be compatible with a number of other ZIPs, and that it can be put into them.
Out of Scope for this Proposal
- This ZIP does not address these items of any particular Development Funding Proposal:
- The merits.
- The motivations.
- The terms.
- Requirements and implementation.
Motivation and Requirements
This ZIP is supplemental to any Development Funding Proposal that puts conditions, or claims to put conditions, on these items:
- How the Electric Coin Company (ECC) and the Zcash Foundation (ZF) use development funds.
- How the ECC and the ZF do other related off-chain actions, for example requirements and Covenants.
For example, ZIP 1006 [zip-1006] contains this text:
“[f]unds accruing to the Zcash Development Fund MUST be used only for ... technical work directly connected to the various software implementations of the Zcash protocol.”
But after development funding is approved and implemented through a network upgrade, this item will not exist: an enforcement mechanism to make sure that the ZF and the ECC obey this requirement.
The aim of this ZIP is to supply such an enforcement mechanism. If this ZIP is adopted, the ECC, the ZF or both (as applicable) must make a legal agreement that contains this right: ZEC holders have the right to enforce the performance of any Covenants by the ECC or the ZF.
In this ZIP, the name of this legal agreement is the “DevFund Charter”, or the “Charter” for short. But the legal agreement can also have a different style of name. Examples are:
- A Constitution.
- Bylaws.
- A Fund Governance Agreement.
- Other names.
On this page, a “ZEC threshold” is one of these shares of ZEC:
- A plurality of ZEC.
- A majority of ZEC.
- A supermajority of ZEC.
We recommend that the DevFund Charter is used for the benefit of all ZEC users. But the DevFund Charter can include this condition: an enforcement action is possible only with the support of the holders of a ZEC threshold.
In the calculation of the necessary ZEC threshold, we recommend that the ZEC of these holders is excluded from the denominator:
- The ZF.
- The ECC.
- The officers of the ZF and the ECC.
- The directors of the ZF and the ECC.
- The employees of the ZF and the ECC.
- The affiliates of the ZF and the ECC.
Note from the ZIP Editors: In a vote, a “plurality” is the option that got more votes than any other single option. But it is not clear how this meaning applies to “a plurality of ZEC”.
Note from the ZIP Editors, continued: Other cryptocurrencies have experience with stake-weighted voting. Consider this threshold for an enforcement action: votes from a simple majority (50%), or more, of all issued ZEC. From this experience, this threshold seems to be an extremely high bar.
Consider a quorum of representatives from a number of groups that are specified in the DevFund Charter. The number of representatives is not yet decided. This quorum can state that the support of the assigned representatives of each group is necessary for an enforcement action.
We recommend that ZEC balance is one such mechanism. But with this mechanism, a 66% majority or an 85% supermajority is necessary. (These numbers have no binding effect. They are open for discussion.)
This recommendation is an assumption: we recommend that these parties identify their vote or signal:
- The Electric Coin Company.
- The Zcash Foundation.
- A party with a direct conflict of interest.
Such a vote or signal can be rejected from the vote.
Legal enforcement can occur in one of these:
- A court of law.
- Non-binding mediation.
- Binding arbitration.
The DevFund Charter can also contain rights for other constituencies of the Zcash community. Examples are specified miners, or the “Third Entity” of ZIP 1006 [zip-1006].
Rationale
ZEC holders do not have specific legal rights against the ECC or the ZF. But ZEC holders can want to put a condition on renewed on-chain development funding. The condition is that the ECC or the ZF agrees to use the development funds in specified ways. For these reasons, we recommend that ZEC holders have the legal right to enforce the compliance of the ECC or the ZF with those agreements.
Specification
-
Two requirements apply if all these conditions are true:
- A Development Funding Proposal has sufficient community support.
- That proposal has a requirement for specified Covenants from the ECC or the ZF.
- There is also sufficient community support to use this enforcement mechanism for that proposal.
In that case, one or more attorneys must be engaged to write a draft of a Charter that contains those Covenants.
In that case also, the Charter must become legally effective and binding when the other aspects of the Development Funding Proposal are implemented on-chain. (An example: a network upgrade is necessary to implement the Development Funding Proposal. Then the Charter becomes effective and binding at the activation of the corresponding network upgrade.)
-
We recommend this amendment to each pending Development Funding Proposal: a specific description of any Covenants that are necessary for these parties to agree to as part of that proposal:
- The ECC.
- The ZF.
- Any other applicable person or entity.
Open Issues
- The ZEC threshold that is necessary to approve an enforcement action against the ECC or the ZF.
- The logistics and the technical implementation of the Charter, for example on-chain signaling or voting for enforcement.
- The remedies under the Charter, for example “specific performance”. (With specific performance, a court orders the ZF or the ECC to obey a Covenant.)
- The discontinuation or the decrease of development funding. (This can occur through Covenants of this type: the ZF or the ECC will prepare a network upgrade to stop or decrease development funding if holders of the necessary ZEC threshold request it.)
- Other items.
Raised Concerns
-
“Code is Law; This is Just Law!”
- Objection: To depend on off-chain legal mechanisms is contrary to the cypherpunk ethos, to the mission or ethos of Zcash, or to both.
- Answer: This is a values judgment. Some people possibly have this opinion for good reasons. But also consider these points:
- The principle “don’t trust, verify” is also a cypherpunk principle.
- Some requirements are off-chain. Thus at this time, a code-based solution is not possible.
-
“Social Coordination Impracticality/Risk”
- Objection: ZEC holders put a high value on anonymity. But for the legal enforcement of breached Covenants, social coordination will be necessary. (People must agree to enforce the action. Someone must actually get a lawyer and go to court.) Thus this mechanism will not be valuable to ZEC holders. ZEC holders can compromise their anonymity because of it. Thus the mechanism can be worse than useless.
- Answer: We recommend that the community discusses a further question: in practice, how can ZEC holders securely coordinate to bring an enforcement action against the ECC and the ZF? (This applies if an enforcement action becomes necessary.) Also, consider this point: with the clear terms of a Charter, legal enforcement is possible. Because of this possibility alone, the ECC and the ZF possibly decide not to violate Covenants. Thus, paradoxically, a Charter can also be the reason that legal action never becomes necessary.
Also, some jurisdictions have the “class action” legal structure. With this structure, the community of ZEC holders possibly can find a ‘champion’ in the form of a class-action attorney. Then it is not necessary for ZEC holders to become personally involved or to ‘out themselves’ as ZEC holders. (One willing ZEC holder as class representative is the exception.)
-
“This Will Just Waste Funding On Lawyers”
- Objection: This Charter will be novel and bespoke. Lawyers possibly charge high fees to write a draft of it and to give assurances that it is enforceable. This is a waste of money. Otherwise, this money can be spent on Zcash development.
- Answer: This is a valid concern. The Zcash community possibly can crowdsource an initial rough draft of the Charter. The draft can come from lawyers in the community. It can even come from non-lawyers who possibly agree to do research and try to write an initial draft. The primary task of the lawyers can be to issue-spot and to formalize the initial draft. The ECC and the ZF possibly have law firms on retainer that can do the work at favorable rates.
Lawyers possibly agree to work at discounted rates. The reason is the unique opportunity and the prestige of the development of this innovative governance mechanism for a block chain. Also, as a percentage of the total value at stake, any legal fees possibly are small. The value at stake possibly is considerable if a block reward of 5-20% for development funding is authorized.
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"
- [zip-1006]
- ZIP 1006: Development Fund of 10% to a 2-of-3 Multisig with Community-Involved Third Entity