We now have launched Zebra v2.4.2. Included are safety fixes, bug fixes, and new options. In case you are at present utilizing Zebra, please be aware of any breaking adjustments. For full particulars, please check with the launch notes.
We needed to pull an earlier launch because of a database improve bug that was launched in v2.4.0. In case you have upgraded to 2.4.0, your Zebra handle index has grow to be corrupted. This doesn’t have an effect on consensus, however will make the RPC interface return invalid knowledge for calls like getaddressutxos
and different address-related calls. To resolve this, please see the launch notes for full particulars.
On this launch we Carried out deserialization for Zebra’s block and transaction varieties, added a brand new gRPC technique for listening to adjustments within the mempool. We’ve achieved plenty of work on RPC strategies, together with including some lacking fields to RPC outputs, introducing new fields and creating new strategies akin to invalidateblock
and reconsiderblock
.
The zebra_network::Config sort now makes use of IPv6 because the default pay attention handle, and we assist configuring shielded addresses for mining.
We now have made a number of vital bug fixes, together with preserving the order of RPC output fields, accurately setting some fields in transaction outputs, and permitting native outbound connections on Regtest.
Â
Breaking Adjustments
Â
Main Database Improve
This launch features a important database improve that may routinely transfer your current database from the v26/ folder to a brand new v27/ folder. Please be aware that downgrading will not be doable. To take care of the choice of reverting to the earlier model in case of sudden points, we strongly advocate backing up the v26/ folder earlier than operating the upgraded Zebra. The improve course of might take a number of hours, particularly on smaller machines. Throughout this time, Zebra will proceed to function usually, however some RPC responses might return empty or inaccurate knowledge.
In case you used the `ldb checkpoint` software for database backups, please be suggested that this software is now not supported and can corrupt any databases utilized by Zebra v2.4.0 or later releases.
Â
Removing of Deprecated Config Choices
The `debug_like_zcashd` config possibility for mining has been eliminated.
Â
Adjustments to Response Codecs
The cm_u
subject byte order has been fastened within the getrawtransaction
and getblock
responses. We’ve eliminated the zebra-scan
and zebra-grpc
crates as they’re now not supported. There was a consensus rule violation in V5 coinbase transactions at low heights, which has now been resolved. This difficulty was restricted to Regtest or customized testnets and has now been resolved.
Â
Acknowledgments
An enormous thanks to all of the contributors who made this launch doable: @ala-mode, @arya2, @conradoplg, @elijahhampton, @gustavovalverde, @idky137, @mpguerra, @oxarbitrage, @sellout, @str4d and @upbqdn.