Zcash in Simplified Technical English

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

ZIP 259: Deployment of the NU7 Network Upgrade

ZIP: 259
Title: Deployment of the NU7 Network Upgrade
Owners: Dev Ojha <dev@valargroup.dev>
Status: Final
Category: Consensus / Network
Created: 2026-09-15
License: MIT
Discussions-To: <https://forum.zcashcommunity.com/t/nu7-coinholder-vote/56912>

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" has the same meaning as in ZIP 200 [zip-0200].

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

The terms "Mainnet" and "Testnet" have the same meanings as in § 3.12 'Mainnet and Testnet' [protocol-networks].

"Scheduled Block Subsidy" is the block subsidy of the existing halving schedule, after the changes in ZIP 218 are applied [zip-0218].

"NSM Value Balance" has the same meaning as in ZIP 237 [zip-0237].

Abstract

This ZIP contains the specification for the deployment of the NU7 network upgrade. NU7 includes these changes:

ZIP 2008 is also deployed with NU7.

NU7 has no new transaction format. From NU7 activation, version 4 transactions are invalid, and version 5 and version 6 transactions stay valid. Sprout transfers can be represented only by version 4 transactions. Thus the funds that remained in the Sprout pool became unspendable [zip-2003].

With these changes, the ZEC supply cap does not increase. Funds that are issued from the NSM Value Balance have one of these two origins:

The NSM Value Balance is public consensus state. With the NSM Value Balance, there is no new data at the transaction level.

Motivation

NU7 is deliberately limited to changes that have strong support from these groups:

These changes can be deployed without another migration of the transaction format. With faster blocks, the confirmation latency decreases. Because of the higher block frequency, the costs of validation and of shielded synchronization can increase. These costs are limited by the action limits in ZIP 218.

Specification

NU7 consensus changes

The primary sources of information about the consensus protocol changes of NU7 are these documents:

  • The Zcash Protocol Specification [protocol].
  • ZIP 200: Network Upgrade Mechanism [zip-0200].
  • ZIP 207: Funding Streams (Revision 2) [zip-0207].
  • ZIP 214: Consensus rules for a Zcash Development Fund (Revision 3) [zip-0214].
  • ZIP 218: 25-second Block Target Spacing [zip-0218].
  • ZIP 235: Remove 60% of Transaction Fees From Circulation [zip-0235].
  • ZIP 237: Network Sustainability Mechanism: Halving-Preserving Issuance [zip-0237].
  • ZIP 2003: Disallow version 4 transactions [zip-2003].
  • ZIP 2008: Update to FS_FPF_ZCG_H3 address list [zip-2008].

The mechanisms for the network handshake and for peer management in ZIP 201 also apply to this network upgrade [zip-0201].

All of the consensus changes that are specified in the ZIPs in the list above are deployed with NU7. These changes include Revision 2 of ZIP 207 and Revision 3 of ZIP 214. ZIP 233 and ZIP 234 are not deployed with NU7 [zip-0233] [zip-0234].

ZIP 218 contains a change for Testnet at the Testnet NU7 activation height. With this change, the minimum-difficulty threshold of ZIP 208 changes from six to 18 target block spacings. With the 25-second target block spacing, a block time must be more than 450 seconds after the previous block's time to qualify for minimum difficulty. This change has no effect on Mainnet [zip-0208].

For NU7 only, a requirement in ZIP 200 [zip-0200] did not apply. This requirement is that ACTIVATION_HEIGHT must be greater than DEPRECATION_HEIGHT in the last implementation version without support for the network upgrade. The recommendation to let approximately three months pass after the first implementation release with support for the network upgrade also did not apply. This exception has no effect on the scheduling requirements for other network upgrades.

Thus it was possible that operators of unsupported implementations stayed online at activation and followed a pre-NU7 consensus branch. It was necessary to give operators an explicit warning in the deployment communications: upgrade before activation.

NU7 network constants

These network upgrade constants are defined for NU7 [zip-0200]:

CONSENSUS_BRANCH_ID
0x77190AD9
ACTIVATION_HEIGHT (NU7)
Testnet: 4465026
Mainnet: 3543405

Each ACTIVATION_HEIGHT (NU7) must be a multiple of 3. This is a requirement of Revision 3 of ZIP 214 [zip-0214]. The Mainnet activation height must also satisfy the address-list constraint in ZIP 2008 [zip-2008]. With this constraint, the new funding recipient is selected before the stream ends.

NSM_REISSUANCE_HEIGHT
Testnet: 7305222
Mainnet: 8939664

Each NSM_REISSUANCE_HEIGHT is the value that is calculated in ZIP 237 [zip-0237] for the applicable network.

