This page is the Simplified Technical English version of ZIP 207. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 207: Funding Streams
ZIP: 207
Title: Funding Streams
Owners: Jack Grigg <thestr4d@gmail.com>
Daira-Emma Hopwood <daira@jacaranda.org>
Status: [Revision 0: Canopy, Revision 1: NU6, Revision 2: NU7] Final
Category: Consensus
Created: 2019-01-04
Last-Updated: 2026-10-13
License: MIT
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 "block subsidy" and "halving" have the same meaning as in sections 3.10 and 7.8 of the Zcash Protocol Specification. [protocol-subsidyconcepts] [protocol-subsidies]
In this document, the terms "consensus branch" and "network upgrade" have the same meaning as in ZIP 200. [zip-0200]
The terms below have these meanings:
- Canopy
- The code name for the fifth Zcash network upgrade. Another name for this network upgrade is Network Upgrade 4.
- Testnet
- The Zcash test network. Its definition is in the Zcash Protocol Specification. [protocol-networks]
- Mainnet
- The Zcash production network. Its definition is in the Zcash Protocol Specification. [protocol-networks]
Abstract
This ZIP contains the specification of a mechanism for funding streams. The funding streams are distributed from a part of the block subsidy for a specified range of block heights.
The intention is to implement the Zcash Development Fund with this mechanism and the funding stream definitions in ZIP 214 [zip-0214]. Read this ZIP together with ZIP 1014 [zip-1014]. ZIP 1014 contains the high-level requirements for that fund.
At NU7, the target block spacing decreases to 25 seconds. With Revision 2, the approximate duration and value of each address period stay the same.
Motivation
The motivation for the Zcash Development Fund is in ZIP 1014 [zip-1014].
This ZIP 207 was first proposed for the Blossom network upgrade. Its purpose then was to divide the original Founders’ Reward into some streams. Then the ZIP was withdrawn when that division was found to be unnecessary at the consensus level. The capabilities of the funding stream mechanism agree with the requirements for the Zcash Development Fund. Thus the ZIP was introduced again for that purpose in the Canopy network upgrade. The intention was to use these items again:
- the specification
- the analysis
- the implementation effort
From NU6, a part of the block subsidy is sent to a reserve, as specified in ZIP 1015 [zip-1015]. The distribution of this reserve will be specified in a future ZIP. This ZIP was changed as specified in ZIP 2001 [zip-2001]. In that change, a common mechanism to implement the ZIP 1015 proposal was added to the funding stream mechanism. ZIP 271 [zip-0271] contains the specification of a one-time disbursement from this reserve at NU6.1 activation. This disbursement is subtracted from the Deferred Development Fund Chain Value Pool Balance.
Requirements
The primary requirement of this ZIP is to supply a mechanism to specify funding streams. These funding streams are used in ZIP 214 [zip-0214] to implement the Zcash Development Fund. We recommend that the mechanism is sufficiently expressive for the three main "slices" that are defined in ZIP 1014 [zip-1014]:
- BP
- ZF
- MG
We recommend that the mechanism, with additional funding stream definitions, is also sufficiently expressive for the "direct grant option" in that ZIP.
As for the original Founders’ Reward, this ZIP has a mechanism to change the addresses for a given funding stream approximately each month. Thus the keys that are not yet necessary can be kept off-line as a security precaution.
Specification
Revisions
- Revision 0: This revision is the initial version of this specification. The Zcash community agreed on it in ZIP 1014 [zip-1014].
- Revision 1: In this revision, the Deferred Development Fund Chain Value Pool Balance is added as a possible recipient of funding stream outputs. The Zcash community agreed on this change in ZIP 1015 [zip-1015]. The change is specified in ZIP 2001 [zip-2001].
- Revision 2: In this revision, the remaining address period at NU7 activation and the later address periods become longer. The increase is in proportion to the change in target block spacing that is specified in ZIP 218 [zip-0218]. Also, in this revision a transparent P2PKH address is a valid recipient, as specified in ZIP 2008 [zip-2008].
Definitions
We use these constants and functions from [protocol-constants], [protocol-diffadjustment], and [protocol-subsidies]:
- \(\mathsf{BlossomActivationHeight}\)
- \(\mathsf{PostBlossomHalvingInterval}\)
- \(\mathsf{Halving}(\mathsf{height})\)
- \(\mathsf{BlockSubsidy}(\mathsf{height})\)
We also define this function:
- \(\mathsf{HeightForHalving}(\mathsf{halving})\): the smallest \(\mathsf{height}\) such that \(\mathsf{Halving}(\mathsf{height}) = \mathsf{halving}\)
Funding streams
The definition of a funding stream has these parts:
- a block subsidy fraction (represented as a numerator and a denominator)
- a start height (inclusive)
- an end height (exclusive)
- a sequence of recipients, as defined below
In this ZIP, the issuance is defined as a proportion of the total block subsidy, and not as absolute zatoshis. Thus this ZIP stays compatible with all changes to the target block spacing and to the issuance-per-block rates. For example, such a change occurred at the Blossom network upgrade. [zip-0208]
This is the definition of the value of a funding stream at a given block height:
\[ \mathsf{FundingStream[FUND].Value}(\mathsf{height}) = \mathsf{floor}\left( \frac{\mathsf{BlockSubsidy}(\mathsf{height}) \,\cdot\, \mathsf{FundingStream[FUND].ValueNumerator}}{\mathsf{FundingStream[FUND].ValueDenominator}} \right) \]
An active funding stream at a given block height is a funding stream that has this property: the block height is less than the end height of the stream, but not less than the start height of the stream.
The value of each funding stream is paid to one recipient from a set of recipients that is defined in advance. The recipient depends on the block height.
From Revision 0, each recipient must be the string encoding of a transparent P2SH address or Sapling address (as specified in [protocol-transparentaddrencoding] or [protocol-saplingpaymentaddrencoding]).
From Revision 1, each recipient identifier must be one of these items (the address encodings are as specified in [protocol-transparentaddrencoding] or [protocol-saplingpaymentaddrencoding]):
- the string encoding of a transparent P2SH address
- the string encoding of a Sapling address
- the identifier \(\mathsf{DEFERRED\_POOL}\)
The identifier \(\mathsf{DEFERRED\_POOL}\) was added in the NU6 network upgrade [zip-0253]. This identifier means that the value is paid to a reserve that is for development funding. The distribution of this reserve will be specified in a future ZIP.
From Revision 2, each recipient identifier must be one of these items (the address encodings are as specified in [protocol-transparentaddrencoding] or [protocol-saplingpaymentaddrencoding]):
- the string encoding of a transparent P2PKH or P2SH address
- the string encoding of a Sapling address
- the identifier \(\mathsf{DEFERRED\_POOL}\)
Each address is used for a maximum of 1/48th of a halving interval. The result is a sequence of funding periods of approximately one month each. This is the definition of the address to use for a given block height:
\[ \begin{array}{rcl} \mathsf{AddressChangeInterval} &=& \mathsf{PostBlossomHalvingInterval} / 48 \\ \mathsf{AddressPeriod}(\mathsf{height}) &=& \mathsf{floor}\left( {\small\frac{\mathsf{height} + \mathsf{PostBlossomHalvingInterval} - \mathsf{HeightForHalving}(1)}{\mathsf{AddressChangeInterval}}} \right) \\ \mathsf{FundingStream[FUND].AddressIndex}(\mathsf{height}) &=& \mathsf{AddressPeriod}(\mathsf{height}) - \\&&\hspace{2em} \mathsf{AddressPeriod}(\mathsf{FundingStream[FUND].StartHeight}) \\ \mathsf{FundingStream[FUND].Address}(\mathsf{height}) &=& \mathsf{FundingStream[FUND].Addresses[} \\&&\hspace{2em} \mathsf{FundingStream[FUND].AddressIndex}(\mathsf{height})\mathsf{]} \end{array} \]
As a result, the address in use changes on the same block height schedule for all active funding streams. This schedule is aligned to the height of the first halving. Thus 48 funding periods fit exactly in a halving interval. This property can be used to make an implementation simpler: the implementation batches the necessary outputs for each funding period.
The first index of the sequence \(\mathsf{FundingStream[FUND].Addresses}\) is 0. This sequence must have \(\mathsf{FundingStream[FUND].AddressIndex}(\mathsf{FundingStream[FUND].EndHeight} - 1) + 1\) entries. (In the protocol specification, the same sequence has the name \(\mathsf{fs.Recipients}\) and its first index is 1. [protocol-fundingstreams])
For a funding stream \(\mathsf{fs}\), at each block height, we write \(\mathsf{fs.Value}(\mathsf{height})\) for \(\mathsf{FundingStream[fs].Value}(\mathsf{height})\). We also write \(\mathsf{fs.Recipient}(\mathsf{height})\) for \(\mathsf{FundingStream[fs].Address}(\mathsf{height})\).
From Revision 2, the definition of \(\mathsf{AddressPeriod}\) above is replaced on each network by the piecewise definition that follows. This definition has these symbols:
- Let \(A\) be the NU7 activation height on that network.
- Let \(R = \mathsf{NU7PoWTargetSpacingRatio} = 3\) and \(\mathsf{IsNU7Activated}\) be as defined in ZIP 218 [zip-0218].
- Let \(C = \mathsf{AddressChangeInterval}\).
- Let \(I = \mathsf{PostBlossomHalvingInterval}\).
- Let \(H_1 = \mathsf{HeightForHalving}(1)\).
\[ \mathsf{AddressPeriod}(\mathsf{height}) = \begin{cases} \mathsf{floor}\left( \dfrac{\mathsf{height} + I - H_1}{C} \right), &\textsf{if not } \mathsf{IsNU7Activated}(\mathsf{height}) \\ \mathsf{floor}\left( \dfrac{R(A + I - H_1) + \mathsf{height} - A}{RC} \right), &\textsf{otherwise} \end{cases} \]
For funding streams that are active at or after NU7 activation, this definition must be used in the \(\mathsf{FundingStream[FUND].AddressIndex}\) and \(\mathsf{FundingStream[FUND].Address}\) calculations above. This includes the calculation of the period at the start height of a stream. As a result, the address index at activation stays the same.
If NU7 activation occurs part of the way through an address period, the remaining block count of that period is multiplied by three. Each later period has a length of 105000 blocks. Thus, at the target block spacing of 25 seconds, the wall-clock duration and the funding amount of each period stay approximately the same. Per-block rounding applies to these values.
(In the protocol specification [protocol-fundingstreams], this is expressed with \(\mathsf{PreNU7EquivalentHeight}(\mathsf{height})\). Assume that the blocks from NU7 activation onward are mined at the pre-NU7 target block spacing. Then this value is the height that the block at \(\mathsf{height}\) has. Its value is \(\mathsf{height}\) if not \(\mathsf{IsNU7Activated}(\mathsf{height})\), and \(A + (\mathsf{height} - A)/R\) otherwise. In \(\mathsf{FSRecipientPeriod}\) of the protocol specification, the pre-NU7 formula is applied to this rational number in the place of \(\mathsf{height}\). This is equal to the definition above when the numerator and the denominator of its second case are divided by \(R\).)
The table below is a visual representation of the alignment of stream addresses with funding periods:
| Example height | Stream A | Stream B | Stream C |
|---|---|---|---|
AddressChangeInterval - 2 | A0 | ||
AddressChangeInterval - 1 | A0 | ||
AddressChangeInterval | A1 | B0 | C0 |
AddressChangeInterval + 1 | A1 | B0 | C0 |
| ... | |||
2*AddressChangeInterval - 2 | A1 | B0 | C0 |
2*AddressChangeInterval - 1 | A1 | B0 | C0 |
2*AddressChangeInterval | A2 | C1 | |
2*AddressChangeInterval + 1 | A2 | C1 | |
| ... | |||
PostBlossomHalvingInterval - 2 | A2 | C1 | |
PostBlossomHalvingInterval - 1 | A2 | C1 | |
PostBlossomHalvingInterval | C2 | ||
PostBlossomHalvingInterval + 1 | C2 | ||
| ... | |||
PostBlossomHalvingInterval + AddressChangeInterval/2 | C2 | ||
| ... | |||
PostBlossomHalvingInterval + 2*AddressChangeInterval - 1 | C2 | ||
PostBlossomHalvingInterval + 2*AddressChangeInterval | C3 | ||
| ... | |||
PostBlossomHalvingInterval + 5*AddressChangeInterval - 1 | C3 | ||
PostBlossomHalvingInterval + 5*AddressChangeInterval | C4 |
The last rows are an example of Revision 2. In this example, NU7 activation occurs halfway through the period of address C2, at height PostBlossomHalvingInterval + AddressChangeInterval/2. The remaining half of that period is multiplied by three. The period of C3 has a length of 3*AddressChangeInterval blocks.
On Mainnet, Canopy activation occurred exactly when the Founders’ Reward expired, at block height 1046400. On Testnet, there was a shortened Founders’ Reward address period before Canopy activation.
Deferred Development Fund Chain Value Pool Balance
From Revision 1 of this specification, full node implementations must track an additional chain value pool balance, \(\mathsf{ChainValuePoolBalance^{Deferred}}\). This balance is in addition to the other chain value pool balances that are defined in [protocol-chainvaluepoolbalances] (refer also to ZIP 209 [zip-0209]).
Define \(\mathsf{totalDeferredOutput}(\mathsf{height}) := \sum_{\mathsf{fs} \in \mathsf{DeferredFundingStreams}(\mathsf{height})} \mathsf{fs.Value}(\mathsf{height})\). In this definition, \(\mathsf{DeferredFundingStreams}(\mathsf{height})\) is the set of funding streams with recipient identifier \(\mathsf{DEFERRED\_POOL}\) in the block at height \(\mathsf{height}\).
Define \(\mathsf{totalDeferredInput}(\mathsf{height})\) as in [protocol-subsidies]. It is \(\mathsf{ZIP271DisbursementAmount}\) at the height \(\mathsf{ZIP271ActivationHeight}\) of the one-time lockbox disbursement that is specified in ZIP 271 [zip-0271]. It is zero at all other heights.
For a given block chain, the \(\mathsf{ChainValuePoolBalance^{Deferred}}\) chain value pool balance is this value: the sum of the values of payments to \(\mathsf{DEFERRED\_POOL}\) for transactions in the block chain, minus the lockbox disbursement from it in that block chain.
An equivalent definition is as follows. For a block chain up to and including height \(\mathsf{height}\), \(\mathsf{ChainValuePoolBalance^{Deferred}}\) is equal to \(\sum_{\mathsf{h} = 0}^{\mathsf{height}} \left(\mathsf{totalDeferredOutput}(\mathsf{h}) - \mathsf{totalDeferredInput}(\mathsf{h})\right)\).
Note: \(\mathsf{totalDeferredOutput}(\mathsf{h})\) is always zero for heights \(\mathsf{h}\) before NU6 activation. \(\mathsf{totalDeferredInput}(\mathsf{h})\) is always zero for heights \(\mathsf{h}\) before NU6.1 activation.
Consensus rules
Before activation of the Canopy network upgrade, the existing consensus rule for payment of the original Founders’ Reward applies. [protocol-foundersreward]
From activation of the Canopy network upgrade:
- The existing consensus rule for payment of the Founders’ Reward [protocol-foundersreward] is no longer active. (Under the earlier consensus rules, this is true for Mainnet, but not for Testnet.)
- The coinbase transaction in each block must contain a minimum of one output of this type for each active funding stream: an output that is a payment of the stream's value in the prescribed way to the stream's recipient address for the block's height.
- The recipient \(\mathsf{fs.Recipient}(\mathsf{height})\) of a funding stream \(\mathsf{fs}\) at block height \(\mathsf{height}\) is as defined in Funding streams.
-
The "prescribed way" to pay a transparent P2SH address is to use a standard P2SH script of the form
OP_HASH160 RedeemScriptHash OP_EQUALas thescriptPubKey[Bitcoin-P2SH]. In this script,RedeemScriptHashis the 20-byte script hash in the raw encoding of the address [protocol-transparentaddrencoding].From Revision 2, the "prescribed way" to pay a transparent P2PKH address is to use
OP_DUP OP_HASH160 <keyHash> OP_EQUALVERIFY OP_CHECKSIGas the output'sscriptPubKey. In this script,<keyHash>is the direct push of the 20-byte public-key hash that is decoded from the recipient's Base58Check address. No other script encoding is valid for this funding-stream payment rule. - The "prescribed way" to pay a Sapling address is as defined in [zip-0213]. That is, the requirement that follows applies to all Sapling outputs in coinbase transactions (including, but not limited to, outputs for funding streams). Each of these outputs must have a valid note commitment when it is recovered with a 32-byte array of zeroes as the outgoing viewing key. In this case the note plaintext lead byte must be \(\mathbf{0x02}\), as specified in [zip-0212].
From activation of the NU6 network upgrade:
-
Rule 2 above is replaced by the rule that follows.
This rule applies to each block. In this rule, \(\mathsf{cb}\) is the coinbase transaction of the block and \(\mathsf{height}\) is its block height. In each block, the rule applies to each funding stream \(\mathsf{fs}\) that has these two properties:
- \(\mathsf{fs}\) is active at that block height.
- The recipient identifier given by \(\mathsf{fs.Recipient}(\mathsf{height})\) is other than \(\mathsf{DEFERRED\_POOL}\).
For each such funding stream, \(\mathsf{cb}\) must contain a minimum of one output that has all of these properties:
- The output is a payment of \(\mathsf{fs.Value}(\mathsf{height})\) zatoshi in the prescribed way to the address represented by that recipient identifier.
- The output is different from the outputs counted for every other such funding stream.
- The output is different from the outputs counted for the lockbox disbursement outputs that are necessary under ZIP 271 [zip-0271].
Note: The outputs that are necessary under rule 2 before NU6 activation are also different for each funding stream. In particular, one output cannot be counted for two active funding streams that have the same recipient and the same value.
Rule 5 was later clarified as follows:
- The "prescribed way" to pay a Sapling or Orchard address is as defined in [zip-0213]. The applicable consensus rules are the post-Heartwood consensus rules that are specified in [protocol-txnconsensus] for shielded outputs of coinbase transactions. A Sapling address is paid by a Sapling-pool output. Before NU6.3 activation, an Orchard address is paid by an Orchard-pool output. From NU6.3 activation onward, an Orchard address is paid by an Ironwood-pool output. The reason is that coinbase transactions can then contain no Orchard-pool component [zip-0213].
Note: The valid recipient identifiers above do not include Orchard addresses. The "prescribed way" to pay an Orchard address is defined in preparation for a future change. Up to and including NU7, no funding stream with a shielded payment address as a recipient was defined. That can change in the future. Thus we encourage implementations to support Sapling and Orchard addresses as recipients, as is valid under [zip-0213].
A copy of these rules is in [protocol-fundingstreams].
The definition of \(\mathsf{ChainValuePoolBalance^{Deferred}}\) above has two effects. For payments to the \(\mathsf{DEFERRED\_POOL}\), \(\mathsf{FundingStream[FUND].Value}(\mathsf{height})\) is added to \(\mathsf{ChainValuePoolBalance^{Deferred}}\) for the block chain that includes that block. For the lockbox disbursement specified in ZIP 271 [zip-0271], \(\mathsf{ZIP271DisbursementAmount}\) is subtracted from it.
For the funding stream definitions activated at these network upgrades, and for their changes at NU7, refer to ZIP 214 [zip-0214]:
- Canopy
- NU6
- NU6.1
In ZIPs that are related to later network upgrades, funding stream definitions can be:
- added
- changed
- deleted
The ZIP process [zip-0000] applies to these changes.
Deployment
This ZIP was first deployed with Canopy. [zip-0251]
The changes for deferred funding streams were deployed with NU6. [zip-0253]
Revision 2 was deployed with NU7, as specified in ZIP 259 [zip-0259].
Backward compatibility
By intention, the change in this ZIP is of the type known as a "bilateral consensus rule change". For this mechanism, it is necessary that all network participants upgrade their implementations to a compatible version in the upgrade window. Older implementations treat post-upgrade blocks as invalid. They follow any pre-upgrade consensus branch that continues.
Reference Implementation
Change History
2026-10-13
- We defined
fs.Valueandfs.Recipient. We added the requirement that each address list has entries for the full height range of its funding stream. - We clarified that a different output is necessary for each funding stream.
- We defined the "prescribed way" to pay any P2SH address. We applied the P2PKH payment rule of ZIP 2008 [zip-2008] to Revision 2.
- We clarified the "prescribed way" to pay an Orchard address from NU6.3. We also clarified that Orchard addresses are not valid recipients.
- We subtracted the ZIP 271 lockbox disbursement from the deferred development fund chain value pool balance.
- We corrected these items:
- the address-period example table
- the section numbers
- the reference titles
- the tense
- We added the reference implementation of Revision 2. We updated the protocol specification citations.
2026-09-30
- We applied ZIP 2008 [zip-2008] to Revision 2 of this ZIP.
2026-09-24
- We wrote a draft of Revision 2 for the NU7 address-period schedule.
2025-08-19
- We defined Revision 0 and Revision 1 explicitly.
2024-10-31
- We released Revision 1.
2024-09-26
- We applied ZIP 2001 [zip-2001] to this ZIP (as a result, Revision 1 was implicitly defined).
2020-05-30
- We released Revision 0 (the status changed from Draft to Proposed).
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-subsidyconcepts]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 3.10: Block Subsidy, Funding Streams, and Founders’ Reward
- [protocol-networks]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 3.12: Mainnet and Testnet
- [protocol-chainvaluepoolbalances]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 4.17: Chain Value Pool Balances
- [protocol-constants]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 5.3: Constants
- [protocol-transparentaddrencoding]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 5.6.1.1: Transparent Addresses
- [protocol-saplingpaymentaddrencoding]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 5.6.3.1: Sapling Payment Addresses
- [protocol-txnconsensus]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 7.1.2: Transaction Consensus Rules
- [protocol-diffadjustment]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 7.7.3: Difficulty adjustment
- [protocol-subsidies]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 7.8: Calculating Block Subsidy, Funding Streams, Lockbox Disbursement, and Founders’ Reward
- [protocol-foundersreward]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 7.9: Payment of Founders’ Reward
- [protocol-fundingstreams]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 7.10: Payment of Funding Streams, Deferred Lockbox, and Lockbox Disbursement
- [zip-0000]
- ZIP 0: ZIP Process
- [zip-0200]
- ZIP 200: Network Upgrade Mechanism
- [zip-0208]
- ZIP 208: Shorter Block Target Spacing
- [zip-0209]
- ZIP 209: Prohibit Out-of-Range Chain Value Pool Balances
- [zip-0212]
- ZIP 212: Allow Recipient to Derive Ephemeral Secret from Note Plaintext
- [zip-0213]
- ZIP 213: Shielded Coinbase
- [zip-0214]
- ZIP 214: Consensus rules for a Zcash Development Fund
- [zip-0218]
- ZIP 218: 25-second Block Target Spacing
- [zip-0251]
- ZIP 251: Deployment of the Canopy Network Upgrade
- [zip-0253]
- ZIP 253: Deployment of the NU6 Network Upgrade
- [zip-0259]
- ZIP 259: Deployment of the NU7 Network Upgrade
- [zip-0271]
- ZIP 271: Dev Fund Extension and One-Time Disbursement
- [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-2001]
- ZIP 2001: Lockbox Funding Streams
- [zip-2008]
- ZIP 2008: Update to FS_FPF_ZCG_H3 address list
- [Bitcoin-P2SH]
- Transactions: P2SH Scripts — Bitcoin Developer Guide
- [zebra-11529]
- Zebra PR 11529: feat(consensus)!: implement NU7 spacing, funding schedules, and shielded limits
- [zebra-11527]
- Zebra PR 11527: feat(nu7)!: prepare ZIP 259 deployment and ZIP 2008 payouts