This page is the Simplified Technical English version of ZIP 1016. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 1016: Community and Coinholder Funding Model
ZIP: 1016
Title: Community and Coinholder Funding Model
Owners: Josh Swihart <josh@electriccoin.co>
Credits: Daira-Emma Hopwood
Kris Nuttycombe
Jack Grigg
Tatyana Peacemonger
Alex Bornstein
Jason McGee
Status: Active
Category: Consensus Process
Created: 2025-02-19
License: MIT
Pull-Request: <https://github.com/zcash/zips/pull/989>
<https://github.com/zcash/zips/pull/994>
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.
In this document, the terms "Mainnet" and "Testnet" have the definitions in the Zcash protocol specification [protocol-networks].
In this document, these terms have the meanings that are described in ZIP 1014 [zip-1014]:
- "Electric Coin Company" (or "ECC")
- "Bootstrap Project" (or "BP")
- "Zcash Foundation" (or "ZF").
In this document, these terms have the definitions in ZIP 1015 [zip-1015]:
- "Zcash Community Grants" (or "ZCG")
- "ZCG Committee"
- "Financial Privacy Foundation" (or "FPF")
- "Deferred Dev Fund Lockbox".
"Shielded Labs" is the Association with that name. This Association is registered in the Swiss canton of Zug. Its Unique Identifier is CHE-243.302.798.
Protocol-defined Ecosystem Funding is the name for funds from sources that have their definition in the Zcash Protocol. These funds are for the development of the Zcash ecosystem. At the time of writing, Protocol-defined Ecosystem Funding is allocated from a part of the block rewards. The allocation is through Funding Streams [zip-0207] and Lockbox Funding Streams [zip-2001].
“ZEC” is the native currency of Zcash on Mainnet.
Abstract
This ZIP contains an outline of a funding model. In this model, the community and the coinholders have different voices. With these voices, they decide what grants, if any, are given to support Zcash development and community efforts.
In this model:
- 8% of the block rewards will be allocated to the ZCG for grants by and for the Zcash Community.
- 12% of the block rewards will go to a fund. Coinholders control this fund through their decisions. The Deferred Dev Fund Lockbox is the seed of this fund.
The Coinholder-Controlled Fund can be used to distribute larger grants to ecosystem participants, or it can stay at rest.
This model is active until the 3rd halving. This period is long enough to decide if the model is to be changed, or specified for a longer period.
Motivation
If no action is taken, then from November 2025 funds from block subsidies will not be directed to Zcash Community Grants [zip-1015-zcg]. Also, from that time, these funds will not be directed to the Deferred Dev Fund Lockbox. This lockbox was established by ZIP 2001 [zip-2001].
If the block subsidies stop, there will be a risk of a gap in the funding of Zcash development organisations. This funding comes through ZCG grants, or through possible future disbursements from the Deferred Dev Fund Lockbox.
The goals of this ZIP are as follows:
- To decentralize decision-making.
- To make stakeholders accountable for outcomes.
- To be dynamic enough to let changes occur.
- To make decision-making clear.
The immediate effects of this ZIP are as follows:
- The voice of coinholders increases.
- Confusion about governance decreases to a minimum.
- Decision-making becomes simpler.
Requirements
- There is a clearly defined process for the evaluation of grant proposals and for community feedback on them. This process has public agreement.
- Funds are held in a multisig. The multisig is resistant to the compromise of the keys of some of the parties, up to a given threshold.
- If a single party does not cooperate or loses its keys, no Protocol-defined Ecosystem Funding becomes locked with no possible recovery.
- During the period of this ZIP, the block rewards are distributed as described in the Abstract above.
- The funds from the 8% funding stream will be usable immediately on activation of this ZIP.
- The funds in the Deferred Dev Fund Lockbox will be usable immediately on activation of this ZIP.
- Each use of Deferred Dev Fund Lockbox funds is consistent with the purpose that is specified in [zip-1015-lockbox]: "funding grants to ecosystem participants".
Non-requirements
- Changes to the ZCG or to its governance can be desirable. An example is an expansion of the ZCG to include more members. But such changes are specifically outside the scope of this ZIP.
- Changes to Zcash protocol governance are outside the scope of this ZIP. Specifically, the governance of what changes are made to consensus node implementations is outside the scope of this ZIP.
Specification
Under this ZIP, two groups have power: the community (through ZCG) and the coinholders. Each group can independently decide what, if anything, is to be funded through development fund grants.
The funding streams in the sections below will be defined in a new revision of ZIP 214 [zip-0214].
Zcash Community Grants
A funding stream will be established for Zcash Community Grants. This funding stream consists of 8% of the block subsidy. It is subject to all of the same rules that are specified at this time in ZIP 1015 [zip-1015-zcg].
On Mainnet, this funding stream starts on expiry of the existing FS_FPF_ZCG funding stream [zip-1015-funding-streams]. With the pre-NU7 target block spacing, it continues for a further 1,260,000 blocks (approximately 3 years). It ends at block height 4406400, the third halving of Zcash.
If NU7 is activated before that height, the stream is extended by ZIP 214 Revision 3 [zip-0214]. The stream then ends at the revised third-halving height \(A + 3(4406400 - A)\). In this expression, \(A\) is the Mainnet NU7 activation height. The number 3 is the target block spacing ratio that is specified in ZIP 218 [zip-0218].
Coinholder-Controlled Fund
A new Coinholder-Controlled Fund is formed from a pool of multisig-controlled funds. The existing contents of the ZIP 1015 Deferred Dev Fund Lockbox [zip-1015-lockbox] are the seed of this pool. A funding stream that consists of 12% of the block subsidy is added to the pool. The time period of this funding stream is the same as the time period of the Zcash Community Grants stream.
The mechanisms for the creation and management of this fund are described in the Deferred Dev Fund Lockbox Disbursement proposal [zip-271]. In this ZIP, the value of the \(\mathsf{stream\_value}\) parameter of that proposal is 12%. The value of the original \(\mathsf{stream\_end\_height}\) parameter is Mainnet block height 4406400.
If NU7 is activated before that height, the end height of both streams is adjusted to the revised third halving. This adjustment is in ZIP 214 Revision 3 [zip-0214].
Requirements on use of the Coinholder-Controlled Fund
The Key-Holder Organizations must be bound by a legal agreement to use funds in the Coinholder-Controlled Fund only according to the specifications in this ZIP. In this agreement, these specifications must be expressed in suitable legal language. In particular, all the requirements in ZIP 1015 [zip-1015-lockbox] on the use of Deferred Dev Fund Lockbox funds must be followed for the Coinholder-Controlled Fund.
The Key-Holder Organizations administer the Coinholder-Controlled Fund together. They do this according to the decisions of coinholder voting. The community decides the model for this voting. This model is specified in another ZIP [TBD].
Disbursement process
- Anyone can send a grant application through a process that the Key-Holder Organizations agree on.
- Coinholders will vote on grant applications every three months. Grant applications must be sent for community review 30 days before coinholder voting.
- This step is for a grant application that is not vetoed and is put to a coinholder vote under the agreed process. Coinholders will be asked to vote on that application.
- If the vote passes, then (subject to the Veto process) we recommend that the Key-Holder Organizations sign a disbursement transaction from the Coinholder-Controlled Fund as each grant payment is scheduled.
For the approval of a grant proposal, a coinholder vote must have these two properties:
- A minimum of 420,000 ZEC (2% of the total eventual supply) is voted.
- A simple majority is cast in favor.
After approval, the grants are paid to the recipient according to the terms of the grant proposal.
If two or more grant proposals that are sent are in competition with one another, a single winner will be selected. For this selection, there will be a separate coinholder vote for each proposal. Of the approved proposals, the winner is the proposal with the highest total ZEC value committed in support. When the Key-Holder Organizations organize coinholder votes, it is their responsibility to decide if proposals are in competition with one another.
Each coinholder vote is independent. This is also true when two or more grants are in competition. Coins that are used in one vote can also be used in a different vote. This approach is necessary to prevent vote-splitting scenarios. In such a scenario, it is possible that an option is selected with only a plurality (not a majority) of coinholder support.
When coinholders decide about the funding of a grant, we recommend that they consider the same factors as the ZCG Committee. (These factors are described in points 2, 3, and 4 of [zip-1015-zcg].)
In these cases, we recommend that the Key-Holder Organizations hold additional coinholder votes to decide if funding is to continue:
- A contentious issue occurs in connection with a grant (for example, milestones that are not met).
- Periodically, for grants of indefinite duration.
Coinholders do not have an obligation to fund any grants. They can leave the funds at rest.
All organizations and individuals can vote their coins.
Veto process
A grant is vetoed if:
- a Key-Holder Organization declares that the funding of the grant is a violation of one or more of its legal or reporting obligations; or
- two or more Key-Holder Organizations declare a principled objection to the grant. The basis of the objection is possible harm to Zcash users, or that the grant is against the values of the Zcash community.
If a grant is vetoed after its approval in a coinholder vote, then payments for it must be stopped. This situation is expected to be unusual. It is expected to occur only in these cases:
- New negative information becomes known.
- There is a change in the law.
- There are unexpected legal proceedings.
If coinholders reject a proposal, the Key-Holder Organizations cannot veto this rejection.
Vetoes are intended for exceptional cases. We recommend that each veto is accompanied by a thorough rationale.
Administrative obligations and constraints
ZIP 1015 has provisions with obligations and constraints that relate to the previous FS_FPF_ZCG funding stream. These provisions apply to these parties:
- Bootstrap Project
- Electric Coin Company
- Zcash Foundation
- Financial Privacy Foundation
- the ZCG Committee
- grant recipients.
All of these provisions must continue in effect for Zcash Community Grants.
These obligations and constraints will be extended to all Key-Holder Organizations, for the Coinholder-Controlled Fund.
The provisions after the first paragraph of the section "Zcash Community Grants (ZCG)" also apply to the administration of the Coinholder-Controlled Fund by the Key-Holder Organizations. In this administration, coinholder voting has the role of the ZCG Committee.
Note: Developers of Zcash consensus node implementations have no obligation to implement any particular ZIP. The only aim of a process specification such as this one is to show social consensus. Fundamentally, such a specification cannot have an effect on the autonomy of these persons:
- Developers of Zcash consensus node implementations. They can publish (or not publish) the implementations that they want to publish.
- Node operators. They can run (or not run) the implementations that they want to run.
Security precautions
The Key-Holder Organizations and the ZCG Committee must take applicable precautions to keep funds safe from theft or accidental loss.
These events must be reported to the Zcash community as quickly as possible, after the necessary mitigations are applied:
- Each theft or loss of funds.
- Each loss or compromise of key material.
Testnet-specific considerations
We recommend that this process is rehearsed on Testnet. The purpose of these rehearsals is to test the mechanism and the process for coinholder voting. The threshold of 420,000 ZEC for Mainnet coinholder votes does not apply to these rehearsals.
Open questions
- Is 420,000 ZEC the correct threshold for coinholder votes?
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"
- [protocol]
- Zcash Protocol Specification, Version 2025.6.0 [NU6.1 proposal] or later
- [protocol-networks]
- Zcash Protocol Specification, Version 2025.6.0 [NU6.1 proposal]. Section 3.12: Mainnet and Testnet
- [zip-0207]
- ZIP 207: Funding Streams
- [zip-0214]
- ZIP 214: Consensus rules for a Zcash Development Fund
- [zip-0218]
- ZIP 218: 25-second Block Target Spacing
- [zip-1014]
- ZIP 1014: Establishing a Dev Fund for ECC, ZF, and Major Grants
- [zip-1015]
- ZIP 1015: Block Subsidy Allocation for Non-Direct Development Funding
- [zip-1015-lockbox]
- ZIP 1015: Block Subsidy Allocation for Non-Direct Development Funding — Lockbox
- [zip-1015-zcg]
- ZIP 1015: Block Subsidy Allocation for Non-Direct Development Funding — Zcash Community Grants
- [zip-1015-funding-streams]
- ZIP 1015: Block Subsidy Allocation for Non-Direct Development Funding — Funding Streams
- [zip-271]
- ZIP 271: Deferred Dev Fund Lockbox Disbursement
- [zip-2001]
- ZIP 2001: Lockbox Funding Streams