Zcash in Simplified Technical English

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

ZIP 237: Network Sustainability Mechanism: Halving-Preserving Issuance

ZIP: 237
Title: Network Sustainability Mechanism: Halving-Preserving Issuance
Owners: Judah Caruso <judah@shieldedlabs.net>
Original-Authors: Nathan Wilcox
                  Jason McGee
                  Zooko Wilcox
                  Mark Henderson
                  Tomek Piotrowski
                  Mariusz Pilarek
                  Paul Dann
Credits: Conrado Gouvea
Status: Final
Category: Consensus
Created: 2026-08-19
License: BSD-2-Clause
Discussions-To: <https://github.com/zcash/zips/issues/1353>
Pull-Request: <https://github.com/zcash/zips/pull/1354>

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.

The term "network upgrade" in this document has the meaning in ZIP 200 [zip-0200].

The character § is the mark for a section of the Zcash Protocol Specification [protocol].

The terms "Mainnet" and "Testnet" have the meaning in § 3.12 ‘Mainnet and Testnet’ [protocol-networks].

The symbol "\(\,\cdot\,\)" is multiplication. \(\mathsf{floor}(x)\) is the largest integer \(\leq x\). \(\mathsf{ceiling}(x)\) is the smallest integer \(\geq x\). These symbols have the meaning in § 2 ‘Notation’ [protocol-notation].

"ZEC/TAZ" is the native currency of Zcash on a given network. That is, it is ZEC on Mainnet and TAZ on Testnet.

\(\mathsf{PostBlossomHalvingInterval}\) has the definition in [protocol-diffadjustment]. \(\mathsf{PostNU7HalvingInterval}\) has the definition in ZIP 218 [zip-0218].

\(\mathsf{MAX\_MONEY}\) is the total ZEC/TAZ supply cap in zatoshi, as defined in § 5.3 ‘Constants’ [protocol-constants]. This value is equal to 21,000,000 ZEC. It is slightly larger than the supply cap for the current issuance mechanism. But it is the value used in existing critical consensus checks.

Issued Supply
The Issued Supply at a given height of a block chain is the total ZEC/TAZ value in all chain value pool balances at that height. This value is calculated by \(\mathsf{IssuedSupply}(\mathsf{height})\), as defined in § 4.17 ‘Chain Value Pool Balances’ [protocol-chainvaluepoolbalances].
Scheduled Block Subsidy
The block subsidy in the existing halving schedule. That is, it is \(\mathsf{BlockSubsidy}(\mathsf{height})\) as defined in § 7.8 ‘Calculating Block Subsidy, Funding Streams, Lockbox Disbursement, and Founders' Reward’ [protocol-subsidies] before this ZIP. In the Specification below, its new name is \(\mathsf{ScheduledBlockSubsidy}(\mathsf{height})\).
NSM Value Balance
The total ZEC/TAZ that was removed from circulation and that is not reissued yet. This total has two parts. The first part is the funds removed through a registered mechanism. The second part is the block subsidy and fees left unclaimed by coinbase transactions before NU6 [zip-0236]. The NSM Value Balance is not part of the Issued Supply. \(\mathsf{NSMValueBalance}(\mathsf{height})\) has its definition in the Specification below.

Abstract

This ZIP contains a change to the method that nodes use to calculate the block subsidy.

The step function around the 4-year halving intervals stays the same. This step function was inherited from Bitcoin. In addition, from the NSM reissuance height onward, a fixed part of the current NSM Value Balance is issued in each block. (The NSM Value Balance is the ZEC/TAZ that was removed from circulation or left unclaimed.) As a result, these funds are reissued along a smooth curve on top of the existing schedule.

When the NSM Value Balance is zero, the new issuance scheme is identical to the existing schedule. Total issuance is never greater than the existing supply cap. (This cap is less than \(\mathsf{MAX\_MONEY}\).) But total issuance is slightly less than this cap. The cause is that the shortfall from the rounding of the post-NU7 block subsidy is not reissued by the NSM [zip-0218-issuance-curve].

