We have now 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 modifications. For full particulars, please discuss with the launch notes.
We needed to pull an earlier launch as a result of a database improve bug that was launched in v2.4.0. You probably have upgraded to 2.4.0, your Zebra tackle index has change into corrupted. This doesn’t have an effect on consensus, however will make the RPC interface return invalid information for calls like getaddressutxos
and different address-related calls. To resolve this, please see the launch notes for full particulars.
On this launch we Applied deserialization for Zebra’s block and transaction varieties, added a brand new gRPC methodology for listening to modifications within the mempool. We’ve completed numerous work on RPC strategies, together with including some lacking fields to RPC outputs, introducing new fields and creating new strategies resembling invalidateblock
and reconsiderblock
.
The zebra_network::Config sort now makes use of IPv6 because the default pay attention tackle, and we help configuring shielded addresses for mining.
We have now made a number of vital bug fixes, together with preserving the order of RPC output fields, appropriately 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 present database from the v26/ folder to a brand new v27/ folder. Please notice that downgrading will not be doable. To take care of the choice of reverting to the earlier model in case of surprising points, we strongly advocate backing up the v26/ folder earlier than operating the upgraded Zebra. The improve course of could take a number of hours, particularly on smaller machines. Throughout this time, Zebra will proceed to function usually, however some RPC responses could return empty or inaccurate information.
Should you used the `ldb checkpoint` instrument for database backups, please be suggested that this instrument 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
area byte order has been mounted 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 challenge 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.