Tags: mdr0id/zcash
Tags
Zcashd release v5.3.0 Notable changes =============== Wallet Performance Improvements ------------------------------- `zcashd 5.2.0` improved the performance of wallet scanning with multithreaded batched trial decryption of Sapling outputs. However, for some nodes this resulted in growing memory usage that would eventually cause an OOM abort. We have identified the cause of the growth, and made significant improvements to reduce the memory usage of the batch scanner. In addition, the batch scanner now has a memory limit of 100 MiB. `zcashd` now reports the following new metrics when `-prometheusport` is set: - (counter) `zcashd.wallet.batchscanner.outputs.scanned` - (gauge) `zcashd.wallet.batchscanner.size.transactions` - (gauge) `zcashd.wallet.batchscanner.usage.bytes` - (gauge) `zcashd.wallet.synced.block.height` RPC Interface ------------- - The `finalorchardroot` field in the `getblock` result and the `orchard.commitments.finalRoot` field in the `z_gettreestate` result have been changed to match the byte ordering used for the `orchard.anchor` field in the `getrawtransaction` result. These previously produced different hash values from the `orchard.anchor` field due to having been byte-flipped in their internal representation in zcashd.
Release v5.3.0-rc1 Notable changes =============== Wallet Performance Improvements ------------------------------- `zcashd 5.2.0` improved the performance of wallet scanning with multithreaded batched trial decryption of Sapling outputs. However, for some nodes this resulted in growing memory usage that would eventually cause an OOM abort. We have identified the cause of the growth, and made significant improvements to reduce the memory usage of the batch scanner. In addition, the batch scanner now has a memory limit of 100 MiB. `zcashd` now reports the following new metrics when `-prometheusport` is set: - (counter) `zcashd.wallet.batchscanner.outputs.scanned` - (gauge) `zcashd.wallet.batchscanner.size.transactions` - (gauge) `zcashd.wallet.batchscanner.usage.bytes` - (gauge) `zcashd.wallet.synced.block.height` RPC Interface ------------- - The `finalorchardroot` field in the `getblock` result and the `orchard.commitments.finalRoot` field in the `z_gettreestate` result have been changed to match the byte ordering used for the `orchard.anchor` field in the `getrawtransaction` result. These previously produced different hash values from the `orchard.anchor` field due to having been byte-flipped in their internal representation in zcashd.
Release v5.2.0 Notable changes =============== Node Performance Improvements ----------------------------- This release makes several changes to improve the performance of node operations. These include: - Backported CuckooCache from upstream to improve the performance of signature caching. - Added caching of proof and signature validation results for Sapling and Orchard to eliminate redundant computation. - Backported SHA-256 assembly optimizations from upstream. Wallet Performance Improvements ------------------------------- This release makes several changes to improve the performance of wallet operations. These include: - We now parallelize and batch trial decryption of Sapling outputs. - We now prune witness data in the wallet for notes spent more than 100 blocks in the past, so that we can avoid unnecessarily updating those witnesses. In order to take advantage of this performance improvement, users will need to start their nodes with `-rescan` one time, in order to ensure that witnesses for spent notes are in the wallet are properly pruned. - The process for incrementing the witnesses for notes the wallet is tracking has been optimized to avoid redundant passes over the wallet. - Removed an assertion that was causing a slowdown in wallet scanning post-NU5. RPC Interface Changes ===================== - A `version` field was added to the result for the `gettransaction` RPC call to avoid the need to make an extra call to `getrawtransaction` just to retrieve the version. Fixes ===== - Fixed a regression that caused an incorrect process name to appear in the process list.
Release v5.2.0-rc1 Notable changes =============== Node Performance Improvements ----------------------------- This release makes several changes to improve the performance of node operations. These include: - Backported CuckooCache from upstream to improve the performance of signature caching. - Added caching of proof and signature validation results for Sapling and Orchard to eliminate redundant computation. - Backported SHA-256 assembly optimizations from upstream. Wallet Performance Improvements ------------------------------- This release makes several changes to improve the performance of wallet operations. These include: - We now parallelize and batch trial decryption of Sapling outputs. - We now prune witness data in the wallet for notes spent more than 100 blocks in the past, so that we can avoid unnecessarily updating those witnesses. In order to take advantage of this performance improvement, users will need to start their nodes with `-rescan` one time, in order to ensure that witnesses for spent notes are in the wallet are properly pruned. - The process for incrementing the witnesses for notes the wallet is tracking has been optimized to avoid redundant passes over the wallet. - Removed an assertion that was causing a slowdown in wallet scanning post-NU5. RPC Interface Changes ===================== - A `version` field was added to the result for the `gettransaction` RPC call to avoid the need to make an extra call to `getrawtransaction` just to retrieve the version. Fixes ===== - Fixed a regression that caused an incorrect process name to appear in the process list.
Release v5.0.0 The mainnet activation of the NU5 network upgrade is supported by the 5.0.0 release, with an activation height of 1687104, which should occur on approximately May 31, 2022. The following ZIPs are being deployed, or have been updated, as part of this upgrade: * [ZIP 32 : Shielded Hierarchical Deterministic Wallets (updated)](https://zips.z.cash/zip_0032) * [ZIP 203: Transaction Expiry (updated)](https://zips.z.cash/zip_0203) * [ZIP 209: Prohibit Negative Shielded Chain Value Pool Balances (updated)](https://zips.z.cash/zip_0209) * [ZIP 212: Allow Recipient to Derive Ephemeral Secret from Note Plaintext (updated)](https://zips.z.cash/zip_0212) * [ZIP 213: Shielded Coinbase (updated)](https://zips.z.cash/zip_0213) * [ZIP 216: Require Canonical Jubjub Point Encodings](https://zips.z.cash/zip_0216) * [ZIP 221: FlyClient - Consensus-Layer Changes (updated)](https://zips.z.cash/zip_0221) * [ZIP 224: Orchard Shielded Protocol](https://zips.z.cash/zip_0224) * [ZIP 225: Version 5 Transaction Format](https://zips.z.cash/zip_0225) * [ZIP 239: Relay of Version 5 Transactions](https://zips.z.cash/zip_0239) * [ZIP 244: Transaction Identifier Non-Malleability](https://zips.z.cash/zip_0244) * [ZIP 252: Deployment of the NU5 Network Upgrade](https://zips.z.cash/zip_0252) * [ZIP 316: Unified Addresses and Unified Viewing Keys](https://zips.z.cash/zip_0316) * [ZIP 401: Addressing Mempool Denial-of-Service (clarified)](https://zips.z.cash/zip_0401)
PreviousNext