At NU7, the balance starts with historical unclaimed value. Thus the balance is positive at activation, also if no funds are removed by a deployed removal mechanism. This ZIP is an alternative to ZIP 234 [zip-0234]. The structure and much of the text of this ZIP are adapted from ZIP 234.

Motivation

The current block reward halving schedule is fixed. It has no method to “recycle” funds removed from circulation into future issuance. (Examples of removal are removal through ZIP 235 or ZIP 233.) When scheduled issuance ends, the network depends on transaction fees for the security budget.

Key Objectives:

  1. We want to introduce an automated mechanism. With this mechanism, users of the network can contribute to the long-term sustainability of the network.
  2. We want to make it possible that ZEC removed from circulation is reissued in the future. This reissuance is for the benefit of network sustainability.
  3. We want to keep the existing ZEC supply cap of 21 million as an upper bound on issuance.
  4. We want the issuance rate to stay identical to the historical rate for Zcash (and before that, Bitcoin) when the NSM Value Balance is zero. This includes the 4-year halving structure.
  5. We want issuance to be easy for all network users to understand and predict.
  6. We want to keep the existing 4-year halving schedule of Zcash.

This ZIP is an alternative to ZIP 234 [zip-0234]. The two ZIPs are different only in Key Objective 6. In ZIP 234, the halving schedule is replaced with a smooth curve to reissue funds removed from circulation. This ZIP is a demonstration that this change is not necessary for reissuance.

The halving schedule is a long-standing and widely understood property of Zcash. Block subsidy recipients and the wider community depend on it. With this ZIP, the question of a change to the halving schedule can be decided on its own merits.

With this NSM-based issuance scheme, these items stay the same:

Most importantly, this scheme contains the intended path for two types of funds:

These funds are reissued automatically and algorithmically over future block subsidies. As a result, these funds are for the benefit of the long-term security of the network.

Privacy Implications

The NSM Value Balance and the additional block subsidy are calculated from values that are already public:

With these calculations, no additional transaction information becomes known.

Requirements

It is possible to reissue funds removed from circulation and also keep the halvings. The method is an exponential decay formula, applied to the NSM Value Balance. The formula satisfies these requirements:

  1. A reasonably simple explanation of the issuance is possible.
  2. If the NSM Value Balance is zero, block subsidies are identical to the existing halving schedule.
  3. From \(\mathsf{NSM\_REISSUANCE\_HEIGHT}\) onward, if the NSM Value Balance is greater than 0, then the additional block subsidy must be non-zero. The purpose is that funds removed from circulation are fully reissued at a later time.
  4. This requirement applies to any halving period when no ZEC/TAZ is removed from circulation. Then the additional block subsidies paid out are approximately equal to half of the NSM Value Balance at the start of that period.
  5. Decrease the short-term effect of the deployment of this ZIP on block subsidy recipients. Make the possible reputation risk to Zcash from a change to the block subsidy amount as small as possible.

Specification

Mechanisms for removal from circulation

From NU7 [zip-0259], these mechanisms for removal from circulation are part of the consensus rules:

MechanismSourceDefining ZIP
Transaction fees\(\mathsf{NSMFeeContribution}(\mathsf{height})\)ZIP 235 [zip-0235]

Additional mechanisms for removal from circulation can be added to this list through changes to this ZIP that are specified in other ZIPs. In such a change, the source must be specified as a function that depends only on height.

Let \(\mathsf{NSMValueRemoved}(\mathsf{height} ⦂ \mathbb{N})\) be the total value removed from circulation in the block at \(\mathsf{height}\). It is the sum of all values in the "Source" column above.

Parameters

\(\mathsf{LN2\_SCALED} ⦂ \mathbb{N} := 6\_931\_680\_000\)

\(\mathsf{HalvingInterval}(\mathsf{height} ⦂ \mathbb{N}) :=\) the number of blocks in a halving period at \(\mathsf{height}\). Its value is as follows:

  • If \(\mathsf{IsNU7Activated}(\mathsf{height})\) as defined in ZIP 218 [zip-0218], the value is \(\mathsf{PostNU7HalvingInterval}\).
  • If not, the value is \(\mathsf{PostBlossomHalvingInterval}\).

