This page is the Simplified Technical English version of ZIP 2003. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 2003: Disallow version 4 transactions
ZIP: 2003 Title: Disallow version 4 transactions Owners: Daira-Emma Hopwood <daira@jacaranda.org> Status: Final Category: Consensus Created: 2024-10-31 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/825> Pull-Request: <https://github.com/zcash/zips/pull/927>
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].
In this document, the character § is used for references to sections of the Zcash Protocol Specification [protocol].
In this document, the terms "Mainnet" and "Testnet" have the definitions in § 3.12 ‘Mainnet and Testnet’ [protocol-networks].
Abstract
With this ZIP, all v4 transactions are invalid from NU7 onward. Thus this ZIP has an effect on each workflow that includes the creation of v4 transactions. Sprout workflows are only some of these workflows.
The v5 transaction format [zip-0225] was added in the NU5 network upgrade. The v6 format [zip-0229] was added in NU6.3. Sprout is not supported in either of these formats. Sprout transfers can only be represented in v4 transactions. Thus, with this ZIP, it is also not possible to spend Sprout funds.
This ZIP does not contain a proposal to make Sprout funds permanently unavailable. For example, it has no proposal to unissue or burn these funds. Thus two possibilities stay open in theory, if the Zcash community thinks that it is worthwhile:
- To make v4 transactions valid again.
- To add a different facility to get these funds back.
But possibly, Sprout funds never become spendable again.
Motivation
Zcash is a very complex protocol. Some of this complexity is from functions that are now obsolete.
The Sprout shielded protocol was the first large-scale deployment of general-purpose zero-knowledge proofs. But Sprout had long proving times and high memory requirements. Its practical use was limited by these problems. The Sapling and Orchard shielded protocols came after Sprout. They have large optimizations [cultivating-sapling] and new functions, for example viewing keys and diversified addresses. As a result, Sprout has almost no use at this time.
In the Sapling network upgrade, the proving system and the pairing-friendly curves of Sprout were changed. They became the same as those of the Sapling shielded protocol, that is, Groth16 and BLS12-381. Thus that part of the attack surface is shared between Sprout and Sapling. If the cryptography of Sprout has a weakness, a balance violation is possible. The possible size of such a violation is also limited by the “turnstile” mechanism of ZIP 209 [zip-0209].
But some parts of Sprout are not shared with Sapling. Examples are the JoinSplit circuit and the processing of Sprout nullifiers and note commitments. Before NU7, these parts are still a large load on the live paths for transaction acceptance.
An example is the verification of transactions that have Sprout JoinSplit descriptions. It is necessary to consider this verification for denial-of-service attacks against mempool processing and new-block processing. Because Sprout has almost no use, node implementations have little incentive to optimize the verification of Sprout. Thus such attacks can cause a higher cost than with optimized verification.
zcashd was deprecated just before the NU6.3 network upgrade. Before the deprecation, zcashd was the only maintained implementation that still supplied wallet functions for Sprout. Thus, after the deprecation, no maintained implementation supplied wallet functions for Sprout. Before NU7, it is still possible under the consensus rules to move Sprout funds. But the deprecation was, and is, another reason to give sufficient warning to the holders of Sprout funds. The warning is about the difficulty to get these funds back.
Privacy Implications
When value is moved out of the Sprout pool, the publicly visible chain value pool balance of that pool changes. This change is through the vpub_old and vpub_new fields [zip-0209]. Thus the amount that is moved by a transaction is visible. Also, the exit period can be short or badly coordinated. Then it can be easier to correlate transaction timing and distinctive amounts with particular holders.
The rule against v4 transactions is not itself a cause of additional public information about the notes that stay in Sprout. But with this rule, these notes cannot be spent, unless a mechanism to spend them is restored in a future consensus change.
Requirements
It must become possible to remove the complexity and the attack surface of Sprout from the Zcash specifications and node implementations.
Specification
In § 7.1.2 ‘Transaction Consensus Rules’ [protocol-txnconsensus], as of NU6.3, change this rule:
- [NU6.3 onward] The transaction version number MUST be 4 or 5 or 6.
Change it to these rules:
- [NU6.3 only, pre-NU7] The transaction version number MUST be 4 or 5 or 6.
- [NU7 onward] The transaction version number MUST be 5 or 6.
These changes apply to Mainnet and Testnet in the same way.
Interaction with the proposed Network Sustainability Mechanism
For clarity: the Sprout chain value pool balance at the activation of this ZIP stays issued. Thus this balance is included in \(\mathsf{IssuedSupply}\) for the calculations in Network Sustainability Mechanism ZIPs that have an effect on issuance. ZIP 237 [zip-0237] is one of these ZIPs. The definition of \(\mathsf{IssuedSupply}\) is in § 4.17 ‘Chain Value Pool Balances’ [protocol-chainvaluepoolbalances].
Deployment
This ZIP was deployed with NU7 [zip-0259].
Reference implementation
- Zebra: [zebra-9787] [zebra-11528]
- Zakura: [zakura-959]
Acknowledgements
The author thanks Jack Grigg and Kris Nuttycombe for the discussions that led to the submission of this ZIP. The author also thanks Conrado Gouvêa for the information that it was necessary to update this ZIP for the changes in NU6.3 and NU7. The author also thanks all the other persons whose work made it feasible to deprecate Sprout.
The author gives particular credit to four persons. During the development of Sapling, these persons were put under a unique kind of stress:
- Ariel Gabizon
- Sean Bowe
- Nathan Wilcox
- Zooko Wilcox
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-chainvaluepoolbalances]
- Zcash Protocol Specification, Version 2026.8.0 [NU6.3]. Section 4.17: Chain Value Pool Balances
- [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-0209]
- ZIP 209: Prohibit Out-of-Range Chain Value Pool Balances
- [zip-0225]
- ZIP 225: Version 5 Transaction Format
- [zip-0229]
- ZIP 229: Version 6 Transaction Format
- [zip-0237]
- ZIP 237: Network Sustainability Mechanism: Halving-Preserving Issuance
- [zip-0259]
- ZIP 259: Deployment of the NU7 Network Upgrade
- [cultivating-sapling]
- Cultivating Sapling: Faster zk-SNARKs. Sean Bowe, September 13, 2017.
- [zebra-9787]
- Zebra PR 9787: change(consensus): Implements draft ZIP 2003 for NU7 and uses Testnet network protocol versions on Regtest
- [zebra-11528]
- Zebra PR 11528: fix(consensus): complete ZIP 2003 transaction version rejection
- [zakura-959]
- Zakura PR 959: feat(consensus): disallow version 4 transactions at NU7