Zcash in Simplified Technical English

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

ZIP 2006: Restricting Transfers into the Orchard Pool

ZIP: 2006
Title: Restricting Transfers into the Orchard Pool
Owners: Daira-Emma Hopwood <daira@jacaranda.org>
Credits: Sean Bowe
         Schell Carl Scivally
         Jack Grigg
         Kris Nuttycombe
Status: Final
Category: Consensus
Created: 2025-06-21
License: MIT
Discussions-To: <https://github.com/zcash/zips/issues/1305>

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].

The character § is used for references to sections of the Zcash Protocol Specification [protocol-updated].

These terms have the definitions in ZIP 229 [zip-0229]:

The expanded receiver of an Orchard-protocol shielded payment address or note is the pair \((\mathsf{g_d}, \mathsf{pk_d})\). This pair contains the diversified base and the diversified transmission key of the address or note. These two items have the definitions in § 4.2.3 ‘Orchard Key Components’ [protocol-orchardkeycomponents].

Abstract

NU6.3 [zip-0258] has two restrictions. The purpose of these restrictions is to limit economic activity in the Orchard pool:

Thus the Orchard pool can still be spent from. This includes spends across the turnstile into the Ironwood pool. But the Orchard pool cannot be used to transfer value to an address if the sender does not hold the spending key of that address.

This ZIP contains these items:

Motivation

The Orchard Action circuit that was deployed before NU6.2 had a soundness vulnerability [zip-0257]. With this vulnerability, the creation of value in the Orchard pool was possible. The Ironwood pool is new in NU6.3. In the Ironwood pool, the Orchard protocol is used with a corrected circuit. Value is moved from the Orchard pool into the Ironwood pool subject to the "turnstile" checks on chain value pool balances. These checks are specified in ZIP 209 [zip-0209].

For these checks to give the desired assurances of balance integrity, it is necessary to direct newly created shielded value into the Ironwood pool. For the same purpose, we recommend that the only possible movement of value in the Orchard pool is out of that pool.

If users can still pay each other in the Orchard pool, it stays a working payment pool. Then any value that was created through the vulnerability can be in circulation in that pool, and it is never checked at the turnstile.

With the restrictions, new value cannot be added to the Orchard pool. Also, users cannot pay each other in that pool. Thus this circulation is not possible. But each holder can still move their own funds out of the pool.

Users can still rebalance note values in the Orchard pool. The purpose of a rebalance is to decrease the information that becomes visible when users migrate those funds to the Ironwood pool. This migration is specified in ZIP 318 [zip-0318].

Privacy Implications

Without the cross-address restriction, unrelated real spends and outputs can share Actions. Thus the minimum Action count is the maximum of the number of real spends and the number of real outputs. With the restriction, a real spend and a real output can share an Action only if they have the same expanded receiver. When no such pair is possible, the minimum Action count is the sum of those two numbers instead.

Thus the transaction size increases. Also, with the restriction, the transaction arity is hidden less well by spend/output pairing. Same-receiver pairing and additional dummy Actions are still possible. Thus, from the public Action count, it is not possible to know the exact numbers of real spends and real outputs. The restriction applies to all Orchard-pool Actions. Thus the increase in Action counts is not, by itself, a fingerprint of a specific wallet.

Because of this ZIP, users cannot pay each other in the Orchard pool. Thus users have a reason to transfer their funds out of that pool. For each such transfer, the net amount that leaves the pool is visible on-chain, whatever the destination. Thus, if all the balance of a wallet is transferred at one time, that balance can become visible. Also, the amounts and the times of transfers can be used to link the transfers.

With the restrictions, notes in the Orchard pool can still be rebalanced without a transfer across the turnstile. Amount-selection measures and timing measures for the migration to the Ironwood pool are in ZIP 318 [zip-0318]. The procedure to create the spend and output Actions that are necessary for a rebalance under the cross-address restriction is in ZIP 326 [zip-0326-orchard].

Requirements

Specification

The enableCrossAddress flag

Each Action has a flag \(\mathsf{enableCrossAddress} \;{\small ⦂}\; \mathbb{B}\). This flag is set to let the expanded receivers of the output note and the input note of the Action be different. The value of \(\mathsf{enableCrossAddress}\) is the same for all Actions of a bundle. This value is encoded one time for each bundle, in bit 2 of the flags byte of the bundle:

  • In the flagsIronwood field of a version 6 transaction, enableCrossAddress for the Ironwood-pool Actions is encoded in bit 2 [zip-0229].
  • In the flagsOrchard field, bit 2 must be 0 for all transaction versions. In a version 5 transaction, this bit is still reserved and must be 0. In a version 6 transaction, enableCrossAddress is encoded in this bit, and the bit must be 0.