\(\mathsf{BLOCK\_SUBSIDY\_FRACTION}(\mathsf{height} ⦂ \mathbb{N}) := \mathsf{floor}(\mathsf{LN2\_SCALED} / \mathsf{HalvingInterval}(\mathsf{height})) / 10\_000\_000\_000\)

With \(\mathsf{PostBlossomHalvingInterval} = 1\_680\_000\), this fraction is \(4126 / 10\_000\_000\_000 = 0.0000004126\). This is the value specified by ZIP 234 [zip-0234]. With \(\mathsf{PostNU7HalvingInterval} = 5\_040\_000\), this fraction is \(1375 / 10\_000\_000\_000\). \(\mathsf{NSM\_REISSUANCE\_HEIGHT}\) is not before NU7 activation. Thus only the second value is used in \(\mathsf{AdditionalBlockSubsidy}\). Refer to the BLOCK_SUBSIDY_FRACTION section below.

\(\mathsf{INITIAL\_NSM\_VALUE\_BALANCE} ⦂ \{0\,..\,\mathsf{MAX\_MONEY}\} :=\) the block subsidy and fees left unclaimed by coinbase transactions before NU6, in zatoshi. This value is the start value of the NSM Value Balance at NU7 activation. Under ZIP 236 [zip-0236], it is necessary for coinbase transactions to claim their full value. Thus this value is the fixed amount

\(\sum_{\mathsf{h}=0}^{\mathsf{H}} \mathsf{ScheduledBlockSubsidy}(\mathsf{h}) - \mathsf{IssuedSupply}(\mathsf{H})\)

for any \(\mathsf{H}\) from the last pre-NU6 height up to \(\mathsf{NU7ActivationHeight} - 1\). The values for each network are as follows:

NetworkLast pre-NU6 height \(\mathsf{H}\)\(\mathsf{INITIAL\_NSM\_VALUE\_BALANCE}\) (zatoshi)
Mainnet2,726,39936,858,445,520 (368.58445520 ZEC)
Testnet2,975,99955,768,414,957 (557.68414957 TAZ)

The derivation of these values is as follows, in zatoshi. The scheduled issuance is calculated from § 7.8. \(\mathsf{IssuedSupply}(\mathsf{H})\) is the sum of these chain value pool balances at \(\mathsf{H}\):

  • The transparent chain value pool balance.
  • The Sprout chain value pool balance.
  • The Sapling chain value pool balance.
  • The Orchard chain value pool balance.

(At \(\mathsf{H}\), the deferred development fund chain value pool balance and the Ironwood chain value pool balance are zero.) This sum can be checked against the chain value pool balances that a full node reports at that height.

Network\(\sum_{\mathsf{h}=0}^{\mathsf{H}} \mathsf{ScheduledBlockSubsidy}(\mathsf{h})\)\(\mathsf{IssuedSupply}(\mathsf{H})\)
Mainnet1,575,000,000,000,0001,574,963,141,554,480
Testnet1,603,125,000,000,0001,603,069,231,585,043

\(\mathsf{NSM\_REISSUANCE\_HEIGHT} ⦂ \mathbb{N} :=\) the height where reissuance starts on the applicable network. The calculation is in NSM reissuance height below.

NSM reissuance height

The reissuance height is determined from the scheduled issuance curve and a reference reserve of \(\mathsf{MAX\_MONEY} - S_A(h - 1)\). This determination does not include amounts removed from circulation or the positive historical start value. Thus the reissuance height is independent of transaction activity and of the actual NSM Value Balance.

For each network, let \(A = \mathsf{NU7ActivationHeight}\). Let \(B_A(h)\) be \(\mathsf{ScheduledBlockSubsidy}(h)\) after ZIP 218 [zip-0218] is applied at \(A\). Let \(S_A(h) = \sum_{i=0}^{h} B_A(i)\) be the cumulative scheduled issuance up to and including height \(h\). This value does not include additional NSM subsidies or amounts removed from circulation. Let \(H_3\) be the first height where the ZIP 218 \(\mathsf{Halving}\) function is equal to 3. Let \(H_4\) be the first height where this function is equal to 4.

\(\mathsf{NSM\_REISSUANCE\_HEIGHT}\) must be the first height \(h\) with \(\max(A, H_3 + 1) \leq h < H_4\) that satisfies this inequality:

\[\mathsf{ceiling}\left(\frac{1375\,(\mathsf{MAX\_MONEY} - S_A(h - 1))}{10^{10}}\right) < B_A(h).\]

In this inequality, 1375 is the numerator of \(\mathsf{BLOCK\_SUBSIDY\_FRACTION}\) after NU7 activation. With the strict inequality, the selected block is the first block where the rounded reference NSM subsidy is less than the scheduled block subsidy. The ceiling is the same rounding rule as in \(\mathsf{AdditionalBlockSubsidy}\). The reference balance \(\mathsf{MAX\_MONEY} - S_A(h - 1)\) is used only to select the deployment height. The NU7 activation heights were selected so that this height exists before \(H_4\). The resulting height for each network is specified in the NU7 deployment ZIP [zip-0259].

It is possible to calculate the value without a test of each block. Set these values:

  • \(h_0 = \max(A, H_3 + 1)\)
  • \(b = B_A(h_0)\)
  • \(R_0 = \mathsf{MAX\_MONEY} - S_A(h_0 - 1)\)
  • \(R_{\max} = \mathsf{floor}((b - 1) \cdot 10^{10}/1375)\)

Before \(H_4\), \(b\) is constant. Thus the first height that qualifies is

\[h_0 + \mathsf{ceiling}\left(\frac{\max(0, R_0 - R_{\max})}{b}\right).\]

The expected case is that \(A\) is between the second and third pre-NU7 halvings. In this case, the ZIP 218 third halving occurs at \(H_3 = A + 3(H_3^{(75)} - A)\). Here, \(H_3^{(75)}\) is 4,406,400 on Mainnet and 4,476,000 on Testnet. Let \(H_2^{(75)}\) be the second halving height for the same network, in the table below. In this range, these values apply:

  • \(b = 26{,}041{,}666\)
  • \(R_{\max} = 189{,}393{,}927{,}272{,}727\)
  • \(R_0 = 262{,}499{,}975{,}638{,}334 - (A - H_2^{(75)})\) zatoshi

Thus \(\mathsf{ceiling}((R_0 - R_{\max})/b) = 2{,}807{,}273\) everywhere in this range. With the one-block offset from \(H_3\) to \(h_0\) included, the result is \(\mathsf{NSM\_REISSUANCE\_HEIGHT} = H_3 + 2{,}807{,}274\):

NetworkSecond halvingThird halving after NU7Reissuance height
Mainnet2,726,400\(13{,}219{,}200 - 2A\)\(16{,}026{,}474 - 2A\)
Testnet2,796,000\(13{,}428{,}000 - 2A\)\(16{,}235{,}274 - 2A\)

For example, the Mainnet activation height is \(A = 3{,}543{,}405\) [zip-0259]. With this value, the third halving is at 6,132,390 and the reissuance height is 8,939,664. At height 8,939,663, the rounded reference subsidy is 26,041,667 zatoshi. This is more than the scheduled 26,041,666. At height 8,939,664, the rounded reference subsidy is 26,041,663. This is less than the scheduled value.

Changes to the Zcash Protocol Specification

These changes apply to § 7.8 ‘Calculating Block Subsidy, Funding Streams, Lockbox Disbursement, and Founders' Reward’ [protocol-subsidies]:

First, apply the changes of ZIP 218 [zip-0218]. Then change the name of the resulting function \(\mathsf{BlockSubsidy}(\mathsf{height})\) to \(\mathsf{ScheduledBlockSubsidy}(\mathsf{height})\). Do not change its definition.

