ZIP: 253
Title: Deployment of the NU6 Network Upgrade
Owners: Arya <arya@zfnd.org>
Status: Proposed
Category: Consensus / Network
Created: 2024-07-17
License: MIT
Discussions-To: <https://github.com/zcash/zips/issues/806>The key word “MUST” in this document are to be interpreted as described in BCP 14 1 when, and only when, they appear in all capitals.
The term “network upgrade” in this document is to be interpreted as described in ZIP 200 2.
The terms “Testnet” and “Mainnet” are to be interpreted as described in section 3.12 of the Zcash Protocol Specification 3.
This proposal defines the deployment of the NU6 network upgrade.
The primary sources of information about NU6 consensus protocol changes are:
The network handshake and peer management mechanisms defined in ZIP 201 9 also apply to this upgrade.
The following ZIPs have been updated in varying degrees to take into account NU6:
The following network upgrade constants 12 are defined for the NU6 upgrade:
0xC8E71055
170110
170120
For each network (Testnet and Mainnet), nodes compatible with NU6 activation on that network MUST advertise a network protocol version that is greater than or equal to the MIN_NETWORK_PROTOCOL_VERSION (NU6) for that activation.
Prior to the network upgrade activating on each network, NU6 and pre-NU6 nodes are compatible and can connect to each other. However, NU6 nodes will have a preference for connecting to other NU6 nodes, so pre-NU6 nodes will gradually be disconnected in the run up to activation.
Once the network upgrades, even though pre-NU6 nodes can still accept the numerically larger protocol version used by NU6 as being valid, NU6 nodes will always disconnect peers using lower protocol versions.
NU6 does not define a new transaction version or impose a new minimum transaction version. NU6 transactions are therefore in the same v4 or v5 formats as NU5 transactions. This does not imply that transactions are valid across the NU6 activation, since signatures MUST use the appropriate consensus branch ID.