Zcash in Simplified Technical English

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

ZIP 271: Dev Fund Extension and One-Time Disbursement

ZIP: 271
Title: Dev Fund Extension and One-Time Disbursement
Owners: Daira-Emma Hopwood <daira@jacaranda.org>
        Kris Nuttycombe <kris@nutty.land>
        Jack Grigg <thestr4d@gmail.com>
Status: Final
Category: Consensus / Process
Created: 2025-02-19
License: MIT
Pull-Request: <https://github.com/zcash/zips/pull/989>
              <https://github.com/zcash/zips/pull/1014>
              <https://github.com/zcash/zips/pull/1015>
              <https://github.com/zcash/zips/pull/1099>

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.

Abstract

This ZIP contains a proposal for an extension of protocol-based development funding. The proposal is in the context of multiple alternatives to distribute the funds that accrued to the Deferred Dev Fund Lockbox. The intention is that this ZIP is evaluated in the context of the Community And Coinholder Funding Model proposal [zip-1016].

At a high level, this ZIP contains these proposals:

Requirements

Specification

This ZIP contains a proposal to create a new Zcash Development Fund. The balance of this Fund is the sum of these two parts:

One-time lockbox disbursement

The coinbase transaction of the activation block of this ZIP must include one or more lockbox disbursement outputs to a 2-of-3 P2SH multisig. The keys of this multisig are held by these "Key-Holder Organizations":

  • Zcash Foundation
  • the Electric Coin Company
  • Shielded Labs

Let \(\mathsf{ZIP271ActivationHeight}\) be the activation height of NU6.1 on the applicable network (Mainnet or Testnet), as defined in [zip-0255].

Let \(\mathsf{ZIP271DisbursementAmount}\) be the zatoshi amount in the Deferred Dev Fund Lockbox at the end of the block before the activation height. (When that height is known, it is possible to predict \(\mathsf{ZIP271DisbursementAmount}\) in advance.)

Let \(\mathsf{ZIP271DisbursementChunks} = 10\).

Let \(\mathsf{ZIP271DisbursementAddress}\) be \(“\texttt{t3ev37Q2uL1sfTsiJQJiWJoFzQpDhmnUwYo}”\) on Mainnet and \(“\texttt{t2RnBRiqrN1nW4ecZs1Fj3WWjNdnSs4kiX8}”\) on Testnet.

The additional coinbase outputs must have these properties:

  • Their sum is \(\mathsf{ZIP271DisbursementAmount}\) zatoshi.
  • The sum is split into \(\mathsf{ZIP271DisbursementChunks}\) equal outputs.
  • Each output is to the address that is represented by \(\mathsf{ZIP271DisbursementAddress}\).
  • Each output has a standard P2MS script, as specified in ZIP 48 [zip-0048].

To fund the outputs, \(\mathsf{ZIP271DisbursementAmount}\) zatoshi are added to the transparent transaction value pool of the coinbase transaction. The same amount is subtracted from the balance of the Deferred Dev Fund Lockbox. This subtraction occurs before all other changes to the Deferred Dev Fund Lockbox balance in the transaction. At that point, the Deferred Dev Fund Lockbox balance must not become negative as a result of this subtraction.

Note: It is necessary to calculate the value \(\mathsf{ZIP271DisbursementAmount}\) in advance. Thus the value is known when node implementations do the applicable consensus check.

\(\mathsf{ZIP271DisbursementAmount}\) must be \(78750\_0000\_0000\) zatoshi on Testnet and on Mainnet. (That is 78,750 TAZ on Testnet and 78,750 ZEC on Mainnet.)

Non-normative note: This is the BIP 388 wallet policy [bip-0388] for the Mainnet \(\mathsf{ZIP271DisbursementAddress}\):

