This page is the Simplified Technical English version of ZIP 211. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 211: Disabling Addition of New Value to the Sprout Chain Value Pool
ZIP: 211 Title: Disabling Addition of New Value to the Sprout Chain Value Pool Owners: Daira-Emma Hopwood <daira@jacaranda.org> Credits: Sean Bowe Status: Final Category: Consensus Created: 2019-03-29 License: MIT
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 same meaning as in ZIP 200. [zip-0200]
In this document, the "Sprout shielded protocol" is the shielded payment protocol that was defined at the launch of the Zcash network.
In this document, the "Sapling shielded protocol" is the shielded payment protocol that was added in the Sapling network upgrade. [zip-0205] [protocol]
In this document, the term "Sprout chain value pool balance" has the same meaning as in ZIP 209. [zip-0209]
Abstract
With this ZIP, it is not possible to add new value to the Sprout chain value pool balance. This is a step toward the ability to remove the Sprout shielded protocol and thus to decrease the total complexity and attack surface of Zcash.
Motivation
The first version of the Zcash network has the name Sprout. Sprout had a shielded payment protocol that was based relatively closely on the original Zerocash proposal. [zerocash]
The Sapling network upgrade [zip-0205] included significant improvements in efficiency and functionality for shielded transactions. The expectation is that, in time, Sapling will be used in the place of Sprout in shielded transactions.
The Sapling shielded protocol and the Sprout shielded protocol have different cryptographic designs. An adversary can possibly exploit any vulnerability in one design or the other. Thus support for the two protocols has more risk than support for only the newer Sapling shielded protocol.
For example, a vulnerability was found in the zero-knowledge proving system that Zcash used at first. With this vulnerability, counterfeiting was possible. [counterfeiting] This vulnerability was corrected in the Sapling network upgrade, also for Sprout shielded transactions. At the time of writing, we know of no other vulnerabilities. But it is not possible to be fully sure that there are no other cryptographic weaknesses.
Also, the Zcash specification and implementation have complexity and "technical debt", because it is necessary to support and test the two shielded payment protocols.
A first step to decrease this complexity and possible risk is to remove the ability to add to the Sprout chain value pool balance. It is still possible to extract value that is held in Sprout addresses and to send it to transparent addresses. It is also still possible to send that value to Sapling addresses with the migration tool. [zip-0308]
Specification
Consensus rule: From the applicable activation height, the vpub_old field of each JoinSplit description must be zero.
When this ZIP is activated, nodes and wallets must disable all facilities to create transactions that have both of these properties:
- One or more outputs to Sprout addresses.
- One or more inputs from non-Sprout addresses.
We recommend that this restriction is clear in user interfaces and in API documentation.
Notes:
- The requirement on wallets is intentionally a little stronger than the requirement of the consensus rule. It is possible to create a mixed transaction that has all of these properties:
- The transaction has inputs from Sprout addresses and from non-Sprout addresses.
- All
vpub_oldfields are zero. - The funds from Sprout inputs are enough to balance the Sprout outputs.
- The facility to send to Sprout addresses is optional for a specific node or wallet implementation. This applies also before the activation of this ZIP.
Rationale
For this design, no change to the JoinSplit circuit is necessary. Thus the risk of security regressions is as small as possible. Also, a new ceremony to generate circuit parameters is not necessary.
The necessary code changes are very small and simple, and it is easy to analyze their security.
During the development of this ZIP, alternative designs were considered. In these designs, some fields of a JoinSplit description are removed. These alternatives were rejected for these reasons:
- There were privacy concerns. With these alternatives, it is not possible to use internal change between JoinSplits, or change sent back to the input Sprout addresses, or both. Thus it is necessary to leak the total value of the input Sprout notes. (For some of the considered designs, it is necessary to leak the total value of the two Sprout inputs to each JoinSplit instead.) In the current design, the total value that is extracted from the Sprout value pool is leaked, and this leak cannot be prevented. But the sum of the values of specific subsets of notes is not leaked.
- For these alternatives, changes are necessary to the design of the Sprout to Sapling migration procedure that is described in [zip-0308].
- For these alternatives, a new transaction version is necessary.
Security and Privacy Considerations
The security motivations for this change are in the Motivation section. The privacy concerns that are the reason for the current design are in the Rationale section.
All implementations change their behavior at the same time, from the activation height of this ZIP. Thus there is no additional distinguisher between implementations.
Deployment
This ZIP is deployed with the Canopy network upgrade. [zip-0251]
Reference Implementation
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 2021.2.16 or later
- [zip-0200]
- ZIP 200: Network Upgrade Mechanism
- [zip-0205]
- ZIP 205: Deployment of the Sapling Network Upgrade
- [zip-0209]
- ZIP 209: Prohibit Out-of-Range Chain Value Pool Balances
- [zip-0251]
- ZIP 251: Deployment of the Canopy Network Upgrade
- [zip-0308]
- ZIP 308: Sprout to Sapling Migration
- [zerocash]
- Zerocash: Decentralized Anonymous Payments from Bitcoin (extended version)
- [counterfeiting]
- Zcash Counterfeiting Vulnerability Successfully Remediated