The Zcash Foundation is pleased to announce the release of Zebra 2.1.0. This release includes some necessary updates post-NU6 activation.
We are now verifying that V5 transactions in the mempool have the correct consensus branch ID before returning a transaction ID, which would indicate a successful insertion in the mempool, even though they would be eventually rejected by the block consensus checks.
Similarly, Zebra also now returns an error when trying to submit transactions that would eventually fail some consensus checks (e.g. double spends) but would also return a transaction ID indicating success.
The release also bumps Zebra’s initial minimum protocol version such that this release of Zebra will always reject connections with peers advertising a network protocol version below 170,120 on Mainnet and 170,110 on Testnet. Prior to this change, these connections would have been accepted until Zebra’s chain state reaches the NU6 activation height. While this is standard procedure in Zebra after a Zcash network upgrade, this change to the minimum protocol version is classified as a breaking change in Zebra.
In addition, the getblock RPC method has been updated to return some additional information such as the block height (even if you provide a block hash) and other fields as supported by the getblockheader RPC call.
You can see a full copy of the included changes in the v2.1.0 Release Notes on GitHub.
The post Zebra 2.1.0 Release appeared first on Zcash Foundation.
