Zcash in Simplified Technical English

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

ZIP 229: Version 6 Transaction Format

ZIP: 229
Title: Version 6 Transaction Format
Owners: Daira-Emma Hopwood <daira@jacaranda.org>
        Kris Nuttycombe <kris@nutty.land>
        Dev Ojha <dev@valargroup.dev>
        Sean Bowe <sean@bowe.tech>
Status: Final
Category: Consensus
Created: 2026-06-13
License: MIT
Discussions-To: <https://github.com/zcash/zips/issues/1326>

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

The term "Recovery Protocol" has the same meaning as in [zip-2005].

The terms that follow have these meanings:

Orchard protocol (or Orchard shielded protocol)
The common cryptographic design for the Orchard pool and the Ironwood pool. The design includes these items, as used for these two pools:
  • The Pallas and Vesta curves.
  • The Sinsemilla hash.
  • The Action circuit, with the changes in [zip-2006].
  • The note construction.
  • The note commitment construction.
  • The nullifier construction.
  • The key constructions.
  • The note encryption, with the changes in [zip-2005].
Orchard pool (or Orchard shielded pool)
The value pool that was introduced by ZIP 224 [zip-0224]. This pool has these items of its own:
  • A note commitment tree.
  • An anchor.
  • A chain value pool balance.
Ironwood pool (or Ironwood shielded pool)
A new value pool of the Orchard protocol. This pool is new in this ZIP. It has these items of its own, different from the items of the Orchard pool:
  • A note commitment tree.
  • An anchor.
  • A chain value pool balance.

Abstract

This ZIP contains the definition of version 6 of the Zcash transaction format. The activation of this format is at NU6.3 [zip-0258].

The Ironwood shielded pool is new in NU6.3 [zip-0258]. This pool is an Orchard-protocol successor to the Orchard pool. The Ironwood pool has quantum recoverability [zip-2005]. From the start, its supply integrity has the support of formal verification work [Ironwood-book].

Thus a new transaction version is necessary. This version can hold an Ironwood component. The Ironwood component is a second Orchard-protocol shielded component. It commits to, and spends from, the Ironwood pool and not the Orchard pool.

The Orchard Action encoding and the Halo 2 proof system are used again with no changes. The circuit is also common to these pools. It has only small changes from the pre-NU6.3 circuit [zip-2006].

This ZIP contains the related changes to these items:

Address structures and address encodings stay the same with the addition of the Ironwood pool. At the protocol level, the authority to spend or view notes in both the Orchard and Ironwood pools comes from Orchard spending-key and viewing-key material.

But from NU6.3, this condition is enforced on each output to the Orchard pool: the output is sent to an Orchard-protocol-level address, and the transaction creator can authorize spends for that address. The intent is that the notes from a transfer between users are automatically in the Ironwood pool. The address restriction is a disincentive to economic activity between users in the Orchard pool. It is also an incentive for faster migration to the Ironwood pool.

This ZIP contains only the specification of the transaction format and its related hashing. The specification of the Action circuit changes that are necessary to restrict address usage in the Orchard pool is in [zip-2006]. The implications for wallets are discussed in [zip-0318] and [zip-0326]. The specification of the activation parameters is in the NU6.3 deployment ZIP [zip-0258].

Motivation

The description of the Orchard soundness vulnerability is in [zip-0257]. After the discovery and remediation of this vulnerability, the main purpose of the NU6.3 network upgrade is to increase confidence in the Zcash supply integrity.

With the turnstile mechanism [zip-0209], it is certain that the total ZEC supply is bounded. But a large part of ZEC was in the Orchard pool at the time of the remediation of this vulnerability. Thus more steps are necessary to make sure that there is confidence in the supply. The method is to migrate funds to a new pool.

All funds in the Ironwood pool are quantum-recoverable [zip-2005]. The existing Zcash shielded protocols depend on the hardness of finding discrete logarithms. An adversary that can find discrete logarithms (with quantum computers or with a different method) can steal or forge funds.

