Zcash in Simplified Technical English

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

ZIP 1013: Keep It Simple, Zcashers: 10% to ECC, 10% to ZF

ZIP: 1013
Title: Keep It Simple, Zcashers: 10% to ECC, 10% to ZF
Owners: Gordon Mohr (@gojomo on relevant forums)
Status: Obsolete
Category: Consensus Process
Created: 2019-11-14
License: Public Domain
Discussions-To: <https://forum.zcashcommunity.com/t/zip-keep-it-simple-zcashers-kisz-10-to-ecc-10-to-zfnd/35425>
Pull-Request: <https://github.com/zcash/zips/pull/293>

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.

These are the definitions of the terms in this ZIP:

ECC
The Electric Coin Company, a limited-liability corporation in the US.
ZF
The Zcash Foundation, a non-profit corporation in the US.
Halvening
A regularly scheduled discontinuity. At a Halvening, the rate of ZEC issuance decreases by half. The expected date of the first Halvening is approximately October 2020. The expected date of the next Halvening is approximately October 2024.

Abstract

This ZIP contains a proposal for these actions.

The "Founders’ Reward" is the protocol-based development funding for the bootstrap of the system. It expires at the 1st Zcash Halvening. After that Halvening, continue to send 20% of new ZEC issuance to activities that are related to development. These activities are for continued work on Zcash in these areas:

Give half of these funds to the ECC, and half to the ZF. Continue this allocation until the 2nd Halvening.

Motivation

There are many proposals for possible allocations of Zcash block rewards (ZEC inflation) after the 1st Halvening. Many of these proposals have similar broad parameters:

But no existing ZIP contains an explicit proposal for the simplest variation on this theme. That variation has the maximum continuity with previous practice. The purpose of this "Keep It Simple, Zcashers" ZIP is to fill that gap.

Requirements

The intention of this ZIP is that it is easy:

Non-requirements

This ZIP does not contain a proposal for a specific course of action after the 2nd Halvening.

Specification

To implement this ZIP, the Zcash protocol and compatible implementations must do these things:

Specifically, this ZIP contains no new conditions or procedural formalities on the delivery of development funds. This applies to technical and legal conditions and formalities.

There is only one expectation for these recipients. We recommend that they continue these items that they showed before this ZIP:

Discussion

The primary differences between this ZIP and similar proposals are these two:

  1. This ZIP has no new conditions or processes for the disbursement of ZEC development funds.
  2. This ZIP has a fixed 50-50 division of funds between the ECC and ZF.

The reason for these differences is a desire for simplicity and continuity. This allocation can be implemented technically without new items of these types:

The adequate performance of fund recipients is expected for the reasons that follow. The expectation does not depend on lists of conditions with underspecified mechanisms for enforcement or dispute resolution.

Approximately 15% of the development funds of the original "Founders’ Reward" period was directed to the ZF. (That is, approximately 3 points of the full 20 points of bootstrap funds.)

But the ZF started later. Recently, the ZF increased its capabilities in these areas:

Also, there is a wide sentiment in the Zcash community, the ECC and the ZF about the role of the ZF. This sentiment is a wish that the ZF grows to a role of equal or greater importance than the ECC for long-term Zcash evolution. Thus this ZIP has a 50:50 split of future development funds. This split is in the place of a continuation of any previous proportions.

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"