The Zcash Basis is happy to announce the discharge of Zebra 2.1.0. This launch contains some needed updates post-NU6 activation.
We at the moment are verifying that V5 transactions within the mempool have the proper consensus department ID earlier than returning a transaction ID, which might point out a profitable insertion within the mempool, despite the fact that they’d be ultimately rejected by the block consensus checks.
Equally, Zebra additionally now returns an error when making an attempt to submit transactions that may ultimately fail some consensus checks (e.g. double spends) however would additionally return a transaction ID indicating success.
The discharge additionally bumps Zebra’s preliminary minimal protocol model such that this launch of Zebra will all the time reject connections with friends promoting a community protocol model beneath 170,120 on Mainnet and 170,110 on Testnet. Previous to this variation, these connections would have been accepted till Zebra’s chain state reaches the NU6 activation peak. Whereas that is customary process in Zebra after a Zcash community improve, this variation to the minimal protocol model is assessed as a breaking change in Zebra.
As well as, the getblock RPC technique has been up to date to return some further info such because the block peak (even for those who present a block hash) and different fields as supported by the getblockheader RPC name.
You’ll be able to see a full copy of the included adjustments within the v2.1.0 Launch Notes on GitHub.
The submit Zebra 2.1.0 Launch appeared first on Zcash Basis.