It can become necessary to disable these protocols to prevent such attacks. In that event, a Recovery Protocol can be used to recover funds from the Ironwood pool. This Recovery Protocol is expected to stay secure against discrete-log-breaking adversaries and quantum adversaries.

With this change alone, Zcash is not secure against attacks that use quantum computers. But this change is a necessary and large step toward that goal.

Recovery is not possible for funds that are still in these pools:

After the protocol of one of these pools is disabled, all such funds in that pool are inaccessible. To get the advantage of this change, we recommend that these funds are migrated to the Ironwood pool.

In the version 6 transaction format, the authorization structure is also different for all the supported shielded pools:

In this structure, anchors are part of the authorizing data, and not part of the effecting data. Thus a transaction can be pre-authorized. After the selection of an anchor, its proofs can be calculated independently. There are also more opportunities for parallelism in transaction creation.

Privacy Implications

With the turnstile mechanism, the amounts in each transaction that cross between pools are public. These amounts include the amounts that are migrated into the Ironwood pool. The full analysis of this is in [zip-0318].

There is no reason to believe that the soundness vulnerability of [zip-0257] made possible a compromise of key material for existing addresses. Separately from the soundness bug, we recommend address rotation because of the quantum privacy implications in [zip-2005].

Requirements

We recommend that the changes relative to v5 transactions are as small as possible.

The version 6 transaction format must be able to contain these components:

For the Ironwood component, the Orchard Action design and component encoding must be used again. The purpose is that the two components share the maximum possible part of the implementation.

When the Ironwood-pool component is present, these items must commit to it:

For these commitments, the personalizations must be different from the personalizations for the Orchard-pool component.

With the changes to the authorization structure, these operations must be possible for all the supported shielded pools:

When the data that is hashed at a node of the digest tree changes, the personalization for that node must be changed.

It must be possible to encode an indication in the flags fields of the Orchard-pool and Ironwood-pool components. The indication is about this restriction on outputs to the Orchard pool: each output uses a protocol-level address, and the transaction creator can authorize spends for that address. The indication has one value when the restriction applies, and a different value when the restriction does not apply.

Keystone is the one known hardware wallet with Orchard support. Keystone must continue to be able to sign Orchard to transparent unshielding transactions in the v5 transaction format. This must be possible with no firmware update.

Non-requirements

It is not necessary for the v6 transaction format to support these features of the withdrawn ZIP 230 [zip-0230]:

It is also not necessary for the v6 transaction format to support these features as planned for ZIP 248 [zip-0248]. The same applies to the other extensibility features that are planned for ZIP 248.

It is not necessary to prevent a collision of the transaction version number 6 with these documents:

Specification

Transaction Format

The encoding of a version 6 transaction is as follows. The fields up to and including the Orchard component are as in the version 5 format [zip-0225], except for the differences that are noted. The Ironwood component is new.

NoteBytesNameData TypeDescription
Common Transaction Fields (unchanged from v5)
\(4\)headeruint32The field contains:
  • The fOverwintered flag (bit 31, always set).
  • version (bits 30 .. 0). The value of version must be 6.