Add this definition. In this definition, \(\mathsf{NSMValueBalance}\) is as defined in § 4.17 ‘Chain Value Pool Balances’ [protocol-chainvaluepoolbalances] below:

\[\mathsf{AdditionalBlockSubsidy}(\mathsf{height} ⦂ \mathbb{N}) := \begin{cases} 0, & \text{if } \mathsf{height} < \mathsf{NSM\_REISSUANCE\_HEIGHT} \\ \mathsf{ceiling}(\mathsf{BLOCK\_SUBSIDY\_FRACTION}(\mathsf{height}) \cdot \mathsf{NSMValueBalance}(\mathsf{height} - 1)), & \text{otherwise} \end{cases}\]

Define \(\mathsf{BlockSubsidy}(\mathsf{height})\) as follows:

\(\mathsf{BlockSubsidy}(\mathsf{height}) := \mathsf{ScheduledBlockSubsidy}(\mathsf{height}) + \mathsf{AdditionalBlockSubsidy}(\mathsf{height})\)

Add these constants to § 5.3 ‘Constants’ [protocol-constants], and to the list of integer constants in § 2 ‘Notation’ [protocol-notation]:

  • \(\mathsf{LN2\_SCALED}\)
  • \(\mathsf{INITIAL\_NSM\_VALUE\_BALANCE}\)
  • \(\mathsf{NSM\_REISSUANCE\_HEIGHT}\)

Add \(\mathsf{HalvingInterval}\) and \(\mathsf{BLOCK\_SUBSIDY\_FRACTION}\) to § 7.8, as given in Parameters above.

All other uses of \(\mathsf{BlockSubsidy}(\mathsf{height})\) in the protocol specification do not change, and they refer to the redefined function. These uses are:

  • \(\mathsf{FoundersReward}\).
  • \(\mathsf{fsValue}\), and thus \(\mathsf{totalDeferredOutput}\).
  • \(\mathsf{MinerSubsidy}\).
  • The total input value of a coinbase transaction in § 7.1.2 [protocol-txnconsensus].

Specifically, the value of each funding stream is its fixed percentage of the total block subsidy. (The total block subsidy is the scheduled block subsidy plus the additional block subsidy.)

Note: \(\mathsf{BlockSubsidy}(\mathsf{height})\) now depends on the NSM Value Balance after block \(\mathsf{height} - 1\). It does not depend only on \(\mathsf{height}\).

In § 4.17 ‘Chain Value Pool Balances’ [protocol-chainvaluepoolbalances], add two definitions. The first definition is \(\mathsf{NSMValueRemoved}(\mathsf{height})\) from Mechanisms for removal from circulation above. From NU7, this value is \(\mathsf{NSMFeeContribution}(\mathsf{height})\). Let \(\mathsf{NU7ActivationHeight}\) be the NU7 activation height on the applicable network [zip-0259]. The second definition is as follows:

\[\mathsf{NSMValueBalance}(\mathsf{height} ⦂ \mathbb{N}) := \begin{cases} 0, & \text{if } \mathsf{height} < \mathsf{NU7ActivationHeight} - 1 \\ \mathsf{INITIAL\_NSM\_VALUE\_BALANCE}, & \text{if } \mathsf{height} = \mathsf{NU7ActivationHeight} - 1 \\ \mathsf{NSMValueBalance}(\mathsf{height} - 1) - \mathsf{AdditionalBlockSubsidy}(\mathsf{height}) + \mathsf{NSMValueRemoved}(\mathsf{height}), & \text{otherwise} \end{cases}\]

The NSM Value Balance is tracked as consensus state, together with the chain value pools. It is not a spendable chain value pool. It is not included in \(\mathsf{IssuedSupply}(\mathsf{height})\). It is a count of ZEC/TAZ that is not in circulation. This is consistent with ZIP 233 [zip-0233], where removed funds are subtracted from the issued supply.

With reissuance, value is moved from the NSM Value Balance into the Issued Supply through the block subsidy.