For blocks before NU6.3 activation, cross-address transfers are always valid: \(\mathsf{enableCrossAddress}\) is taken to be \(1\) for each Action. From NU6.3 activation, \(\mathsf{enableCrossAddress}\) is bit 2 of the flags byte for each pool. Thus it is \(0\) for each Orchard-pool Action.

Action statement

For a given Orchard-protocol Action description, let \(\mathsf{disableCrossAddress} = 1 - \mathsf{enableCrossAddress}\).

From NU6.3 activation, the Action statement has an additional primary input \(\mathsf{disableCrossAddress} \;{\small ⦂}\; \mathbb{B}\), after \(\mathsf{enableOutputs}\). The Action statement also has this condition:

Cross-address restriction: \(\mathsf{disableCrossAddress} = 0\), or \(\mathsf{g_d^{old}} = \mathsf{g_d^{new}}\) and \(\mathsf{pk_d^{old}} = \mathsf{pk_d^{new}}\).

The auxiliary input of the Action statement already includes the expanded receiver of the spent note, \((\mathsf{g_d^{old}}, \mathsf{pk_d^{old}})\). It also includes the expanded receiver of the output note, \((\mathsf{g_d^{new}}, \mathsf{pk_d^{new}})\).

From NU6.3 activation, one circuit is used for the Actions of the Orchard pool and for the Actions of the Ironwood pool. One verifying key is also used for these Actions. This key is identified as OrchardCircuitVersion::PostNu6_3. The two pools have different consensus restrictions on the value of \(\mathsf{enableCrossAddress}\). The circuit is the same for the two pools.

Consensus rules

The consensus rules that follow apply from NU6.3 activation to each transaction, for all transaction versions:

  • The verifying key for the proof of an Action description must be the key that is identified as OrchardCircuitVersion::PostNu6_3. The proof must be valid for the primary input that includes \(\mathsf{disableCrossAddress}\).
  • A coinbase transaction must not contain any Orchard-pool Actions.
  • \(\mathsf{v^{balanceOrchard}}\) must be nonnegative. (When the valueBalanceOrchard field is present, \(\mathsf{v^{balanceOrchard}}\) is encoded as that field.) That is, in a transaction, value can be taken from the Orchard pool, but value must not be added to it.

These rules and the rule that bit 2 of flagsOrchard is 0 have these two results after NU6.3 activation:

  • No value is added to the Orchard pool.
  • The output note of each Orchard-pool Action is sent to the expanded receiver of the note that is spent in that Action.

Requirements on wallets

A dummy output note that is necessary for an Action with \(\mathsf{enableCrossAddress} = 0\) must be sent to the expanded receiver of the Action's spent note. That note is sent there in the place of a random address. (This spent note can itself be a dummy note.) Also, a dummy spent note that is paired with a non-dummy output note must be at the expanded receiver of that output note.

After NU6.3 activation, wallets spend from the Orchard pool, and rebalance notes in it, as specified in ZIP 326 [zip-0326-orchard]. Two of the specified items are as follows:

  • In an Action with an output note that holds value, that output note is paired with a dummy spent note at the same expanded receiver.
  • In an Action with a real spent note, the dummy output note has a random note ciphertext.

Changes to the Protocol Specification

This section is a set of changes relative to version 2026.7.0 of the protocol specification [protocol-base]. These changes are applied in version 2026.8.0 [protocol-updated]. Each change applies from NU6.3 activation. In the specification, each change is marked as a change from NU6.3 activation.

§ 4.6 ‘Action Descriptions’

Add this text:

Let \(\mathsf{pool} \;{\small ⦂}\; \{\mathsf{OrchardPool}, \mathsf{IronwoodPool}\}\) be the pool of this Action description.

Define an expanded receiver as in ZIP 2006, i.e. \((\mathsf{g_d}, \mathsf{pk_d})\) for a shielded payment address.

Add \(\mathsf{enableCrossAddress}\) to the components of an Action description, after \(\mathsf{enableOutputs}\). Use this description:

\(\mathsf{enableCrossAddress} \;{\small ⦂}\; \mathbb{B}\) is a flag that is set in order to enable the expanded receiver of the output note to be different from the expanded receiver of the input note in this Action.

In the description of the proof, append \(\mathsf{disableCrossAddress}\) to the primary input. Do this also in the consensus rule about the validity of the proof. Here, \(\mathsf{disableCrossAddress} = 1 - \mathsf{enableCrossAddress}\).

In the note about the components that are encoded one time for each pool, add \(\mathsf{enableCrossAddress}\) to the list of components.

Add this consensus rule:

[NU6.3 onward] \(\mathsf{vk}\) MUST be the verifying key identified by OrchardCircuitVersion::PostNu6_3.

§ 4.8.3 ‘Dummy Notes (Orchard)’

Find the steps that create the spend-related fields for a dummy Orchard-pool input note. After these steps, add this text:

[NU6.3 onward] If \(\mathsf{enableCrossAddress} = 0\) for the Action, and its output note is not a dummy note, then the first two steps are replaced: \((\mathsf{ak}, \mathsf{nk}, \mathsf{rivk})\) and \((\mathsf{d}, \mathsf{pk_d})\) are instead the full viewing key and diversified payment address of the output note's recipient, and the spend authorization signature for the Action is made with the corresponding spend authorizing key.

Find the paragraph with the statement that a dummy Orchard-pool output note is sent to a random shielded payment address. After this paragraph, add this text:

[NU6.3 onward] If \(\mathsf{enableCrossAddress} = 0\) for the Action, the dummy output note is instead sent to the expanded receiver of the Action's spent note. If the spent note is not a dummy note, the transmitted note ciphertext of the dummy output note is filled with random bytes rather than being an encryption of its note plaintext. [zip-0326-orchard]

§ 4.18.4 ‘Action Statement (Orchard)’

Append this text to the primary input:

[NU6.3 onward] \(\mathsf{disableCrossAddress} \;{\small ⦂}\; \mathbb{B}\)

In the encoding of the primary input, append \(\mathsf{disableCrossAddress} \pmod{q_{\mathbb{P}}}\) to the current sequence of nine elements. From NU6.3 onward, the result is a sequence of type \(\mathbb{F}_{q_{\mathbb{P}}}^{10}\). Put the qualifier "[Pre-NU6.3]" on the current encoding of nine elements.

After the "Enable output flag" condition, add this text:

Cross-address restriction [NU6.3 onward]: \(\mathsf{disableCrossAddress} = 0\), or \(\mathsf{g_d^{old}} = \mathsf{g_d^{new}}\) and \(\mathsf{pk_d^{old}} = \mathsf{pk_d^{new}}\).

§ 7.1 ‘Transaction Encoding and Consensus’

Find the combined table of the version 5 and version 6 transaction formats. In the Description column for flagsOrchard, replace this list:

  • enableSpendsOrchard flag (bit \(0\))
  • enableOutputsOrchard flag (bit \(1\))
  • Reserved, zeros (bits \(2..7\)).

Put this list in its place:

  • enableSpends flag (bit \(0\))
  • enableOutputs flag (bit \(1\))
  • Bit \(2\): reserved (v5) or enableCrossAddress (v6), always \(0\)
  • Reserved, zeros (bits \(3..7\)).

The flagsIronwood field is only in version 6. This field was added by ZIP 229 [zip-0229]. In the Description column for flagsIronwood, replace this list:

  • enableSpendsIronwood flag (bit \(0\))
  • enableOutputsIronwood flag (bit \(1\))
  • Reserved, zeros (bits \(2..7\)).

Put this list in its place:

  • enableSpends flag (bit \(0\))
  • enableOutputs flag (bit \(1\))
  • enableCrossAddress flag (bit \(2\))
  • Reserved, zeros (bits \(3..7\)).

§ 7.1.2 ‘Transaction Consensus Rules’

Add this text:

[NU6.3 onward] A coinbase transaction MUST NOT have any Orchard-pool Action descriptions.

[NU6.3 onward] \(\mathsf{v^{balanceOrchard}}\) MUST be nonnegative.

Find the rule that the reserved bits \(2..7\) of the flagsOrchard field must be zero. After this rule, add this text:

[NU6.3 onward] In a version 6 transaction, bit 2 of flagsOrchard encodes \(\mathsf{enableCrossAddress}\) for the Orchard-pool Actions; it is covered by the preceding rule, and so is \(0\).

Changes to ZIPs

ZIP 229

In the Consensus Rules section, replace this text:

Note that the reserved-bit rules above leave bit 2 of flagsOrchard reserved as 0 (bits 2..7), while bit 2 of flagsIronwood is the enableCrossAddress bit (reserved bits 3..7); the Orchard pool's cross-address restriction is enforced for its Actions from NU6.3 onward as specified in [ZIP 2006].

Put this text in its place:

Note that bit 2 of flagsOrchard is required to be 0 by the reserved-bit rule above (bits 2..7), independent of the transaction version: in a version 5 transaction it is still reserved, and in a version 6 transaction it encodes enableCrossAddress. Bit 2 of flagsIronwood is the enableCrossAddress bit (reserved bits 3..7). The Orchard pool's cross-address restriction is enforced for its Actions from NU6.3 onward as specified in [ZIP 2006].

Rationale

Polarity of the flag

The flag is encoded in the "enabled" sense. Bit 2 is 1 when cross-address transfers are possible. This is the usual case for the Ironwood pool. With the opposite sense, it is necessary to set bit 2 to 1 in a post-NU6.3 Orchard-pool spend. Then signers that treat bit 2 as a reserved zero bit cannot create valid Orchard-pool spends. An example of such a signer is hardware wallet firmware that is not upgraded.

In the "enabled" sense, the restricted state is bit 2 = 0. This value is exactly the value that such signers already set.

In the circuit, the primary input is the negated value \(\mathsf{disableCrossAddress} = 1 - \mathsf{enableCrossAddress}\). Then a condition of the form "\(\mathsf{disableCrossAddress} = 0\) or \(a = b\)" is enforced directly by the constraint \(\mathsf{disableCrossAddress} \cdot (a - b) = 0\).

One circuit for both pools

From NU6.3 activation, the same circuit and the same verifying key are used for the Orchard pool and the Ironwood pool. The two pools are different in these items:

  • Their bundles.
  • Their note commitment trees.
  • Their nullifier sets.
  • Their chain value pools.
  • The value of \(\mathsf{enableCrossAddress}\).

With this design, a separate circuit for the restricted pool is not necessary. Also, with this design, similar restrictions on the Ironwood pool stay possible in the future, if there is a reason for them. This design is intentionally similar to the design of the enableSpends and enableOutputs flags.

Comparing both coordinates

In the circuit, the points of the expanded receivers are witnessed in affine coordinates. The condition is enforced for each coordinate. For each \(\mathsf{P} \in \{\mathsf{g_d}, \mathsf{pk_d}\}\) and each coordinate \(\mathsf{c} \in \{x, y\}\), the constraint is \(\mathsf{disableCrossAddress} \cdot (\mathsf{c}(\mathsf{P^{old}}) - \mathsf{c}(\mathsf{P^{new}})) = 0\). The two coordinates are necessary.

Restricting value as well as addresses

With only the cross-address restriction, new value can still be added to the Orchard pool. The cause is that value can be sent in an Action to the address of the spent note of that Action. That path is closed by these two rules:

  • The rule that \(\mathsf{v^{balanceOrchard}}\) is nonnegative.
  • The rule that coinbase transactions have no Orchard-pool Actions.

Deployment

This ZIP was deployed with NU6.3 [zip-0258]. NU6.3 was activated on Mainnet at block height 3428143.

Reference implementation

Version 0.16.0 of the orchard crate [orchard-0.16.0] implements these items:

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-base]
Zcash Protocol Specification, Version 2026.7.0 [NU6.2]
[protocol-updated]
Zcash Protocol Specification, Version 2026.8.0 [NU6.3]
[protocol-orchardkeycomponents]
Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 4.2.3: Orchard Key Components
[zip-0200]
ZIP 200: Network Upgrade Mechanism
[zip-0209]
ZIP 209: Prohibit Out-of-Range Chain Value Pool Balances
[zip-0229]
ZIP 229: Version 6 Transaction Format
[zip-0257]
ZIP 257: Deployment of the Orchard Temporary Vulnerability Mitigation and NU6.2 Network Upgrade
[zip-0258]
ZIP 258: Deployment of the NU6.3 Network Upgrade
[zip-0318]
ZIP 318: Orchard to Ironwood Migration
[zip-0326-orchard]
ZIP 326: NU6.3 Consequences for Wallets, section "Spending from and rebalancing within the Orchard pool"
[orchard-0.16.0]
orchard crate, version 0.16.0