\(4\)nVersionGroupIduint32The version group ID. The value is nonzero. It is specified in § 7.1.2.
\(4\)nConsensusBranchIduint32The consensus branch ID. The value is nonzero. It is constrained in § 7.1.2.
\(4\)lock_timeuint32A Unix-epoch UTC time or a block height. It is encoded as in Bitcoin.
\(4\)nExpiryHeightuint32A block height in the range {1 .. 499999999}, or 0. After this block height, the transaction expires. If the value is 0, the transaction does not expire. Refer to [zip-0203].
Transparent Transaction Fields (unchanged from v5)
variestx_in_countcompactSizeThe number of transparent inputs in tx_in.
variestx_intx_inThe transparent inputs. They are encoded as in Bitcoin.
variestx_out_countcompactSizeThe number of transparent outputs in tx_out.
variestx_outtx_outThe transparent outputs. They are encoded as in Bitcoin.
Sapling Transaction Fields (unchanged from v5)
variesnSpendsSaplingcompactSizeThe number of Sapling Spend descriptions in vSpendsSapling.
\(96\,\cdot\) nSpendsSaplingvSpendsSaplingSpendDescriptionV5[nSpendsSapling]The Sapling Spend descriptions. They are encoded as in § 7.3 ‘Spend Description Encoding and Consensus’.
variesnOutputsSaplingcompactSizeThe number of Sapling Output descriptions in vOutputsSapling.
\(756\,\cdot\) nOutputsSaplingvOutputsSaplingOutputDescriptionV5[nOutputsSapling]The Sapling Output descriptions. They are encoded as in § 7.4 ‘Output Description Encoding and Consensus’.
†\(8\)valueBalanceSaplingint64The net value: Sapling Spends minus Outputs.
‡\(32\)anchorSaplingbyte[32]A root of the Sapling note commitment tree at a block height in the past.
\(192\,\cdot\) nSpendsSaplingvSpendProofsSaplingbyte[192 * nSpendsSapling]The encodings of the zk-SNARK proofs for each Sapling Spend.
\(64\,\cdot\) nSpendsSaplingvSpendAuthSigsSaplingbyte[64 * nSpendsSapling]The authorizing signatures for each Sapling Spend.
\(192\,\cdot\) nOutputsSaplingvOutputProofsSaplingbyte[192 * nOutputsSapling]The encodings of the zk-SNARK proofs for each Sapling Output.
†\(64\)bindingSigSaplingbyte[64]A Sapling binding signature on the SIGHASH transaction hash.
Orchard Transaction Fields
variesnActionsOrchardcompactSizeThe number of Orchard Action descriptions in vActionsOrchard.
\(820\,\cdot\) nActionsOrchardvActionsOrchardOrchardAction[nActionsOrchard]A sequence of Orchard Action descriptions. They are encoded as in § 7.5 ‘Action Description Encoding and Consensus’.
§\(1\)flagsOrchardbyteAn 8-bit value that is a set of flags. From LSB to MSB, the flags are:
  • enableSpends
  • enableOutputs
  • enableCrossAddress (new at NU6.3)
The remaining bits must be 0.
§\(8\)valueBalanceOrchardint64The net value: Orchard spends minus outputs.
§\(32\)anchorOrchardbyte[32]A root of the Orchard note commitment tree at a block height in the past.
§variessizeProofsOrchardcompactSizeThe length in bytes of proofsOrchard. The value is 2720 + 2272 * nActionsOrchard.
§sizeProofsOrchardproofsOrchardbyte[sizeProofsOrchard]The encoding of the aggregated zk-SNARK proofs for Orchard Actions.
\(64\,\cdot\) nActionsOrchardvSpendAuthSigsOrchardbyte[64 * nActionsOrchard]The authorizing signatures for each Orchard Action.
§\(64\)bindingSigOrchardbyte[64]An Orchard binding signature on the SIGHASH transaction hash.
Ironwood Transaction Fields (new)
variesnActionsIronwoodcompactSizeThe number of Ironwood Action descriptions in vActionsIronwood.
\(820\,\cdot\) nActionsIronwoodvActionsIronwoodOrchardAction[nActionsIronwood]A sequence of Ironwood Action descriptions. They have the same encoding as Orchard Actions (§ 7.5).
◊\(1\)flagsIronwoodbyteThe layout is the same as the layout of flagsOrchard, with enableCrossAddress at bit 2. The remaining bits must be 0.
◊\(8\)valueBalanceIronwoodint64The net value: Ironwood spends minus outputs.
◊\(32\)anchorIronwoodbyte[32]A root of the Ironwood note commitment tree at a block height in the past.
◊variessizeProofsIronwoodcompactSizeThe length in bytes of proofsIronwood. The value is 2720 + 2272 * nActionsIronwood.
◊sizeProofsIronwoodproofsIronwoodbyte[sizeProofsIronwood]The encoding of the aggregated zk-SNARK proofs for Ironwood Actions.
\(64\,\cdot\) nActionsIronwoodvSpendAuthSigsIronwoodbyte[64 * nActionsIronwood]The authorizing signatures for each Ironwood Action.
◊\(64\)bindingSigIronwoodbyte[64]An Ironwood binding signature on the SIGHASH transaction hash.

