New Release 5.1.0 - Electric Coin Company

On June 17, 6pm UTC, shielded transactions submitted to the Zcash community elevated dramatically. Because of this, third social gathering wallets have skilled decrease efficiency. The community remained, and nonetheless stays, steady and operational, and transactions are being processed usually.

The ECC core group labored over the Fourth of July vacation to implement a brand new batch validation algorithm to additional cut back verification time by one other 80%. Their efforts noticed launch zcashd 5.1.0 go stay.

Abstract

This launch is primarily focused at bettering the validation efficiency of Sapling and Orchard transactions in addition to an incremental enchancment to the scan efficiency of post-NU5 blocks. The discharge additionally made enhancements to getblocktemplate efficiency and added Orchard data to getrawtransaction and decoderawtransaction. We’ll proceed to deal with remaining scan efficiency points in subsequent releases.

Notable modifications

Sooner block validation for Sapling and Orchard transactions

Block validation in zcashd is a largely single-threaded course of, attributable to how the chain replace logic inherited from Bitcoin Core is written. Nevertheless, sure extra computationally intensive checks are carried out extra effectively than checking every thing individually:

ECDSA signatures on clear inputs are checked by way of multithreading.
RedPallas signatures on Orchard actions are checked by way of batch validation.

As of this launch, zcashd applies these strategies to extra Sapling and Orchard elements:

RedJubjub signatures on Sapling Spends are checked by way of batch validation.
Groth16 proofs for Sapling Spends and Outputs are checked by way of batch validation and multithreading.
Halo 2 proofs for Orchard Actions are checked by way of batch validation and multithreading.

This reduces worst-case block validation occasions for noticed historic blocks by round 80% on a Ryzen 9 5950X CPU.

The variety of threads used for checking Groth16 and Halo 2 proofs (in addition to for creating them when spending funds) could be set by way of the RAYON_NUM_THREADS setting variable.

Possibility dealing with

A brand new -preferredtxversion argument permits the node to preferentially create transactions of a specified model, if a transaction doesn’t include elements that necessitate creation with a particular model. For instance, setting -preferredtxversion=4 will trigger the node to create V4 transactions each time the transaction doesn’t include Orchard elements. This may be useful if recipients of transactions are prone to be utilizing legacy wallets that haven’t but been upgraded to assist parsing V5 transactions.

RPC interface

The getblocktemplate RPC technique now skips proof and signature checks on templates it creates, as these templates solely embody transactions which have beforehand been checked when being added to the mempool.
The getrawtransaction and decoderawtransaction RPC strategies now embody particulars about Orchard actions inside transactions.

Pockets

Rescan efficiency of post-NU5 blocks has been barely improved (general rescan time for a single-account pockets decreases by round 6% on a Ryzen 9 5950X). Additional enhancements shall be carried out in future releases to assist mitigate the impact of blocks stuffed with shielded outputs.
The CWallet::UpdatedTransaction sign is not referred to as whereas holding the cs_main lock. This fixes a difficulty the place RPCs may block for lengthy durations of time on zcashd nodes with giant wallets. Downstream code forks which have reconnected the NotifyTransactionChanged pockets sign ought to be aware of this variation, and never rely there on entry to globals protected by cs_main.
Some zcashd 5.0.0 nodes would shut down a while after begin with the error ThreadNotifyWallets: Did not learn block X whereas notifying wallets of block disconnects. zcashd now makes an attempt to rectify the scenario, and in any other case will inform the person earlier than shutting down {that a} reindex is required.

Deprecated

As of this launch, the next beforehand deprecated options are disabled by default, however could also be reenabled utilizing -allowdeprecated=<characteristic>.

The dumpwallet RPC technique is disabled. It could be reenabled with allowdeprecated=dumpwallet. dumpwallet shouldn’t be used; it’s unsafe for backup functions because it doesn’t return any key data for keys used to derive shielded addresses. Use z_exportwallet as a substitute.

As of this launch, the next options are deprecated, however stay accessible by default. These options could also be disabled by setting -allowdeprecated=none. After no less than 3 minor-version releases, these options shall be disabled by default and the next flags to -allowdeprecated shall be required to allow their continued use: