Zcash in Simplified Technical English

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

ZIP 255: Deployment of the NU6.1 Network Upgrade

ZIP: 255
Title: Deployment of the NU6.1 Network Upgrade
Owners: Daira-Emma Hopwood <daira@jacaranda.org>
Credits: Arya
Status: Final
Category: Consensus / Network
Created: 2025-05-06
License: MIT
Discussions-To: <https://github.com/zcash/zips/issues/1011>

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 used for references to sections of the Zcash Protocol Specification [protocol].

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

Abstract

This ZIP contains the definition of the deployment of the NU6.1 network upgrade.

Specification

NU6.1 deployment

The primary sources of information about the NU6.1 changes to the consensus protocol are:

  • The Zcash Protocol Specification [protocol].
  • ZIP 200: Network Upgrade Mechanism [zip-0200].
  • ZIP 271: Deferred Dev Fund Lockbox Disbursement [zip-0271].
  • ZIP 1016: Community And Coinholder Funding Model [zip-1016].

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

These are the network upgrade constants [zip-0200] for the NU6.1 network upgrade:

CONSENSUS_BRANCH_ID
0x4DEC4DF0
ACTIVATION_HEIGHT (NU6.1)

Testnet: 3536500

Mainnet: 3146400

MIN_NETWORK_PROTOCOL_VERSION (NU6.1)

Testnet: 170130

Mainnet: 170140

For each network (Testnet and Mainnet), this requirement applies to the nodes that are compatible with NU6.1 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.1) for that activation.

Backward compatibility

Before the activation of the network upgrade on each network, NU6.1 nodes and pre-NU6.1 nodes are compatible and can connect to each other. But NU6.1 nodes prefer to connect to other NU6.1 nodes. Thus pre-NU6.1 nodes are gradually disconnected in the period before activation.

After the activation of the network upgrade, pre-NU6.1 nodes can still accept the numerically larger protocol version of NU6.1 as valid. But after that activation, NU6.1 nodes always disconnect peers that use lower protocol versions.

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.0 or later
[protocol-networks]
Zcash Protocol Specification, Version 2025.6.0 [NU6.1 proposal]. Section 3.12: Mainnet and Testnet
[zip-0200]
ZIP 200: Network Upgrade Mechanism
[zip-0201]
ZIP 201: Network Peer Management for Overwinter
[zip-0271]
ZIP 271: Deferred Dev Fund Lockbox Disbursement
[zip-1016]
ZIP 1016: Community and Coinholder Funding Model