The fields with a mark in the Note column are present only on a condition:

NoteDescription
†valueBalanceSapling and bindingSigSapling are present if and only if nSpendsSapling + nOutputsSapling > 0. If valueBalanceSapling is not present, the value 0 is used for it.
‡anchorSapling is present if and only if nSpendsSapling > 0.
§These fields are present if and only if nActionsOrchard > 0:
  • flagsOrchard
  • valueBalanceOrchard
  • anchorOrchard
  • sizeProofsOrchard
  • proofsOrchard
  • bindingSigOrchard
If valueBalanceOrchard is not present, the value 0 is used for it.
◊These fields are present if and only if nActionsIronwood > 0:
  • flagsIronwood
  • valueBalanceIronwood
  • anchorIronwood
  • sizeProofsIronwood
  • proofsIronwood
  • bindingSigIronwood
If valueBalanceIronwood is not present, the value 0 is used for it.

The encoding of the transparent fields and the Sapling fields is the same as in version 5 [zip-0225]. Ironwood Action descriptions have the same OrchardAction encoding as Orchard Action descriptions. Each Ironwood-pool output note has the quantum-recoverable note plaintext format that is defined in ZIP 2005 [zip-2005]. (The lead byte of this format is 0x03.) No Orchard-pool output note has that format. This is the only difference between the two pools at the note level.

Two flagsOrchard bits have new names relative to version 5:

  • enableSpendsOrchard → enableSpends
  • enableOutputsOrchard → enableOutputs

In version 6, these bits and enableCrossAddress have the same meaning in flagsOrchard and in flagsIronwood. Thus the previous ...Orchard suffix can give an incorrect meaning.

Consensus Rules

For the version 6 transaction format, the changes below to the transaction consensus rules in § 7.1.2 'Transaction Consensus Rules' [protocol-txnconsensus] are necessary. These changes apply from NU6.3 activation.

The list does not include purely editorial generalizations. Examples are the replacement of Orchard pool with Orchard or Ironwood pool, and updates to cross-references.

  • Replace this rule:

    [Pre-NU6.3] The transaction version number MUST be 4 or 5.

    with this rule:

    [NU6.3 onward] The transaction version number MUST be 4 or 5 or 6.

  • Add this rule:

    [NU6.3 onward] If the transaction version number is 6 then the version group ID MUST be 0xD884B698.

  • Add this rule:

    [NU6.3 onward] If effectiveVersion \(\geq 6\), then nActionsIronwood MUST be less than \(2^{16}\).

  • Replace this rule:

    [NU5 onward] If effectiveVersion \(\geq 5\) then this condition MUST hold: tx_in_count \(> 0\) or nSpendsSapling \(> 0\) or (nActionsOrchard \(> 0\) and enableSpendsOrchard \(= 1\)).

    with these rules:

    [NU5, pre-NU6.3] If effectiveVersion \(= 5\) then this condition MUST hold: tx_in_count \(> 0\) or nSpendsSapling \(> 0\) or (nActionsOrchard \(> 0\) and enableSpendsOrchard \(= 1\)).

    [NU6.3 onward] If effectiveVersion \(\geq 6\) then this condition MUST hold: tx_in_count \(> 0\) or nSpendsSapling \(> 0\) or (nActionsOrchard \(> 0\) and enableSpendsOrchard \(= 1\)) or (nActionsIronwood \(> 0\) and enableSpendsIronwood \(= 1\)).

    Make the same change to the related output-side condition. In that condition, use these names in place of the input-side names:

    • tx_out_count in place of tx_in_count.
    • nOutputsSapling in place of nSpendsSapling.
    • enableOutputsOrchard in place of enableSpendsOrchard.
    • enableOutputsIronwood in place of enableSpendsIronwood.
  • Add this rule:

    [NU6.3 onward] If effectiveVersion \(\geq 6\) and nActionsIronwood \(> 0\), then at least one of enableSpendsIronwood and enableOutputsIronwood MUST be 1.

  • Add this rule, parallel to the Orchard-pool binding-signature rule:

    [NU6.3 onward] If effectiveVersion \(\geq 6\) and nActionsIronwood \(> 0\), then bindingSigIronwood MUST represent a valid signature, under the Ironwood pool's transaction binding validating key, of the SIGHASH transaction hash — with the binding validating key and SIGHASH as defined for the Ironwood pool in § 4.14 'Balance and Binding Signature (Orchard)'. As for the Orchard pool, validation of the R component of the signature prohibits non-canonical point encodings.

  • In the definition of the total output value of a coinbase transaction, replace this text:

    define the total output value of its coinbase transaction to be the total value in zatoshi of its transparent outputs, minus \(\mathsf{v}^{\textit{SaplingPoolBalance}}\), minus \(\mathsf{v}^{\textit{OrchardPoolBalance}}\), plus \(\mathsf{totalDeferredOutput}(\mathsf{height})\);

    with this text:

    define the total output value of its coinbase transaction to be the total value in zatoshi of its transparent outputs, minus \(\mathsf{v}^{\textit{SaplingPoolBalance}}\), minus \(\mathsf{v}^{\textit{OrchardPoolBalance}}\), minus \(\mathsf{v}^{\textit{IronwoodPoolBalance}}\), plus \(\mathsf{totalDeferredOutput}(\mathsf{height})\);

    For a coinbase transaction that has no Ironwood component, \(\mathsf{v}^{\textit{IronwoodPoolBalance}}\) is zero. Thus the rule stays the same for version 4 and version 5 coinbase transactions.

  • Add this rule:

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

  • Replace this rule:

    [NU5 onward] In a version 5 coinbase transaction, the enableSpendsOrchard flag MUST be 0.

    with this rule:

    [NU5 onward] In a version 5 or version 6 coinbase transaction, the enableSpendsOrchard flag MUST be 0.

  • Add this rule:

    [NU6.3 onward] In a version 6 coinbase transaction, the enableSpendsIronwood flag MUST be 0.

  • Replace this rule:

    [NU5 onward] In a version 5 transaction, the reserved bits 2..7 of the flagsOrchard field MUST be zero.

    with this rule:

    [NU5 onward] In a version 5 or version 6 transaction, the reserved bits 2..7 of the flagsOrchard field MUST be zero.

  • Add this rule:

    [NU6.3 onward] In a version 6 transaction, the reserved bits 3..7 of the flagsIronwood field MUST be zero.

The specification of the enableCrossAddress bit is in [zip-2006].

Note: Because of the reserved-bit rule above (bits 2..7), it is necessary that bit 2 of flagsOrchard is 0, independent of the transaction version. In a version 5 transaction, bit 2 is still reserved. In a version 6 transaction, bit 2 is the encoding of enableCrossAddress.

Bit 2 of flagsIronwood is the enableCrossAddress bit. The reserved bits of flagsIronwood are bits 3..7. From NU6.3, the cross-address restriction of the Orchard pool is enforced for the Actions of that pool, as specified in [zip-2006].

For the version 6 format, this ZIP also contains these rules:

  • The proofs in proofsOrchard correspond 1:1 to the elements of vActionsOrchard, in the same order.
  • The signatures in vSpendAuthSigsOrchard correspond 1:1 to the elements of vActionsOrchard, in the same order.
  • The proofs in proofsIronwood correspond 1:1 to the elements of vActionsIronwood, in the same order.
  • The signatures in vSpendAuthSigsIronwood correspond 1:1 to the elements of vActionsIronwood, in the same order.

(The conditional presence of the fields is in the format table above.)

From NU6.3 activation, transactions of these versions are all valid:

  • Version 4.
  • Version 5.
  • Version 6.

This ZIP contains the definition of the version 6 format only. The version 4 and version 5 formats stay the same.

The NU6.3 consensus rules on Orchard actions apply to all transaction versions. Specifically, the Orchard-protocol cross-address restriction is enforced for each Orchard-pool Action that is mined from NU6.3 [zip-2006]. Thus a version 5 transaction cannot be used to bypass the restriction.

Refer to [zip-0258] for more consensus requirements. These requirements apply to all transactions from NU6.3, for all transaction versions. This short summary of the requirements is not normative:

  • Coinbase transactions must have an empty Orchard component.
  • The enableCrossAddress bit of flagsOrchard must be 0.
  • \(\mathsf{v}^{\textit{OrchardPoolBalance}}\) must be nonnegative.

Transaction Identifiers, Auth Digests, and Signature Digests

These version 6 values are calculated as in ZIP 244 [zip-0244]:

  • Transaction identifiers (txids).
  • Authorizing-data commitments ("auth digests").
  • Signature digests.

There are two changes:

  • An Ironwood component digest is added.
  • For version 6, these anchors are moved from effecting data to authorizing data:
    • The Sapling anchor.
    • The Orchard anchor.
    • The Ironwood anchor.

The version 5 algorithm stays the same.

Ironwood component digest

The version 6 txid digest has one more child than the txid digest for v5 transactions [zip-0244-txiddigest]. This child is an Ironwood component digest. It is the last child, after the Orchard component digest:

txid_digest_v6 = BLAKE2b-256("ZcashTxHash_" || consensusBranchId,
                             header_digest || transparent_digest || sapling_digest_v6 ||
                             orchard_digest_v6 || ironwood_digest_v6)

The version 6 auth digest has one more child than the auth digest for v5 transactions [zip-0244-authorizingdatacommitment]. This child is an Ironwood auth digest. It is the last child, after the Orchard auth digest:

auth_digest_v6 = BLAKE2b-256("ZTxAuthHash_" || consensusBranchId,
                             transparent_auth_digest || sapling_auth_digest_v6 ||
                             orchard_auth_digest_v6 || ironwood_auth_digest_v6)

Anchor commitment (version 6)

In version 5, the Sapling anchor and the Orchard anchor are part of the effecting data:

  • The Sapling anchor is encoded redundantly as anchor in each sapling_spends_noncompact_digest.
  • The Orchard anchor is anchorOrchard in orchard_digest.

These anchors are committed to in txid_digest. The Sapling and Orchard auth digests commit only to proofs and signatures [zip-0244-authorizingdatacommitment].

In version 6, the anchor is part of the authorizing data for these components:

  • The Sapling component.
  • The Orchard component.
  • The Ironwood component.

For version 6 transactions, these are the changes relative to ZIP 244:

  • These digests do not include the anchor:
    • sapling_spends_noncompact_digest_v6
    • orchard_digest_v6
    • ironwood_digest_v6
  • These digests also commit to an anchor, after the existing fields:
    • sapling_auth_digest_v6 commits to anchorSapling.
    • orchard_auth_digest_v6 commits to anchorOrchard.
    • ironwood_auth_digest_v6 commits to anchorIronwood.
    As in the serialization, each anchor is present only when its component has a spend or an action that references it:
    • anchorSapling is present if and only if nSpendsSapling > 0.
    • anchorOrchard is present if and only if nActionsOrchard > 0.
    • anchorIronwood is present if and only if nActionsIronwood > 0.
    Specifically, a Sapling component with outputs and no spends commits to no anchorSapling. An example is a transparent-to-Sapling transfer.

With this change, the anchor can be updated with no change to the transaction identifier. (The new anchor is a more recent note commitment tree root.) The proofs still bind to the specific anchor that is used.

ironwood_digest_v6 and ironwood_auth_digest_v6 are calculated with the same structure as orchard_digest_v6 and orchard_auth_digest_v6. But each node has a 16-byte BLAKE2b-256 personalization that is specific to Ironwood.

Also, different personalizations are used for some Sapling and Orchard nodes. At these nodes, the directly hashed data is different, because the anchor commitments are moved to authorizing data. These personalizations are in this table:

