This page is the Simplified Technical English version of ZIP 233. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 233: Network Sustainability Mechanism: Removing Funds From Circulation
ZIP: 233
Title: Network Sustainability Mechanism: Removing Funds From Circulation
Owners: Jason McGee <jason@shieldedlabs.net>
Zooko Wilcox <zooko@shieldedlabs.net>
Mark Henderson <mark@shieldedlabs.net>
Tomek Piotrowski <tomek@eiger.co>
Mariusz Pilarek <mariusz@eiger.co>
Paul Dann <paul@eiger.co>
Original-Authors: Nathan Wilcox
Credits:
Status: Draft
Category: Consensus / Ecosystem
Created: 2023-08-16
License: BSD-2-Clause
Discussions-To: <https://github.com/zcash/zips/issues/922>
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 meaning in ZIP 200 [zip-0200].
In a reference to a section of the Zcash Protocol Specification [protocol], the character § is before the section number.
The terms “Mainnet” and “Testnet” have the meaning in § 3.12 ‘Mainnet and Testnet’ [protocol-networks].
- ZEC/TAZ
- The native currency of Zcash on a given network. That is, ZEC on Mainnet and TAZ on Testnet.
- Block Subsidy
- The algorithmic issuance of ZEC/TAZ when a block is created, as defined by consensus. The block subsidy is split between the miner and Funding Streams.
- Issuance
- The method for ZEC/TAZ to become available for circulation on the network.
TODO (in the source document): There is a possible conflict of terms between this definition of issuance and the definition of issuance in ZIP 227.
\(\mathsf{MAX\_MONEY}\) is the total ZEC/TAZ supply cap in zatoshi. Its definition is in § 5.3 ‘Constants’ [protocol-constants]. This cap is equal to 21,000,000 ZEC. This value is slightly larger than the supply cap for the current issuance mechanism. But it is the value in existing critical consensus checks.
Abstract
This ZIP contains a proposal for a mechanism to voluntarily remove funds entirely from circulation on the network. The explicit intent of this removal is that the funds will be returned to circulation through future block subsidies. The intent is not a permanent destruction of the funds, and not a reserve of the funds for discretionary use.
This mechanism and ZIPs 235 [zip-0235] and 237 [zip-0237] together are a long-term strategy for the sustainability of the network. We will use the name “Network Sustainability Mechanism” for the combined effects of these three ZIPs.
Motivation
The purpose of this mechanism is to address concerns about the sustainability of the network design that Bitcoin-like systems share:
- Long Term Consensus Sustainability: With this mechanism, funds can be removed from circulation. Thus it becomes possible to create “headroom” between the chain value and \(\mathsf{MAX\_MONEY}\). This is necessary groundwork for an extension of the block subsidy system. At this time, the block subsidy system has a clear final end date. The intent is that removed funds will be automatically and algorithmically reissued through future block subsidies. The purpose of this reissue is to sustain the long-term security budget of the network. This intent applies if all three ZIPs of the Network Sustainability Mechanism are deployed in the same network upgrade or if they are not.
- Benefits to ZEC Holders: When funds are removed from circulation, the circulating supply of ZEC decreases. This decrease can possibly be a factor in an increase in the value of the remaining ZEC. To that extent, it is possible to argue that the removal is a benefit to network users in proportion to their holdings. For this benefit, the users do not have to opt into any scheme. Also, the users do not get these items with the benefit:
- extra risk
- active oversight
- accounting complexity.
Privacy Implications
With ZIP 233, there is a new type of transparent transaction event. Chain observers can fully see this event. The event is linked to other events in the transaction.
The removal of funds from circulation is a possible distinguisher. Transactions with an intentional removal of funds from circulation are probably a small fraction of Zcash transactions. Thus this distinguisher will be another tool for adversaries. Adversaries can use it to segment the users of the network.
Requirements
- With the mechanism, users can remove funds from the circulating supply. Each removal event is explicitly specified in its transaction.
- The process is publicly auditable. Thus network participants can verify the amount and the occurrence of funds removed from circulation.
Specification
Changes to ZIP 248
In this ZIP, we propose to register bundle type 6 variant 0 (“ZIP 233 NSM field”) in the registry of v7 transaction bundle types. The definition of this registry is in ZIP 248 [zip-0248].
| BundleType | BundleVariant | mValuePoolDeltas | mEffectBundles | mAuthBundles |
|---|---|---|---|---|
| 6 | 0 | ✅ | ❌ | ❌ |
The NSM bundle has no effecting data and no authorizing data. The only representation of the amount to remove from circulation is an entry in mValuePoolDeltas with bundleType = 6.
NSM Amount
When the mValuePoolDeltas map contains an entry with bundleType = 6, funds are removed from circulation by the transaction. The value field of the entry must be nonpositive. The negation of this value is denoted \(\mathsf{zip233\_amount}\). This negation is the value in zatoshis that is removed from circulation when the transaction is mined. If no such entry is present, \(\mathsf{zip233\_amount}\) is defined to be 0. For v6 transactions, \(\mathsf{zip233\_amount}\) is defined to be 0.
The NSM bundle has an effect on the transparent transaction value pool. This effect is not an output that is produced in any chain value pool. When the transaction is applied to the global chain state, \(\mathsf{zip233\_amount}\) is subtracted from the issued supply. This amount is unavailable for circulation on the network at least until the end of the block where the transaction is mined.
Changes to ZIP 237
In this ZIP, we propose to register the mechanism for removal from circulation that follows. The registration is in the list of ZIP 237 [zip-0237]:
| Mechanism | Source |
|---|---|
| Transaction field | \(\mathsf{NSMFields}(\mathsf{height})\) |
\[\mathsf{NSMFields}(\mathsf{height}) := \sum_{i=0} \mathsf{block}[\mathsf{height}].\mathsf{vtx}[i].\mathsf{zip233\_amount}\]
Changes to the Zcash Protocol Specification
Let \(\mathsf{NSMBundleId} = 6.\)
Change § 3.4 'Transactions and Treestates' [protocol-transactions]. Add these consensus rules:
- [NU7 onward] If \(\mathsf{mValuePoolDeltas}[\mathsf{NSMBundleId}]\) is present, its value must be nonpositive. The absolute value of this value is \(\mathsf{zip233\_amount}\).
- [NU7 onward] No output is produced in any chain value pool as a result of \(\mathsf{zip233\_amount}\).
In § 7.1 'Transaction Encoding and Consensus' [protocol-txnconsensus], add this rule:
[NU7 onward] \(\mathsf{zip233\_amount}\) must be in the range \(\{ 0 .. \mathsf{MAX\_MONEY} \}\).
In § 7.1.2 'Transaction Consensus Rules' [protocol-txnconsensus], change the definition of the total output value of a coinbase transaction. Add the \(\mathsf{zip233\_amount}\) of that transaction to the definition. The changed definition is:
Define the total output value of its coinbase transaction to be the result of this calculation:
- the total value in zatoshis of its transparent outputs,
- minus \(\mathsf{v}^{\textit{SaplingPoolBalance}}\),
- minus \(\mathsf{v}^{\textit{OrchardPoolBalance}}\),
- minus \(\mathsf{v}^{\textit{IronwoodPoolBalance}}\),
- plus \(\mathsf{totalDeferredOutput}(\mathsf{height})\),
- plus \(\mathsf{zip233\_amount}\).
Each shielded balancing value and \(\mathsf{totalDeferredOutput}\) is zero before the corresponding pool is activated. For pre-v7 transactions, \(\mathsf{zip233\_amount}\) in this definition is zero.
The definition of the total input value stays the same. The existing rules for the comparison of the total output value with the total input value also stay the same. When \(\mathsf{zip233\_amount}\) is added, the value removed from circulation is counted as consumed. This is true, although no output in a chain value pool is produced for this value.
Modifications to Digest Algorithms
\(\mathsf{zip233\_amount}\) is committed to in the transaction identifier through value_pool_deltas_digest. It is also committed to in the variant 0 signature digest through the txid_digest that is supplied to that digest. The definitions of these digests are in ZIP 248 [zip-0248].
The entry of the NSM bundle is included in that commitment for all values of the hash_type of the transparent signature.
The NSM bundle (bundle type 6) has no effecting data and no authorizing data. Thus its only contribution to these digests is through its entry in mValuePoolDeltas.
Applicability
All of these changes apply in the same way to Mainnet and to Testnet.
Rationale
Each technical decision in this ZIP is a balance between two items: the necessary robustness of the NSM mechanics, and the simplicity of implementation.
New transaction field for amount to remove from circulation
With an explicit value, the funds to remove from circulation and the transaction fee are clearly different. Also, because the value is explicit, any arithmetic flaws in any implementations are more likely to be observed and caught immediately.
Deployment
This ZIP is not deployed in Network Upgrade 7 [zip-0259]. It is proposed for activation in a later network upgrade.
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 2025.6.2 [NU6.1] or later
- [protocol-transactions]
- Zcash Protocol Specification, Version 2025.6.2 [NU6.1]. Section 3.4: Transactions And Treestates
- [protocol-networks]
- Zcash Protocol Specification, Version 2025.6.2 [NU6.1]. Section 3.12: Mainnet and Testnet
- [protocol-constants]
- Zcash Protocol Specification, Version 2025.6.2 [NU6.1]. Section 5.3: Constants
- [protocol-txnconsensus]
- Zcash Protocol Specification, Version 2025.6.2 [NU6.1]. Section 7.1.2 Transaction Consensus Rules
- [zip-0200]
- ZIP 200: Network Upgrade Mechanism
- [zip-0235]
- ZIP 235: Remove 60% of Transaction Fees From Circulation
- [zip-0237]
- ZIP 237: Network Sustainability Mechanism: Halving-Preserving Issuance
- [zip-0248]
- ZIP 248: Extensible Transaction Format
- [zip-0259]
- ZIP 259: Deployment of the NU7 Network Upgrade