This page is the Simplified Technical English version of ZIP 253. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 253: Deployment of the NU6 Network Upgrade
ZIP: 253 Title: Deployment of the NU6 Network Upgrade Owners: Arya <arya@zfnd.org> Status: Final Category: Consensus / Network Created: 2024-07-17 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/806>
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 term "network upgrade" has the definition in ZIP 200 [zip-0200].
In this document, the terms "Testnet" and "Mainnet" have the definitions in section 3.12 of the Zcash Protocol Specification [protocol-networks].
Abstract
This ZIP contains the definition of the deployment of the NU6 network upgrade.
Specification
NU6 deployment
The primary sources of information about the NU6 changes to the consensus protocol are:
- The Zcash Protocol Specification [protocol].
- ZIP 200: Network Upgrade Mechanism [zip-0200].
- ZIP 236: Blocks should balance exactly [zip-0236].
- ZIP 1015: Block Reward Allocation for Non-Direct Development Funding [zip-1015].
- ZIP 2001: Lockbox Funding Streams [zip-2001].
The network handshake and peer management mechanisms that are defined in ZIP 201 [zip-0201] also apply to this network upgrade.
The ZIPs that follow have updates for NU6. The size of the update is different for each ZIP:
- ZIP 207: Funding Streams [zip-0207].
- ZIP 214: Consensus rules for a Zcash Development Fund [zip-0214].
These are the network upgrade constants [zip-0200] for the NU6 network upgrade:
- CONSENSUS_BRANCH_ID
0xC8E71055- ACTIVATION_HEIGHT (NU6)
-
Testnet: 2976000
Mainnet: 2726400
- MIN_NETWORK_PROTOCOL_VERSION (NU6)
-
Testnet:
170110Mainnet:
170120
For each network (Testnet and Mainnet), this requirement applies to the nodes that are compatible with NU6 activation on that network. These nodes must advertise a network protocol version that is greater than or equal to the MIN_NETWORK_PROTOCOL_VERSION (NU6) for that activation.
Backward compatibility
Before the activation of the network upgrade on each network, NU6 nodes and pre-NU6 nodes are compatible and can connect to each other. But NU6 nodes prefer connections to other NU6 nodes. Thus pre-NU6 nodes are gradually disconnected in the period before activation.
After the activation of the network upgrade, pre-NU6 nodes can still accept the numerically larger protocol version of NU6 as valid. But after that activation, NU6 nodes always disconnect peers that use lower protocol versions.
NU6 has no new transaction version and no new minimum transaction version. Thus NU6 transactions are in the same v4 or v5 formats as NU5 transactions. But this does not mean that transactions are valid across the NU6 activation. The reason is that the applicable consensus branch ID must be used in signatures.
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.2 or later [NU6.1]
- [protocol-networks]
- Zcash Protocol Specification, Version 2025.6.2 [NU6.1]. 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-0214]
- ZIP 214: Consensus rules for a Zcash Development Fund
- [zip-0236]
- ZIP 236: Blocks should balance exactly
- [zip-1015]
- ZIP 1015: Block Reward Allocation for Non-Direct Development Funding
- [zip-2001]
- ZIP 2001: Lockbox Funding Streams