Nodev5 personalizationv6 personalizationComment for v6
\(\hspace{22em}\) Sapling
sapling_digest[_v6]ZTxIdSaplingHashZTxIdSaplingHashNo direct change.
sapling_spends_digestZTxIdSSpendsHashZTxIdSSpendsHashNo change.
sapling_spends_compact_digestZTxIdSSpendCHashZTxIdSSpendCHashNo change.
sapling_spends_noncompact_digest[_v6]ZTxIdSSpendNHashZTxIdSSpendNH_v6Does not include anchor.
sapling_auth_digest[_v6]ZTxAuthSapliHashZTxAuthSapliH_v6Includes anchorSapling.
\(\hspace{22em}\) Orchard
orchard_digest[_v6]ZTxIdOrchardHashZTxIdOrchardH_v6Does not include anchorOrchard.
orchard_actions_compact_digestZTxIdOrcActCHashZTxIdOrcActCHashNo change.
orchard_actions_memos_digestZTxIdOrcActMHashZTxIdOrcActMHashNo change.
orchard_actions_noncompact_digestZTxIdOrcActNHashZTxIdOrcActNHashNo change.
orchard_auth_digest[_v6]ZTxAuthOrchaHashZTxAuthOrchaH_v6Includes anchorOrchard.
\(\hspace{22em}\) Ironwood
ironwood_digest_v6n/aZTxIdIronwd_H_v6Does not include anchorIronwood.
ironwood_actions_compact_digest_v6n/aZTxIdIrnActCH_v6
ironwood_actions_memos_digest_v6n/aZTxIdIrnActMH_v6
ironwood_actions_noncompact_digest_v6n/aZTxIdIrnActNH_v6
ironwood_auth_digest_v6n/aZTxAuthIrnwdH_v6Includes anchorIronwood.

A version 6 transaction can have no Ironwood actions. Then, as for Sapling and Orchard, these digests are the hashes of empty input:

  • ironwood_digest_v6 is the hash of empty input under the component personalization, that is, BLAKE2b-256("ZTxIdIronwd_H_v6", []).
  • ironwood_auth_digest_v6 is the hash of empty input under the auth personalization, that is, BLAKE2b-256("ZTxAuthIrnwdH_v6", []).

These values are different from the Orchard empty-component digests.

Summary of the resulting digest structure

In the trees below, (*) is the mark for a node that has a direct change relative to v5. (+) is the mark for a node that is added relative to v5.

This is the txid digest structure:

txid_digest_v6
├── header_digest
├── transparent_digest
│   ├── prevouts_digest
│   ├── sequence_digest
│   └── outputs_digest
├── sapling_digest_v6
│   ├── sapling_spends_digest_v6
│   │   ├── sapling_spends_compact_digest
│   │   └── sapling_spends_noncompact_digest_v6 (*)
│   │       ├── cv
│   │       └── rk
│   ├── sapling_outputs_digest
│   │   ├── sapling_outputs_compact_digest
│   │   ├── sapling_outputs_memos_digest
│   │   └── sapling_outputs_noncompact_digest
│   └── valueBalance
├── orchard_digest_v6 (*)
│   ├── orchard_actions_compact_digest
│   ├── orchard_actions_memos_digest
│   ├── orchard_actions_noncompact_digest
│   ├── flagsOrchard
│   └── valueBalanceOrchard
└── ironwood_digest_v6 (+)
    ├── ironwood_actions_compact_digest_v6
    ├── ironwood_actions_memos_digest_v6
    ├── ironwood_actions_noncompact_digest_v6
    ├── flagsIronwood
    └── valueBalanceIronwood

This is the auth digest structure:

auth_digest_v6
├── transparent_scripts_digest
├── sapling_auth_digest_v6 (*)
│   ├── vSpendProofsSapling
│   ├── vSpendAuthSigsSapling
│   ├── vOutputProofsSapling
│   ├── bindingSigSapling
│   └── anchorSapling (+)
├── orchard_auth_digest_v6 (*)
│   ├── proofsOrchard
│   ├── vSpendAuthSigsOrchard
│   ├── bindingSigOrchard
│   └── anchorOrchard (+)
└── ironwood_auth_digest_v6 (+)
    ├── proofsIronwood
    ├── vSpendAuthSigsIronwood
    ├── bindingSigIronwood
    └── anchorIronwood

Note: The nodes under each of these digests are present only if the related component is not empty:

  • sapling_digest_v6 and its auth_digest.
  • orchard_digest_v6 and its auth_digest.
  • ironwood_digest_v6 and its auth_digest.

Block Commitments

The hashAuthDataRoot component of hashBlockCommitments [zip-0244] includes the version 6 auth digest, with no more structural change. The version 6 auth digest now includes the Ironwood auth digest. Because of the change above, it also includes the anchors.

Rationale

The description of the Orchard soundness vulnerability is in [zip-0257]. After the discovery and remediation of this vulnerability, the main purpose of the NU6.3 network upgrade is to increase confidence in the Zcash supply integrity.

Because this motivation was urgent, an accelerated timeline was necessary. Thus the bar for the inclusion of a feature was high. Thus even fairly simple improvements were omitted from this upgrade. An example is [zip-2002]. It was "queued" for inclusion in the next update of the transaction format.

Reuse of the Orchard protocol with minimal changes

The Ironwood pool is carried as a second Orchard-protocol component, and no new shielded protocol is defined. Because of this design, the transaction-format surface and the implementation surface stay small. These items are inherited with no change:

  • The Action encoding.
  • The proving system.
  • The authorization.
  • The note encryption, except for the new note plaintext format that is defined in [zip-2005].

The pools are distinguished by these items, and not by separate circuits:

  • Their note commitment trees.
  • Their nullifier sets.
  • Their value pool balances.
  • Their component position.

Separate state

The Ironwood pool has these items of its own:

  • A note commitment tree.
  • An anchor.
  • A nullifier set.

Thus there is a state boundary between the Ironwood pool and the Orchard pool. With this boundary, the chain value pool balance of each pool can be accounted for independently.

enableCrossAddress polarity

The encoding of this flag is in the positive sense:

  • 1: cross-address transfers can occur. This is the normal case for Ironwood-pool actions.
  • 0: the outputs of an action are restricted to the same protocol-level address as the spend of the action.

Before NU6.3, bit 2 is reserved as 0.

This encoding is backward-compatible. After NU6.3, the restricted state is necessary for an Orchard-pool spend. This state is bit 2 = 0. Signers that treat bit 2 as a reserved-zero bit already produce exactly this value. The in-circuit constraint and the equivalent internal disableCrossAddress instance value are discussed in [zip-2006].

Deployment

This transaction format is deployed at NU6.3. The activation heights and the NU6.3 consensus branch ID are specified in [zip-0258]. The version 6 version group ID is specified in § 7.1.2 [protocol-txnconsensus].

Acknowledgements

We thank the developers of Penumbra [penumbra]. They showed the advantages when the note commitment tree anchor is part of the authorizing data, and not part of the effecting data.

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-txnconsensus]
Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 7.1.2: Transaction Consensus Rules
[zip-0200]
ZIP 200: Network Upgrade Mechanism
[zip-0203]
ZIP 203: Transaction Expiry
[zip-0209]
ZIP 209: Prohibit Out-of-Range Shielded Chain Value Pool Balances
[zip-0224]
ZIP 224: Orchard Shielded Protocol
[zip-0225]
ZIP 225: Version 5 Transaction Format
[zip-0230]
ZIP 230: Withdrawn Version 6 Transaction Format
[zip-0244]
ZIP 244: Transaction Identifier Non-Malleability
[zip-0244-txiddigest]
ZIP 244: Transaction Identifier Non-Malleability — TxId Digest
[zip-0244-authorizingdatacommitment]
ZIP 244: Transaction Identifier Non-Malleability — Authorizing Data Commitment
[zip-0248]
ZIP 248: Extensible Transaction Format (unmerged; PR at https://github.com/zcash/zips/pull/1156)
[zip-0252]
ZIP 252: Deployment of the NU5 Network Upgrade
[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]
ZIP 326: NU6.3 Consequences for Wallets
[zip-2002]
ZIP 2002: Explicit Fees
[zip-2005]
ZIP 2005: Ironwood Quantum Recoverability
[zip-2006]
ZIP 2006: Restricting Transfers into the Orchard Pool
[Ironwood-book]
The Ironwood Book
[penumbra]
The Penumbra Protocol