Tags: zcash/zcash
Tags
zcashd release version 6.10.0 Notable changes =============== Network Upgrade 6.1 ------------------- The mainnet activation of the NU6.1 network upgrade is supported by the 6.10.0 release, with an activation height of 3146400, which should occur on approximately November 23, 2025. Please upgrade to this release, or any subsequent release, in order to follow the NU6.1 network upgrade. The following ZIPs are being deployed as part of this upgrade: - [ZIP 271: Deferred Dev Fund Lockbox Disbursement](https://zips.z.cash/zip-0271) - [ZIP 1016: Community and Coinholder Funding Model](https://zips.z.cash/zip-1016) (partially) In order to help the ecosystem prepare for the mainnet activation, NU6.1 has already been activated on the Zcash testnet. Any node version 6.3.0 or higher, including this release, supports the NU6 activation on testnet.
zcashd release version 6.3.0 Notable changes =============== Network Upgrade 6.1 ------------------- The code preparations for the Network Upgrade 6.1 consensus rules are finished and included in this release. The following ZIPs are being deployed: - [ZIP 271: Deferred Dev Fund Lockbox Disbursement](https://zips.z.cash/zip-0271) - [ZIP 1016: Community and Coinholder Funding Model](https://zips.z.cash/zip-1016) (partially) NU6.1 will activate on testnet at height **3,536,500**, and can also be activated at a specific height in regtest mode by setting the config option `-nuparams=4dec4df0:HEIGHT`. As with previous network upgrades, it is possible that backwards-incompatible changes might be made to the consensus rules in this testing phase, prior to setting the mainnet activation height. In the event that this happens, testnet will be rolled back in v6.10.0 and a second testnet activation will occur. See [ZIP 255](https://zips.z.cash/zip-0255) for additional information about the deployment process for NU6.1. Fixed Orchard bug in transparent balance APIs --------------------------------------------- Several RPC methods inherited from Bitcoin Core internally rely on `CWalletTx::IsFromMe` for detecting involvement of the wallet in the input side of a transaction. For example: - The `getbalance` RPC method uses it as part of identifying "trusted" zero-confirmation transactions to include in the balance calculation. - The `gettransaction` RPC method uses it to decide whether to include a `fee` field in its response. When Orchard was integrated into `zcashd`, this method was not updated to account for it, meaning that unshielding transactions spending Orchard notes would not be correctly accounted for in transparent-specific RPC methods. A similar bug involving Sprout and Sapling spends was fixed in v4.5.1. Updates to default values ------------------------- - The default for the `-preferredtxversion` config option has been changed from `4` (the v4 transaction format introduced in the 2018 Sapling Network Upgrade) to `5` (the v5 transaction format introduced in the 2022 NU5 Network Upgrade). Use `-preferredtxversion=4` to retain the previous behaviour.
Release v6.2.0 Notable changes =============== zcashd is being deprecated in 2025. Full nodes are being migrated to zebrad, and the Zallet wallet is being built as a replacement for the zcashd wallet. For some of zcashd's JSON-RPC methods, zebrad or Zallet should be a drop-in replacement. Other JSON-RPC methods may require modified usage, and some JSON-RPC methods will not be supported. You can find all information about the zcashd deprecation process on this webpage, which you can monitor for future updates: <https://z.cash/support/zcashd-deprecation/> We are collecting information about how zcashd users are currently using the existing JSON-RPC methods. The above webpage has a link to a spreadsheet containing the information we have collected so far, and the planned status for each JSON-RPC method based on that information. If you have not provided feedback to us about how you are using the zcashd JSON-RPC interface, please do so as soon as possible. To confirm that you are aware that zcashd is being deprecated and that you will need to migrate to zebrad and/or Zallet in 2025, add the following option to your config file: i-am-aware-zcashd-will-be-replaced-by-zebrad-and-zallet-in-2025=1 Platform Support ---------------- - Ubuntu 20.04 LTS has been removed from the list of supported platforms. It will reach End of Support on May 31st 2025, but it no longer satisfies our Tier 2 policy requirements because GitHub no longer supports Ubuntu 20.04 runners. RPC Changes ----------- * The RPC methods `keypoolrefill`, `settxfee`, `createrawtransaction`, `fundrawtransaction`, and `signrawtransaction` have been deprecated, but are still enabled by default. * The RPC methods `z_getbalance` (which was previously deprecated), and `getnetworkhashps`, and the features `deprecationinfo_deprecationheight` and `gbt_oldhashes`, have been disabled by default. The `addrtype` feature is now disabled by default even when zcashd is compiled without the `ENABLE_WALLET` flag.
zcashd release version 6.0.0 Notable changes =============== The mainnet activation of the NU6 network upgrade is supported by the 6.0.0 release, with an activation height of 2726400, which should occur on approximately November 23, 2024. Please upgrade to this release, or any subsequent release, in order to follow the NU6 network upgrade. The following ZIPs are being deployed, or have been updated, as part of this upgrade: * [ZIP 207: Funding Streams (updated)](https://zips.z.cash/zip-0207) * [ZIP 214: Consensus rules for a Zcash Development Fund (updated)](https://zips.z.cash/zip-0214) * [ZIP 236: Blocks should balance exactly](https://zips.z.cash/zip-0236) * [ZIP 253: Deployment of the NU6 Network Upgrade](https://zips.z.cash/zip-0253) * [ZIP 1015: Block Reward Allocation for Non-Direct Development Funding](https://zips.z.cash/zip-1015) * [ZIP 2001: Lockbox Funding Streams](https://zips.z.cash/zip-2001) In order to help the ecosystem prepare for the mainnet activation, NU6 has already been activated on the Zcash testnet. Any node version 5.10.0 or higher, including this release, supports the NU6 activation on testnet. Mining ------ - The default setting of `-blockunpaidactionlimit` is now zero, which has the effect of no longer allowing "unpaid actions" in [block production]. This adapts to current network conditions. If you have overridden this setting as a miner, we recommend removing the override. This configuration option may be removed entirely in a future release. [block production]: https://zips.z.cash/zip-0317#block-production Platform Support ---------------- - Windows builds have been fixed.
Zcashd release version 5.10.0 Notable changes =============== Network Upgrade --------------- - This release includes support for NU6 on Testnet. A further upgrade will be needed for NU6 on Mainnet. RPC Changes ----------- - A bug in parameter handling has been fixed for the `getaddresstxids` and `getaddressdeltas` RPC methods. Previously, leaving the end height unset would cause the start height to be set to zero and therefore ignored. The end height is now also automatically bounded to the chain tip; passing an end height greater than the chain tip height no longer results in an error; values up to and including the chain tip are returned instead. Platform Support ---------------- - Debian 10 (Buster) has been removed from the list of supported platforms. It reached EoL on June 30th 2024, and does not satisfy our Tier 2 policy requirements. Other ----- - The `zcash-inspect` tool (which was never distributed, and was present in this repository for debugging purposes) has been moved to the `devtools` subfolder of the https://github.com/zcash/librustzcash repository. Fixes ----- - Security fixes for vulnerabilities disclosed in https://bitcoincore.org/en/2024/07/03/disclose-orphan-dos/ and https://bitcoincore.org/en/2024/07/03/disclose-inv-buffer-blowup/ have been backported to `zcashd`.
PreviousNext