Add this consensus rule:

[NU7 onward] All nodes must reject a block at \(\mathsf{height}\) as invalid if \(\mathsf{NSMValueBalance}(\mathsf{height})\) becomes negative in the block chain that results from its acceptance.

In § 3.10 ‘Block Subsidy, Funding Streams, and Founders' Reward’ [protocol-subsidyconcepts], add this text:

[NU7 onward] From \(\mathsf{NSM\_REISSUANCE\_HEIGHT}\), the block subsidy also includes value reissued from the NSM Value Balance defined in § 4.17 ‘Chain Value Pool Balances’. Thus the block subsidy depends on the NSM Value Balance after the previous block, and also on the block height.

In § 3.4 ‘Transactions and Treestates’ [protocol-transactions], there is a statement about coinbase transactions in blocks before NU6. The statement is that the remaining value in their transparent transaction value pool is destroyed. Change this statement. Write that this value is left unclaimed and is not added to any chain value pool. Then add this text:

[NU7 onward] This unclaimed value is included in \(\mathsf{INITIAL\_NSM\_VALUE\_BALANCE}\). Thus it is reissued as specified in § 7.8.

Applicability

All of these changes apply in the same way to Mainnet and to Testnet.

Rationale

Rationale for Parameters

When the NSM Value Balance is zero, the formula is the same as the existing schedule. Thus there is no constraint from the rule itself on the deployment height. At deployment, the only change is the reissuance of the NSM Value Balance at that point, at \(\mathsf{BLOCK\_SUBSIDY\_FRACTION}\) per block. (At that point, the NSM Value Balance is \(\mathsf{INITIAL\_NSM\_VALUE\_BALANCE}\) plus all value removed from circulation since NU7 activation.)

For example, assume that a total of 100,000 ZEC is removed from circulation between NU7 activation and \(\mathsf{NSM\_REISSUANCE\_HEIGHT}\). Then, at \(\mathsf{NSM\_REISSUANCE\_HEIGHT}\), the issuance is larger than the Scheduled Block Subsidy by \(100\_000\textsf{ ZEC} \cdot \mathsf{BLOCK\_SUBSIDY\_FRACTION}\). Under the post-NU7 schedule, this difference is equal to \(0.01375\) ZEC. This example is selected to show the effect of a very large amount removed from circulation. (This amount is much larger than expected.) The increase in issuance is relatively small, and thus Requirement 5 is satisfied.

From NU6, it is necessary for coinbase transactions to claim the full miner subsidy and fees [zip-0236]. Thus the part of the NSM Value Balance that does not come from funds removed from circulation is a fixed historical amount, \(\mathsf{INITIAL\_NSM\_VALUE\_BALANCE}\). On Mainnet, this amount is 368.58445520 ZEC. From deployment, it is reissued at an initial rate of approximately 0.00005 ZEC per block under ZIP 218.

BLOCK_SUBSIDY_FRACTION

Let \(\mathsf{IntendedFractionRemainingAfterOneHalvingPeriod} = 0.5\). That is, the intention is that the NSM Value Balance decreases by half in the same period as the block subsidy. Thus the fraction is a function of the halving schedule, and it is not a constant. The purpose is that this property stays true for all target block spacings:

\((1 - \mathsf{BLOCK\_SUBSIDY\_FRACTION}(\mathsf{height}))^{\mathsf{HalvingInterval}(\mathsf{height})} \approx \mathsf{IntendedFractionRemainingAfterOneHalvingPeriod}\)

The solution is a fraction of approximately \(\ln 2 / \mathsf{HalvingInterval}(\mathsf{height})\). \(\mathsf{LN2\_SCALED}\) is \(10^{10} \cdot \ln 2 \approx 6\_931\_471\_805.6\), rounded up to a multiple of \(\mathsf{PostBlossomHalvingInterval}\). The purpose is that, on the 75-second schedule, the numerator is exactly the 4126 of ZIP 234 [zip-0234]. This numerator satisfies the approximation within \(\pm 0.003\%\).

