ZIP: 1002
Title: Opt-in Donation Feature
Owners: mistfpga (zcash forums) <>
Status: Obsolete
Category: Consensus Process
Created: 2019-07-17
License: CC BY-SA 4.0 <>
Discussions-To: <>


The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as described in BCP 14 3 when, and only when, they appear in all capitals.

This ZIP defines these terms:

1 If there is contradiction between Spirit and any other part of the proposal that needs to be addressed, in the event it is not addressed Spirit is assumed to overrule all.

Out of Scope for this Proposal

Governance on how decisions are made. This ZIP is not meant to be used as a form of governance. It is a protocol-level opt-in for supporting the Zcash network development (like the Founders’ Reward, just with opt-out).

Signalling. Whilst a lot of the ZIP relies on the ability to signal intent in one way or another, it does not put forward such a mechanism and is designed to work with various form of signalling, or potentially without signalling at all.


The spirit of this ZIP is:


Technology changes, and it changes fast. What works now, may be easily breakable in 10 years, 20 years and certainly 50 years.

To help ensure ZEC can keep up with these changes, now and in 50 or 500 years' time, there needs to be a continual funding for research into new technology and financial stability in order to attract new talent.

The only source of indefinite wealth transfer is transaction fees or donations. This ZIP is specifically about voluntary donations (including via mining fees).


2 The Zcash Foundation has stated (later clarified in 4) that the Foundation would only support proposals that: a) don’t rely on the Foundation being a single gatekeeper of funds; b) don’t change the upper bound of ZEC supply; and c) have some kind of opt-in mechanism for choosing to disburse funds (from miners and/or users).


this proposal is being published as a ZIP for the purpose of discussion and for the Zcash Foundation's sentiment collection process, despite significant issues with lack of clarity in the above specification.

Raised objections and issues so far

Implications to other users

Technical implementation

Stuff that is already implemented in some form or another:


3 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"
4 Zcash Foundation Guidance on Dev Fund Proposals. Zcash Foundation blog, August 6, 2019.