[ad_1]
The code preparations for the Community Improve 5 consensus guidelines are completed and included on this launch. The next ZIPs are being deployed:
NU5 will activate on testnet at top 1,590,000, and will also be activated at a selected top in regtest mode by setting the config choice
-nuparams=f919a198:HEIGHT.
The testnet activation of NU5, and zcashd v4.5.0 itself, is aimed toward enabling current Zcash customers to check their software program and make the required adjustments to be suitable with the brand new consensus guidelines. Specifically:
- Wallets ought to begin including assist for v5 transactions.
- Miners and mining swimming pools ought to be certain that their software program is suitable with the semantic change to the block header laid out in ZIP 244
A subsequent v4.5.1 launch within the coming weeks will add assist for producing and utilizing Unified Addresses (ZIP 316), which is able to allow zcashd wallets to work together with the Orchard shielded pool.
As with earlier community upgrades, it’s doable that backwards-incompatible adjustments is perhaps made to the consensus guidelines on this testing section, previous to setting the mainnet activation top. Within the occasion that this occurs, testnet can be rolled again in v5.0.0 and a second testnet activation will happen.
See ZIP 252 for extra details about the deployment course of for NU5.
Rejecting unknown CInv message varieties
Beforehand, if zcashd acquired an inv or getdata message containing unknown CInv message varieties, it could ignore them and course of the rest of the message. Beginning with v4.5.0, zcashd will as a substitute drop your entire inv or getdata message and reply with a reject message. This can allow node operators to find whether or not their nodes are sending sudden CInv varieties; specifically, node operators ought to guarantee their software program doesn’t produce the MSG_WTX CInv message sort meant for the Bitcoin community, which is incompatible with the MSG_WTX CInv message sort outlined in ZIP 239 (which can be used from NU5 activation for promoting v5 transactions).
Deprecated or eliminated RPCs
The ‘account’ API inherited from Bitcoin Core has been disabled for the reason that
launch of Zcash. Following its deprecation in Bitcoin Core v0.17 and elimination
in Bitcoin Core v0.18, we have now now eliminated the API from zcashd.
[ad_2]
Source link