In ZIP 218 [zip-0218], \(\mathsf{PostBlossomHalvingInterval}\) does not change. ZIP 218 has a separate definition, \(\mathsf{PostNU7HalvingInterval} = 5\_040\_000\), for its 25-second blocks. With that interval, the numerator is 1375. This value applies from \(\mathsf{NSM\_REISSUANCE\_HEIGHT}\): \((1 - 1375/10^{10})^{5\_040\_000} \approx 0.50007\), within \(+0.015\%\).

If the numerator stays at 4126 under ZIP 218, the balance decreases by half approximately every 1.33 years. The cause is that the numerator then applies three times as often.

Without rounding, approximately half of the NSM Value Balance is issued as additional block subsidies after one halving period. Each subsidy is rounded up to a zatoshi. With this rounding, the amount issued is larger than on that curve by less than one zatoshi per block. Thus the approximation is close for large balances, but not for small balances. For example, a balance of 1 zatoshi is issued in the next block, and it does not decrease by half over a halving period. More generally, when the rounded additional subsidy is 1 zatoshi, one zatoshi is issued per block until the balance is zero.

In theory, it is possible that all issued funds are removed from circulation. In that case, the largest possible value of the NSM Value Balance is less than \(\mathsf{MAX\_MONEY}\). Also, the largest interim product in the block subsidy calculation is less than \(\mathsf{MAX\_MONEY} \cdot 1375\) under ZIP 218 [zip-0218].

The size of this product is a maximum of 61.33 bits. This is less than the 63-bit limit for signed two's complement 64-bit integer amount types.

With a larger denominator, the numerator can be closer to the limit. But the difference in the amount issued is very small. Thus we selected a power-of-10 denominator, because it is simple.

Appendix: Considerations for the Future

In future protocol changes, the payout rate of the NSM Value Balance must not increase past the one-halving-period half-life constraint, to a reasonable approximation.

Deployment

This ZIP activated with Network Upgrade 7 [zip-0259]. Reissuance starts at \(\mathsf{NSM\_REISSUANCE\_HEIGHT}\). This ZIP must not be deployed together with ZIP 234 [zip-0234].

This ZIP does not depend on ZIP 233 (“NSM: Removing Funds From Circulation” [zip-0233]). Funds removed from circulation by ZIP 233 or any other mechanism are credited to the NSM Value Balance if and when that mechanism is deployed. ZIP 218 is necessary for this ZIP [zip-0218].

Reference implementation

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 2026.8.0 [NU6.3] or later
[protocol-notation]
Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 2: Notation
[protocol-transactions]
Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 3.4: Transactions and Treestates
[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-diffadjustment]
Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 7.7.3: Difficulty Adjustment
[protocol-txnconsensus]
Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 7.1.2: Transaction Consensus Rules
[protocol-subsidies]
Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 7.8: Calculating Block Subsidy, Funding Streams, Lockbox Disbursement, and Founders' Reward
[zip-0200]
ZIP 200: Network Upgrade Mechanism
[zip-0218]
ZIP 218: 25-second Block Target Spacing
[zip-0218-issuance-curve]
ZIP 218: 25-second Block Target Spacing — Rationale for altering the issuance curve
[zip-0233]
ZIP 233: Network Sustainability Mechanism: Removing Funds From Circulation
[zip-0234]
ZIP 234: Network Sustainability Mechanism: Issuance Smoothing
[zip-0235]
ZIP 235: Remove 60% of Transaction Fees From Circulation
[zip-0236]
ZIP 236: Blocks should balance exactly
[zip-0259]
ZIP 259: Deployment of the NU7 Network Upgrade
[zebra-11454]
Zebra PR 11454: feat(chain, consensus, state, rpc): add halving-preserving NU7 issuance
[zebra-11529]
Zebra PR 11529: feat(consensus)!: implement NU7 spacing, funding schedules, and shielded limits
[zebra-11530]
Zebra PR 11530: feat(nsm)!: enable merged issuance and fee accounting