The Testnet ACTIVATION_HEIGHT (NU7) is \(A = 4{,}465{,}026\). This height is between the second and the third pre-NU7 Testnet halvings (2,796,000 and 4,476,000). Thus the ZIP 218 third halving is at \(H_3 = 13{,}428{,}000 - 2A = 4{,}497{,}948\). The Testnet reissuance height is \(H_3 + 2{,}807{,}274 = 16{,}235{,}274 - 2A = 7{,}305{,}222\).

The Mainnet ACTIVATION_HEIGHT (NU7) is \(A = 3{,}543{,}405\). This height is between the second and the third pre-NU7 Mainnet halvings (2,726,400 and 4,406,400). Thus the ZIP 218 third halving is at \(H_3 = 13{,}219{,}200 - 2A = 6{,}132{,}390\). The Mainnet reissuance height is \(H_3 + 2{,}807{,}274 = 16{,}026{,}474 - 2A = 8{,}939{,}664\).

MIN_NETWORK_PROTOCOL_VERSION (NU7)
Testnet: 170180
Mainnet: 170190

For each network, nodes compatible with NU7 activation on that network must advertise a network protocol version equal to or greater than the applicable MIN_NETWORK_PROTOCOL_VERSION.

Backward compatibility

Before NU7 activation on a network, NU7 nodes and pre-NU7 nodes were able to connect to each other. NU7 nodes preferred other NU7 nodes. Thus pre-NU7 nodes were gradually disconnected in the period before activation.

From NU7 activation, NU7 nodes disconnect peers that advertise a lower network protocol version. Also, blocks that are produced under the pre-NU7 consensus rules can be rejected because of one or more of these new items:

  • The target block spacing.
  • The subsidy calculation.
  • The action limits.
  • The fee allocation.
  • The transaction-version rule.

The prohibition of version 4 transactions applies to all version 4 transactions. This prohibition also applies to transparent-only transactions and Sapling transactions, in addition to Sprout transfers. It was necessary for wallets and transaction services to do these two things:

  • Stop the creation of version 4 transactions for inclusion after activation.
  • Clearly report pending transactions that became invalid.

Where possible, users can create non-Sprout transactions again in a supported format. A version 4 transaction cannot become valid if it is only signed again. The same activation checks are necessary for saved transactions and offline-signed transactions. For Sprout transactions, there is no supported replacement format after activation.

The structure of version 5 and version 6 transactions stays the same. But this does not mean that a transaction is valid across NU7 activation. The reason is that the signatures of a transaction commit to a consensus branch ID.

Rationale

Coinholder and Community polling

The August and September 2026 NU7 polls had five questions about the scope:

  • If halvings are to be kept, or if issuance is to be smoothed.
  • When NSM reissuance is to start.
  • When version 4 transactions are to be disabled.
  • If ZIP 218 is to be deployed.
  • If NU7 is to be released promptly, with only the features that are ready by the September 30 deadline.

The complete questions and response options are in the poll announcement [nu7-poll-questions].

The coinholder and community poll results are available in [nu7-poll-results].

In the polls, there was no shared majority position on when NSM reissuance is to start. For NU7, the start is the post-third-halving crossover of reference NSM issuance and the scheduled block subsidy. This crossover is calculated from the assigned NU7 activation height, as specified in ZIP 237 [zip-0237].

Rationale for no new transaction format

Version 6 was introduced in NU6.3 [zip-0229]. NU7 is the network upgrade immediately after this introduction. Without a new format in NU7, the disruption to parsers and wallets is limited.

The fee contribution is a consensus calculation at the block level. Thus a new field is not necessary in ordinary transactions or in coinbase transactions.

Open issues

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-networks]
Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 3.12: Mainnet and Testnet
[zip-0200]
ZIP 200: Network Upgrade Mechanism
[zip-0201]
ZIP 201: Network Peer Management for Overwinter
[zip-0207]
ZIP 207: Funding Streams
[zip-0208]
ZIP 208: Shorter Block Target Spacing
[zip-0214]
ZIP 214: Consensus rules for a Zcash Development Fund
[zip-0218]
ZIP 218: 25-second Block Target Spacing
[zip-0229]
ZIP 229: Version 6 Transaction Format
[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-0237]
ZIP 237: Network Sustainability Mechanism: Halving-Preserving Issuance
[zip-2003]
ZIP 2003: Disallow version 4 transactions
[zip-2008]
ZIP 2008: Update to FS_FPF_ZCG_H3 address list
[nu7-poll-questions]
NU7 Coinholder Vote: poll questions and scope
[nu7-poll-results]
NU7 Sentiment Polls Results