This page is the Simplified Technical English version of ZIP 258. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 258: Deployment of the NU6.3 Network Upgrade
ZIP: 258 Title: Deployment of the NU6.3 Network Upgrade Owners: Daira-Emma Hopwood <daira@jacaranda.org> Status: Final Category: Consensus / Network Created: 2026-06-19 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/1304>
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].
These terms have the same meanings as in ZIP 229 [zip-0229]:
- "Orchard protocol"
- "Orchard pool"
- "Ironwood pool"
- "Orchard-pool Action"
- "version 6 transaction"
Abstract
This ZIP is the specification for the deployment of the NU6.3 network upgrade. NU6.3 has a new shielded pool, the Ironwood shielded pool.
The specification of the consensus changes for NU6.3 is in these documents:
- The version 6 transaction format [zip-0229].
- The Orchard Action circuit update [zip-2006].
- ZIP 2005 [zip-2005].
- This ZIP.
This ZIP contains the values of the activation parameters. It also contains the consensus rules that apply from NU6.3 activation, for all transaction versions.
Specification
NU6.3 deployment
The primary sources of information about the changes to the consensus protocol in NU6.3 are:
- The Zcash Protocol Specification [protocol]
- ZIP 200: Network Upgrade Mechanism [zip-0200]
- ZIP 229: Version 6 Transaction Format [zip-0229]
- ZIP 2005: Ironwood Quantum Recoverability [zip-2005]
- ZIP 2006: Restricting Transfers into the Orchard Pool [zip-2006]
- ZIP 209: ... [zip-0209] (updated)
- ZIP 213: ... [zip-0213] (updated)
The wallet considerations are in these documents:
- ZIP 318: Orchard to Ironwood Migration [zip-0318]
- ZIP 326: NU6.3 Consequences for Wallets [zip-0326]
- ZIP 317: Proportional Fee Mechanism [zip-0317] (updated)
The mechanisms for the network handshake and for peer management in ZIP 201 [zip-0201] also apply to this network upgrade.
The network upgrade constants [zip-0200] for the NU6.3 network upgrade have these values:
- CONSENSUS_BRANCH_ID
- 0x37A5165B
- ACTIVATION_HEIGHT (NU6.3)
- Testnet: 4134000
Mainnet: 3428143 - MIN_NETWORK_PROTOCOL_VERSION (NU6.3)
- Testnet: 170160
Mainnet: 170160
The assignment of these values is as described in ZIP 204 [zip-0204].
Note: For NU6.3, the Testnet protocol version and the Mainnet protocol version are the same. They were also the same for NU6.2. NU6.3 is the last network upgrade that can have the same protocol version for Testnet and Mainnet. Because of the assignment rule in ZIP 204, the two protocol versions are different from NU7 onward.
For each network (Testnet and Mainnet), this requirement applies to the nodes compatible with NU6.3 activation on that network. These nodes must advertise a network protocol version equal to or greater than the MIN_NETWORK_PROTOCOL_VERSION (NU6.3) for that activation.
Consensus rules from NU6.3 activation
These consensus rules apply to each transaction in a block that is mined at a height equal to or greater than the NU6.3 ACTIVATION_HEIGHT. The rules apply to all transaction versions.
With these rules, after NU6.3:
- Value in the Orchard pool can be spent, but no value can be added to it.
- Cross-address transfers in the Orchard pool are disabled.
The purpose of these rules is that the destination of newly created shielded value is the Ironwood pool.
A coinbase transaction must not contain any Orchard-pool Actions. That is, its Orchard component must be empty.
Every Orchard-pool Action must be created with cross-address transfers disabled. (That is, the value of the
enableCrossAddressbit is 0.)This restriction is enforced by the Action circuit verifying key. The verifying key is selected by consensus branch [zip-2006]. Thus, after NU6.3 activation, the restriction applies to Orchard-pool Actions in version 5 transactions and in version 6 transactions.
No new value can be added to the Orchard pool. For every transaction, \(\mathsf{v}^{\textit{OrchardPoolBalance}} \geq 0\). (Thus the encoded
valueBalanceOrchardis nonnegative.)Value can still be transferred out of the Orchard pool. This includes transfers across the turnstile into the Ironwood pool.
Changes to ZIP 209
ZIP 209 [zip-0209] is extended with an Ironwood chain value pool balance. As for the other shielded pool balances, the extended ZIP 209 has these requirements for the Ironwood chain value pool balance:
- The balance does not become negative.
- The sum of all chain value pool balances is not greater than \(\mathsf{MAX\_MONEY}\) zatoshis.
These changes are relative to the changes in ZIP 256 [zip-0256].
In the Terminology section of ZIP 209, after this paragraph:
The "Orchard chain value pool balance" for a given block chain is the negation of the sum of all
valueBalanceOrchardfields for transactions in the block chain. (Before NU5 has activated, the Orchard chain value pool balance is zero.)
add this paragraph:
The "Ironwood chain value pool balance" for a given block chain is the negation of the sum of all
valueBalanceIronwoodfields for transactions in the block chain. (Before NU6.3 has activated, the Ironwood chain value pool balance is zero.)
In the Specification section of ZIP 209, replace this text:
If any of the Sprout chain value pool balance, Sapling chain value pool balance, Orchard chain value pool balance, transparent chain value pool balance, or deferred development fund chain value pool balance would become negative in the block chain created as a result of accepting a block, then all nodes must reject the block as invalid.
Put this text in its place:
If the chain value pool balance for any of the Sprout, Sapling, Orchard, Ironwood, transparent, or deferred development fund pools would become negative in the block chain created as a result of accepting a block, then all nodes must reject the block as invalid.
Note: The paragraph immediately after this text contains a limit on the sum of "these chain value pool balances". In that paragraph, this reference includes the Ironwood chain value pool balance.
Changes to the Protocol Specification
Changes that correspond to the ZIP 209 changes above are necessary in § 4.17 ‘Chain Value Pool Balances’ [protocol-chainvalue]. With these changes, § 4.17 contains the definition of an Ironwood chain value pool balance. This balance is in addition to the balances for these existing pools:
- The Sprout pool
- The Sapling pool
- The Orchard pool
These changes are equivalent to the changes above. They are not given in full here.
Many changes are necessary in all parts of the specification. These changes have two purposes:
- To make a clear distinction between pools and protocols. (Some of these changes were done before, in version 2026.6.4.)
- To add the Ironwood pool as another use of the Orchard protocol.
These changes are also not given in full here.
These consensus rules are added. Each rule is the Ironwood-pool equivalent of an existing Orchard-pool rule (or Sapling-pool rule):
- The Ironwood-pool Action transfers of a transaction must be consistent with its
valueBalanceIronwoodvalue. (This is as forvalueBalanceOrchard.) - When the
anchorIronwoodfield exists, it must refer to the final Ironwood-pool treestate of some earlier block. (This is as foranchorOrchard.) The field exists when there are any Ironwood-pool Action descriptions. - A block must not include Ironwood-pool note commitments if, as a result, the Ironwood-pool note commitment tree has more leaf nodes than its capacity. The capacity is \(2^{\mathsf{MerkleDepth}^{\mathsf{Orchard}}}\) leaf nodes. (This is as for the Orchard pool.)
- Each Ironwood-pool output of a coinbase transaction that is decrypted to a note plaintext must have the note plaintext lead byte
0x03. (In the equivalent rule for the Sapling pool and the Orchard pool, the necessary value is0x02.)
Changes to ZIP 221
The history tree is a commitment to the chain history [zip-0221]. Ironwood metadata is added to this tree in exactly the same way that Orchard metadata was added at NU5. The calculation and the aggregation of the new fields are the same as for the equivalent ...Orchard... fields.
In the "Tree Node specification" section of ZIP 221, after field 14 nOrchardTxCount, add this text:
[NU6.3 onward]
hashEarliestIronwoodRoot
- Leaf node
- Calculated as the note commitment root of the final Ironwood treestate (similar to
hashEarliestOrchardRoot).- Internal or root node
- Inherited from the left child.
Serialized as
char[32].[NU6.3 onward]
hashLatestIronwoodRoot
- Leaf node
- Calculated as the note commitment root of the final Ironwood treestate (similar to
hashLatestOrchardRoot).- Internal or root node
- Inherited from the right child.
Serialized as
char[32].[NU6.3 onward]
nIronwoodTxCount
- Leaf node
- The number of transactions in the leaf block where
vActionsIronwoodis non-empty.- Internal or root node
- The sum of the
nIronwoodTxCountfield of both children.Serialized as
CompactSize uint.
Replace this text:
The fields marked "[NU5 onward]" are omitted before NU5 activation [zip-0252].
Each node, when serialized, is between 147 and 171 bytes long (between 212 and 244 bytes after NU5 activation). [...]
Put this text in its place:
The fields marked "[NU5 onward]" are omitted before NU5 activation [zip-0252]. The fields marked "[NU6.3 onward]" are omitted before NU6.3 activation.
Each node, when serialized, is between 147 and 171 bytes long (between 212 and 244 bytes after NU5 activation, and between 277 and 317 bytes after NU6.3 activation). [...]
These items of the pseudocode are extended:
- The node structure.
- The
serializefunction. - The
make_leaffunction. - The
make_parentfunction.
The new fields in these items are:
hashEarliestIronwoodRoothashLatestIronwoodRootnIronwoodTxCount
The extension is the same as the addition of the "# NU5 only" Orchard fields. The new fields are present if and only if NU6.3 is active. In internal nodes, each root is inherited from the left child or the right child, as in the field descriptions above. In internal nodes, the count is the sum of the counts of the children.
hashChainHistoryRoot is still the BLAKE2b-256 digest of the serialized root node. At NU6.3, the added node fields are the only cause of a change to its value. The hashBlockCommitments header field [zip-0244] has no other changes.
ZIP 2005 activation
ZIP 2005 [zip-2005] is activated at NU6.3 on each network. The Ironwood pool is created at NU6.3 activation. From that point onward, the format of every Ironwood-pool output note is the quantum-recoverable note plaintext format of ZIP 2005. This format has the lead byte 0x03.
Implementation support
The proposal is that zcashd does not implement the consensus changes for NU6.3. Thus the expectation is that zebra is the only full-validator implementation that can follow the consensus Zcash block chain from NU6.3 activation onward.
Backward compatibility
On each network, before the activation of the network upgrade, NU6.3 nodes and pre-NU6.3 nodes are compatible. They can connect to each other. But NU6.3 nodes prefer connections to other NU6.3 nodes. Thus pre-NU6.3 nodes are gradually disconnected in the period before activation.
After the network upgrade, pre-NU6.3 nodes can still accept the numerically larger protocol version of NU6.3 as valid. But NU6.3 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 2026.8.0 [NU6.3] or later
- [protocol-networks]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 3.12: Mainnet and Testnet
- [protocol-chainvalue]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3] or later. Section 4.17: Chain Value Pool Balances
- [zip-0200]
- ZIP 200: Network Upgrade Mechanism
- [zip-0201]
- ZIP 201: Network Peer Management for Overwinter
- [zip-0204]
- ZIP 204: Zcash P2P Network Protocol
- [zip-0209]
- ZIP 209: Prohibit Out-of-Range Chain Value Pool Balances
- [zip-0213]
- ZIP 213: Shielded Coinbase
- [zip-0221]
- ZIP 221: FlyClient - Consensus-Layer Changes
- [zip-0229]
- ZIP 229: Version 6 Transaction Format
- [zip-0244]
- ZIP 244: Transaction Identifier Non-Malleability
- [zip-0252]
- ZIP 252: Deployment of the NU5 Network Upgrade
- [zip-0256]
- ZIP 256: Deployment of Consensus Bug Fixes Between NU6.1 and NU6.2
- [zip-0318]
- ZIP 318: Orchard to Ironwood Migration
- [zip-0326]
- ZIP 326: NU6.3 Consequences for Wallets
- [zip-2005]
- ZIP 2005: Ironwood Quantum Recoverability
- [zip-2006]
- ZIP 2006: Restricting Transfers into the Orchard Pool