Zcash in Simplified Technical English

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

Motivation and Requirements

This ZIP is supplemental to any Development Funding Proposal that puts conditions, or claims to put conditions, on these items:

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:

On this page, a “ZEC threshold” is one of these shares 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:

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:

Such a vote or signal can be rejected from the vote.

Legal enforcement can occur in one of these:

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

Open Issues

Raised Concerns

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