Wallet descriptor template: sh(sortedmulti(2,@0/**,@1/**,@2/**))
Key information vector:
[2efd03f5/48'/133'/0'/133000']xpub6ERFr6gbA9jHXGj9Qxebua1Fj78ADQJPMyFgP78rUz9kdr4kMMXjkbGQSk6GPD8aYsyPPDXUqftNbuW3jKcHPP1hBa1paPv9FNMLqCqWsNz
[281d1aeb/48'/133'/0'/133000']xpub6FNah9qMu1jMRQdsFXXYWfWXXMhsdP3KRAexTBnnMykskq7VWQGm4439zUwAxNPGVfi7nuL5UWhLwGrHmfnxvLFEx3coS2tjYrezDavvh3T
[e1c4c104/48'/133'/0'/133000']xpub6E2qmBdHpQu9yJ3HvYJ8p8FVYMEWG4a6St2Knd7vfQC9jm7gyWZdvxMo6FafcKvjxiSmd61NW2Mu7udKDbcA5DAVzVdNU6JPrY2uhtPXxE4

Rationale for using P2MS outputs

Rationale

It is possible that the key-holders want the grant-filling transactions to use transparent inputs or shielded inputs. Whatever they want, the one-time disbursement must go through a shielded pool at some point. The reason is that this ZIP has no proposal for a change to the consensus rules for the spendability of transparent coinbase outputs. Such a change is much too complex for the intended scope.

Thus, with P2MS (that is, P2SH multisig) outputs in consensus, it is necessary that the Key-Holder Organizations spend each chunk of the one-time disbursement completely into a shielded output. Probably, this spend is to a FROST address, to keep a consistent security position over the lockbox funds. Possibly, the Key-Holder Organizations also publish the viewing key, to keep visibility.

An alternative proposal is possible. That proposal can contain this requirement: the one-time disbursement is directly a shielded output to the FROST address. Then the Key-Holder Organizations can immediately start to disburse grants. (But the 100-block coinbase maturity is not a large burden.)

Instead, this ZIP has P2MS outputs, for two reasons:

  • With a shielded output, it is necessary that the miner (or mining pool) can create shielded coinbase outputs. Technically, that requirement is already in the consensus rules. But that requirement was never exercised before, because no Funding Stream was defined with a shielded address.
  • With a shielded output in the context of this ZIP, it is necessary to derive the FROST address a long time before NU activation. At the time of writing (May 2025), ZIP 312 has no specification of key generation. A link between the specification process for key generation and this ZIP is not desirable. By comparison, P2SH multisig addresses have a format and a generation process that are relatively stable and well understood.

The one-time disbursement is split into 10 P2MS outputs. Thus the Key-Holder Organizations have more flexibility: they can shield only part of the disbursement at a time.

Changes to the Zcash Protocol Specification

§ 4.17 ‘Chain Value Pool Balances’ [protocol-chainvaluepoolbalances]

Replace this text:

Define \(\mathsf{totalDeferredOutput}\) as in § 7.8 ‘Calculation of Block Subsidy, Funding Streams, and Founders’ Reward’.

Then, consistent with [ZIP-207], the deferred development fund chain value pool balance for a block chain up to and including height \(\mathsf{height}\) is given by \(\mathsf{ChainValuePoolBalance^{Deferred}}(\mathsf{height}) := \sum_{\mathsf{h} = 0}^{\mathsf{height}} \mathsf{totalDeferredOutput}(\mathsf{h})\).

Non-normative notes:

  • \(\mathsf{totalDeferredOutput}(\mathsf{h})\) is necessarily zero for heights \(\mathsf{h}\) prior to NU6 activation.
  • Currently there is no way to withdraw from the deferred development fund chain value pool, so there is no possibility of it going negative. Therefore, no consensus rule to prevent that eventuality is needed at this time.

Put this text in its place:

Define \(\mathsf{totalDeferredOutput}\) and \(\mathsf{totalDeferredInput}\) as in § 7.8.

Then, consistent with [ZIP-207], the deferred development fund chain value pool balance for a block chain up to and including height \(\mathsf{height}\) is given by:

\[\mathsf{ChainValuePoolBalance^{Deferred}}(\mathsf{height}) := \sum_{\mathsf{h} = 0}^{\mathsf{height}} \mathsf{totalDeferredOutput}(\mathsf{h}) - \mathsf{totalDeferredInput}(\mathsf{h})\]

Consensus rule: If the deferred development fund chain value pool balance would become negative in the block chain created as a result of accepting a block, then all nodes MUST reject the block as invalid.

Non-normative notes:

  • \(\mathsf{totalDeferredOutput}(\mathsf{h})\) is necessarily zero for heights \(\mathsf{h}\) prior to NU6 activation.
  • \(\mathsf{totalDeferredInput}(\mathsf{h})\) is necessarily zero for heights \(\mathsf{h}\) prior to NU6.1 activation.
§ 7.1.2 ‘Transaction Consensus Rules’ [protocol-txnconsensus]

Replace this text:

  • A transaction MUST NOT spend a transparent output of a coinbase transaction from a block less than 100 blocks prior to the spend. Note that transparent outputs of coinbase transactions include Founders’ Reward outputs and transparent funding stream outputs.

Put this text in its place:

  • A transaction MUST NOT spend a transparent output of a coinbase transaction from a block less than 100 blocks prior to the spend. Note that transparent outputs of coinbase transactions include Founders’ Reward outputs, transparent funding stream outputs [ZIP-207], and lockbox disbursement outputs [ZIP-271].
§ 7.8 ‘Calculation of Block Subsidy, Funding Streams, and Founders’ Reward’ [protocol-subsidies]

Change the section title to include "Lockbox Disbursement".

Add this definition:

Let \(\mathsf{ZIP271ActivationHeight}\) and \(\mathsf{ZIP271DisbursementAmount}\) be as defined in [ZIP-271].

Also add this definition:

\(\mathsf{totalDeferredInput}(\mathsf{height}) := \begin{cases} \mathsf{ZIP271DisbursementAmount},&\!\!\textsf{if } \mathsf{height} = \mathsf{ZIP271ActivationHeight} \\ 0,&\!\!\textsf{otherwise.} \end{cases}\)

In these two definitions, the source has \(\mathsf{ZIP217ActivationHeight}\). This page has the repaired name. Refer to Source errata.

§ 7.10 ‘Payment of Funding Streams’ [protocol-fundingstreams]

Change the section title to ‘Payment of Funding Streams, Deferred Lockbox, and Lockbox Disbursement’.

Add a new paragraph at the start of the section:

[ZIP-207] defines a consensus mechanism to require coinbase transactions to include funding stream outputs, intended to provide funds from issuance for Zcash development. [ZIP-2001] extended this mechanism to support directing funds from issuance into a reserve, the deferred development fund lockbox. [ZIP-271] defines a one-time disbursal of funds from this lockbox in order to support the Community And Coinholder Funding Model [ZIP-1016].

Add this definition:

Let \(\mathsf{ZIP271ActivationHeight}\), \(\mathsf{ZIP271DisbursementAmount}\), \(\mathsf{ZIP271DisbursementChunks}\), and \(\mathsf{ZIP271DisbursementAddress}\) be as defined for the relevant network (Mainnet or Testnet) in [ZIP-271].

Replace this text:

Consensus rule: [Canopy onward] In each block with coinbase transaction \(\mathsf{cb}\) at block height \(\mathsf{height}\), for each funding stream \(\mathsf{fs}\) active at that block height with a recipient identifier other than \(\mathsf{DeferredPool}\) given by \(\mathsf{fs.Recipient}(\mathsf{height})\), \(\mathsf{cb}\) MUST contain at least one output that pays \(\mathsf{fs.Value}(\mathsf{height})\) zatoshi in the prescribed way to the address represented by that recipient identifier.

  • The prescribed way to [...]

Put this text in its place:

Consensus rule: [Canopy onward] In each block with coinbase transaction \(\mathsf{cb}\) at block height \(\mathsf{height}\), \(\mathsf{cb}\) MUST contain at least the given number of distinct outputs for each of the following:

  • for each funding stream \(\mathsf{fs}\) active at that block height with a recipient identifier other than \(\mathsf{DeferredPool}\) given by \(\mathsf{fs.Recipient}(\mathsf{height})\), one output that pays \(\mathsf{fs.Value}(\mathsf{height})\) zatoshi in the prescribed way to the address represented by that recipient identifier.
  • [NU6.1 onward] if the block height is \(\mathsf{ZIP271ActivationHeight}\), \(\mathsf{ZIP271DisbursementChunks}\) equal outputs paying a total of \(\mathsf{ZIP271DisbursementAmount}\) zatoshi in the prescribed way to the Key-Holder Organizations’ P2SH multisig address represented by \(\mathsf{ZIP271DisbursementAddress}\), as specified by [ZIP-271].

The term “prescribed way” is defined as follows:

  • The prescribed way to [...]

Change the reference to the definition of standard redeem script hashes for P2SH multisig addresses. The old reference is the "Pay To Script Hash (P2SH) — Multisig" section of the Bitcoin Developer Documentation [Bitcoin-Multisig]. The new reference is ZIP 48 [zip-0048]. (This change is a clarification. The intention is not to change the redeem scripts for existing P2SH addresses that are defined by consensus before NU6.1.)

Change the second bullet point that contains the definition of the prescribed way to pay a Sapling payment address. The changed bullet point also applies to Orchard. This is the new text:

  • The prescribed way to pay a Sapling or Orchard payment address is defined in [ZIP-213], using the post-Heartwood consensus rules specified for Sapling and Orchard outputs of coinbase transactions in § 7.1.2 ‘Transaction Consensus Rules’ [protocol-txnconsensus].

Clarify the notes. This is the clarified text:

  • The funding stream addresses are not treated specially in any other way, and there can be other outputs to them, in coinbase transactions or otherwise. In particular, it is valid for a coinbase transaction to have other outputs, possibly to the same address, that do not meet the criterion in the above consensus rule, as long as there is at least the given number of distinct outputs that meet it, disjointly for each funding item.
  • For clarification, if there are multiple active funding streams or lockbox disbursements with the same recipient identifier and/or value, there MUST be at least the given number of distinct outputs for each of them.
  • Up to and including NU6.1 there have been no funding streams or lockbox disbursements defined with a shielded payment address as a recipient. That might change in future, so implementations are encouraged to support Sapling and Orchard outputs as recipients, as permitted by [ZIP-213] and [ZIP-207].
§ 7.10.1 ‘ZIP 214 Funding Streams’ [protocol-zip214fundingstreams]

Add the Mainnet and Testnet funding streams from Revision 2 of ZIP 214 [zip-0214-funding-streams] to this section.

Extension to the lockbox funding stream

FS_CCF_H3 is the continuation of the 12% lockbox funding stream, as defined in ZIP 214 Revision 2 [zip-0214-funding-streams]. Under the pre-NU7 block spacing, the stream has these block heights:

  • Mainnet: heights 3146400 through 4406399 (1,260,000 blocks).
  • Testnet: heights 3536500 through 4475999 (939,500 blocks).

If NU7 activates before the applicable end height, the stream continues to the revised third-halving height on that network. This extension is in ZIP 214 Revision 3. This height is calculated with ZIP 218 [zip-0218].

Rationale for lockbox extension

Rationale

With a one-time disbursement to a P2SH multisig address, a source of grant funding is available for a limited period. During that period, there is time to specify and deploy a lockbox disbursement mechanism. ZIP 1015 [zip-1015] had this intention originally.

Specifically, there is an opportunity to include in the v6 transaction format [zip-0230] the transaction format changes that can be necessary for such a mechanism. It is desirable to limit the frequency of transaction format changes, because such changes are disruptive to the ecosystem. It is not necessary to implement the protocol rules for disbursement before the transaction format changes are live on the network. To prevent such disruption, we recommend that the upcoming v6 transaction format includes any such transaction format changes.

We implement a one-time disbursement together with a continuation of the FS_DEFERRED stream. Thus we give priority to two items:

  • The availability of grant funding.
  • The implementation of a more flexible and more secure mechanism for disbursement from the lockbox.

With such a mechanism, it is possible to rotate keys, or to change the set of key-holders, or both, when this is necessary. With a return to hard-coded output addresses for repeated disbursements, this is not possible.

Privacy and Security Implications

Development funding is a public good on the Zcash network. Thus this ZIP has no applicable privacy concerns. All disbursement of development funds is intentionally transparent, and any participant in the network can audit it. (This is not necessarily true for the later distribution of the funds.)

Security implications of the One-Time Lockbox Disbursement

After the activation block of this ZIP is mined, a 2-of-3 multisig address holds all the development funds that accrued earlier to the in-protocol lockbox. The lockbox does not hold these funds after that. The key-holders for this address have the capability to spend these funds. If 2 of these 3 keys are compromised or lost, all the funds are lost. Thus, if a single key is compromised or lost, the key-holders must establish a new multisig key set and address. They must also transfer the remaining unspent funds of the original address before more loss or compromise occurs.

This disbursement occurs one time only. Thus, additional infrastructure for key rotation is not necessary.

Security implications for extension of the lockbox funding stream

Funds continue to accrue securely to the Deferred Development Lockbox until a disbursement mechanism for the lockbox is implemented in a future network upgrade. We recommend that the design of such a disbursement mechanism includes an in-protocol option for key rotation. With this option, a network upgrade is not necessary for these operations:

  • Recovery from key loss or key compromise.
  • A change to the size of the signing set.
  • A change to the number of signatures that is necessary to reach the threshold.

Previously considered alternatives

These two variables were defined for use in this ZIP:

\(\mathsf{stream\_value}\)
The percentage of the block subsidy to send to a new funding stream. Refer to the options below.
\(\mathsf{stream\_end\_height}\)
The end block height of that stream.

Option 1: Extend the lockbox funding stream

This option was selected. Earlier, the section Extension to the lockbox funding stream had the name "Option 1" of this ZIP. In ZIP 1016 [zip-1016], the \(\mathsf{stream\_value}\) parameter was set to 12%. In ZIP 1016, the \(\mathsf{stream\_end\_height}\) parameter was set to Mainnet block height 4406400. This height is equal to the end height of the Zcash Community Grants stream. Thus, under the pre-NU7 block spacing, both streams end at the 3rd halving of Zcash.

In ZIP 214 Revision 3 [zip-0214], the end height changes to the revised third halving if NU7 activates before the original end height.

Option 2: Revert to hard-coded output address

A new funding stream is defined. It consists of \(\mathsf{stream\_value}\%\) of the block subsidy. It starts when the existing ZIP 1015 funding streams [zip-1015-funding-streams] end. The funds of the new streams go to a 3-of-5 P2SH multisig. The keys of this multisig are held by the same Key-Holder Organizations as above.

The resulting Fund is considered to include this stream of funds and also the funds from the one-time lockbox disbursement above.

Option 2 is possible with either of these two mechanisms:

Mechanism 2a: Classic funding stream

A new funding stream is defined. In each block, a payment from this stream goes directly to the 3-of-5 multisig address above. The stream starts at the end height of the existing FS_DEFERRED funding stream. It ends at \(\mathsf{stream\_end\_height}\). It consists of \(\mathsf{stream\_value}\%\) of the block subsidy.

Mechanism 2b: Periodic lockbox disbursement

The constant parameter is \(N = 35000\) blocks \(= \mathsf{PostBlossomHalvingInterval}/48\). (That is, approximately one month of blocks.)

The FS_DEFERRED lockbox funding stream is extended to end at height \(\mathsf{stream\_end\_height}\). Its output value for each block is set to \(\mathsf{stream\_value}\%\).

A consensus rule is added for disbursements from the Deferred Dev Fund Lockbox to a 2-of-3 P2SH multisig. The keys of this multisig are held by the same Key-Holder Organizations as above. The first disbursement is at block height \(\mathsf{activation\_height} + N\). Then there is one disbursement at each interval of \(N\) blocks, until \(\mathsf{stream\_end\_height}\). After each disbursement, the lockbox is empty.

This is equivalent to the specification of \(\frac{\mathstrut\mathsf{stream\_end\_height} \,-\, \mathsf{activation\_height}}{N}\) one-time lockbox disbursements (refer to One-time lockbox disbursement). All these disbursements have the same output address.

Rationale for periodic disbursement
Rationale

Classic funding streams [zip-0207] have many small output values. The cause is that each output can contain funds from the subsidy of only one block. As a result, the use of the funds has operational burdens. Specifically, the number of outputs that can be combined at one time has a limit, because of block sizes and transaction sizes. Thus more transactions are necessary. As a result, the overall fee increases.

With the periodic lockbox disbursement mechanism, the effective funding stream can be the same, but the aggregation occurs at no cost. At each interval of \(N\) blocks, the output to the funding stream recipient is aggregated into larger outputs. For Mechanism 2b, approximately 40 outputs go to the recipient multisig address, instead of approximately 1,300,000.

Security implications for Mechanism 2a

From the activation height of this ZIP, development funds start to accrue in each block as additional outputs. These outputs are spendable by a 2-of-3 multisig address. To shield the resulting coinbase outputs, it is necessary that the key-holders do regular multiparty signing ceremonies. In each such signing ceremony, shared spending authority is used to sign thousands of inputs to large shielding transactions. For practical reasons, this work is often done with a scripted process that has spending authority over these funds.

This process is an attractive target for compromise. Thus we recommend that address rotation is implemented, as was done for the ECC funding stream that is described in ZIP 1014 [zip-1014]. (In this case, the means of address rotation is a hard-coded sequence of addresses. Each address is the destination of a time-bounded subset of the fractional outputs of the block reward.)

If a key is compromised or lost, an emergency network upgrade can be necessary to do a manual key rotation. The purpose of this rotation is to make sure that future development funds are not lost.

Security implications for Mechanism 2b

Option 2b has a recommendation for an aggregation of funds. Because of this aggregation, scripts with spending privileges are no longer necessary for shielding operations, distribution operations, or both. Instead, human operators can do these operations with an interactive protocol. With this protocol, it is not necessary to share spending key material.

As with Option 2a, if a key is compromised or lost, an emergency network upgrade is necessary to do a manual key rotation. The purpose of this rotation is to decrease the risk of a loss of funds.

Deployment

This ZIP is deployed with the NU6.1 network upgrade. [zip-0255]

Reference implementation

Source errata

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-chainvaluepoolbalances]
Zcash Protocol Specification, Version 2025.6.0 [NU6.1 proposal]. Section 4.17: Chain Value Pool Balances
[protocol-txnconsensus]
Zcash Protocol Specification, Version 2025.6.0 [NU6.1 proposal]. Section 7.1.2: Transaction Consensus Rules
[protocol-subsidies]
Zcash Protocol Specification, Version 2025.6.0 [NU6.1 proposal]. Section 7.8: Calculating Block Subsidy, Funding Streams, Lockbox Disbursement, and Founders’ Reward (section title as modified)
[protocol-fundingstreams]
Zcash Protocol Specification, Version 2025.6.0 [NU6.1 proposal]. Section 7.10: Payment of Funding Streams, Deferred Lockbox, and Lockbox Disbursements (section title as modified)
[protocol-zip214fundingstreams]
Zcash Protocol Specification, Version 2025.6.0 [NU6.1 proposal]. Section 7.10.1: ZIP 214 Funding Streams
[zip-0048]
ZIP 48: Transparent Multisig Wallets
[zip-0207]
ZIP 207: Funding Streams
[zip-0207-consensus-rules]
ZIP 207: Funding Streams — Consensus Rules
[zip-0214]
ZIP 214: Consensus rules for a Zcash Development Fund
[zip-0214-funding-streams]
ZIP 214: Consensus rules for a Zcash Development Fund — Funding Streams
[zip-0218]
ZIP 218: 25-second Block Target Spacing
[zip-0230]
ZIP 230: Version 6 Transaction Format
[zip-0255]
ZIP 255: Deployment of the NU6.1 Network Upgrade
[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-funding-streams]
ZIP 1015: Block Subsidy Allocation for Non-Direct Development Funding — Funding Streams
[zip-1016]
ZIP 1016: Community and Coinholder Funding Model
[bip-0388]
BIP 388: Wallet Policies for Descriptor Wallets
[Bitcoin-Multisig]
Bitcoin Developer Documentation — Pay To Script Hash (P2SH) — Multisig