This page is the Simplified Technical English version of ZIP 2009. The source ZIP is the normative text. Read the writing rules to understand the marked words.
ZIP 2009: Reduce Marginal Fee to 1000 Zatoshis and Raise the Weight Ratio Cap to 10
ZIP: 2009 Title: Reduce Marginal Fee to 1000 Zatoshis and Raise the Weight Ratio Cap to 10 Owners: Mark Henderson <mark@shieldedlabs.net> Status: Proposed Category: Standards / Wallet Updates: ZIP 317 Created: 2026-04-06 License: MIT Discussions-To: <https://github.com/zcash/zips/issues/1388> Pull-Request: <https://github.com/zcash/zips/pull/1352>
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 fee terms have the same meaning as in ZIP 317 [zip-0317]. The term "zatoshi" has the same meaning as in the Zcash protocol specification [protocol].
Abstract
This ZIP contains two changes to ZIP 317 [zip-0317]:
- The \(\mathit{marginal\_fee}\) of ZIP 317 decreases from 5,000 to 1,000 zatoshis per logical action. Thus the minimum conventional transaction fee decreases from 10,000 to 2,000 zatoshis.
- The \(\mathit{weight\_ratio\_cap}\) in the block template algorithm of ZIP 317 increases from 4 to 10. With this increase, the fee decrease has a smaller effect on the range.
No other part of ZIP 317 changes.
Motivation
The fee of ZIP 317 was set in late 2022. At that time, ZEC was approximately USD 30, and the minimum fee of 10,000 zatoshis cost approximately USD 0.0030. The fee is a fixed number of zatoshis. Thus, when the price increased, the fee increased also. At approximately USD 1,300 (the price on 2026-10-21), the minimum fee costs approximately USD 0.13.
With a \(\mathit{marginal\_fee}\) of 1,000, the minimum fee is 2,000 zatoshis (approximately USD 0.026). After a 5x decrease, the minimum fee is still approximately 8.7 times its cost when ZEC was approximately USD 30. The minimum fee costs less than the 2022 fee only if ZEC decreases to less than approximately USD 150.
Also, \(\mathit{weight\_ratio\_cap}\) is a multiple of the conventional transaction fee. Thus, when \(\mathit{marginal\_fee}\) decreases, the range of fees that have an effect on inclusion decreases from 10,000 - 40,000 zatoshis to 2,000 - 8,000. When \(\mathit{weight\_ratio\_cap}\) increases to 10, that range increases to 2,000 - 20,000. This range is still below the maximum of today. With this increase, the transactions from wallets that do not have the update yet are not clamped at the cap. These wallets pay 5x the new conventional transaction fee.
Privacy Implications
Privacy: If wallets change to the new fee at different times, the wallet implementation that created the transaction can be identified from the fee. To keep that time window short, we recommend that wallets change at the activation height in Deployment, and not at the time of the release.
Specification
Changes to ZIP 317
With these changes, ZIP 317 [zip-0317] has a Revision 2.
In the Revisions section, add:
- Revision 2: Reduces \(\mathit{marginal\_fee}\) from 5000 to 1000 zatoshis per logical action, and raises \(\mathit{weight\_ratio\_cap}\) from 4 to 10, as specified in ZIP 2009. It applies from \(\mathsf{FEE\_REDUCTION\_HEIGHT}\), which is 3590000 on Mainnet and 4465026 on Testnet. For a wallet, the height that determines whether it applies is the height of the block in which the transaction is expected to be mined. For a node, it is the height of the next block.
In the parameter table of the Fee calculation section, replace this entry:
\(\mathit{marginal\_fee}\) \(5000\) zatoshis per logical action (as defined below)
with this entry:
\(\mathit{marginal\_fee}\) \(5000\) before Revision 2; \(1000\) from Revision 2 zatoshis per logical action (as defined below)
No other entry in the table changes.
In the section Rationale for the chosen parameters, update the rationale for the marginal fee. Include the value of \(\mathit{marginal\_fee}\) from Revision 2. Use the Rationale section of this ZIP for the update.
In the section Recommended algorithm for block template construction, replace this text:
Define constants \(\mathit{weight\_ratio\_cap} = 4\) and \(\mathit{block\_unpaid\_action\_limit} = 50\).
with this text:
Define constants \(\mathit{weight\_ratio\_cap} = 4\) before Revision 2, or \(10\) from Revision 2, and \(\mathit{block\_unpaid\_action\_limit} = 50\).
In the section Rationale for block template construction algorithm, replace the paragraph that starts with "The rationale for choosing \(\mathit{weight\_ratio\_cap} = 4\)". Use this text:
The rationale for choosing \(\mathit{weight\_ratio\_cap} = 10\) from Revision 2 is as a compromise between not allowing any prioritization of transactions relative to those that pay the conventional fee, and allowing arbitrary prioritization based on ability to pay. Because the cap is a multiple of the conventional fee, the fee at which a transaction's weight ratio saturates falls with \(\mathit{marginal\_fee}\). A cap of 10 at \(\mathit{marginal\_fee} = 1000\) places that point below where it was at \(\mathit{weight\_ratio\_cap} = 4\) and \(\mathit{marginal\_fee} = 5000\).
In the Deployment section, add:
Revision 2 applies from \(\mathsf{FEE\_REDUCTION\_HEIGHT}\), as specified in ZIP 2009.
If ZIP 235 [zip-0235] is activated, the fraction that is removed from circulation stays the same. From a fee of 2,000 zatoshis, 1,200 zatoshis are removed from circulation, and the miner gets 800 zatoshis.
Interaction with the getstandardfee RPC endpoint
zebrad reports the ZIP 317 \(\mathit{marginal\_fee}\) through its getstandardfee RPC endpoint. Implementations that supply this endpoint or an equivalent endpoint must report 1,000 zatoshis per logical action from the activation height in the Deployment section.
Rationale
Why a \(\mathit{marginal\_fee}\) of 1,000. After a 5x decrease, the fee is still approximately 8.7 times its 2022 cost in USD, at the price of 2026-10-21.
Why not cut \(\mathit{marginal\_fee}\) further. ZIP 218 [zip-0218-dos] has a limit on the shielded actions in each block: a global budget of 330 units. If an adversary fills this budget with its own transactions, the adversary crowds the shielded transactions of other users out of blocks. The target of this denial-of-service (DoS) attack is the use of the chain, and not the nodes.
The cheapest method to fill the budget is a transaction with these items:
- 150 Sapling spends and 150 Sapling outputs. Together, these count as 150 logical actions.
- 30 Orchard or Ironwood actions.
The total is 180 logical actions for each block. At \(\mathit{marginal\_fee} = 1000\) and the target block spacing of 25 seconds, an adversary that does not mine pays 0.0018 ZEC for each block. This is approximately 6.2 ZEC each day. With a further decrease, this cost decreases in proportion. Then there is a risk that the cost is not a sufficient disincentive to a DoS attack.
Why a \(\mathit{weight\_ratio\_cap}\) of 10. With this value, the rationale of ZIP 317 in the section "Rationale for block template construction algorithm" continues to apply. That rationale is to limit the ability of an adversary to get a significant advantage over other users. The adversary gets this advantage when it pays more than the conventional transaction fee.
Precedent. In 2020, the conventional transaction fee was decreased with ZIP 313 [zip-0313] in the same way. That change was a wallet convention, and it had no network upgrade.
Deployment
Node implementations must release the new relay policy before wallets start to use the new fee. In zebra and in zakura, \(\mathit{block\_unpaid\_action\_limit}\) is 0. An operator cannot change this value. Thus a node that is not upgraded does not relay a transaction with a fee of 2,000 zatoshis at all. The reason is that, with the old parameters, this transaction has 2 unpaid actions.
Both parameter changes apply from \(\mathsf{FEE\_REDUCTION\_HEIGHT}\). On Mainnet, this is block height 3590000. This height is expected at approximately 19 November 2026, approximately two weeks after the activation of NU7 [zip-0259].
On Testnet, \(\mathsf{FEE\_REDUCTION\_HEIGHT}\) is block height 4465026. This is the Testnet activation height of NU7. The Testnet chain is already past this height. Thus the changes apply immediately on Testnet.
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.3 [NU6.1] or later
- [zip-0218-dos]
- ZIP 218: 25-second Block Target Spacing — Fee incentives and DoS resistance
- [zip-0235]
- ZIP 235: Remove 60% of Transaction Fees From Circulation
- [zip-0259]
- ZIP 259: Deployment of the NU7 Network Upgrade
- [zip-0313]
- ZIP 313: Reduce Conventional Transaction Fee to 1000 zatoshis
- [zip-0317]
- ZIP 317: Proportional Transfer Fee Mechanism