Heartwood testnet activation
This launch helps the activation of Heartwood on testnet, with an activation peak of 903800, slated to happen on Might 6, 2020. Please improve to this launch, or any subsequent launch, to be able to comply with the Heartwood community improve on testnet.
This launch does not help activation of Heartwood on mainnet. With a purpose to comply with the Heartwood improve on mainnet you’ll nonetheless must improve to three.0.0 (or a later model) when it’s launched within the coming month.
The Heartwood community improve deploys ZIP 213, which permits miners to mine immediately into shielded addresses. It additionally deploys ZIP 221, enabling Flyclient help by altering the semantics of current block header fields. The deployment course of for the Heartwood improve is described in ZIP 250.
Testnet: Mining to Sapling addresses
After the activation of Heartwood on testnet, miners will be capable to instantly protect funds to Sapling addresses within the coinbase transactions which mint new testnet cash (TAZ).
This launch offers the power for miners to specify
mineraddress=SAPLING_ADDRESS of their
zcash.conf file, the place
SAPLING_ADDRESS is a Sapling cost deal with that they will acquire utilizing
z_getnewaddress. Nevertheless, miners ought to wait till Heartwood has activated on testnet earlier than making this variation to their configuration file, or else
getblocktemplate will return block templates that can not be mined.
Sapling viewing key help
This launch offers help for Sapling viewing keys (particularly, the prolonged viewing keys described in ZIP 32) within the pockets. Nodes will observe each despatched and obtained transactions for any Sapling addresses related to the Sapling viewing keys which were imported into the pockets.
- Use the
z_exportviewingkeyRPC methodology to acquire the viewing key for a shielded deal with in a node’s pockets. For Sapling addresses, these at all times start with “zxviews” (or “zxviewtestsapling” for testnet addresses).
z_importviewingkeyto import a viewing key into one other node. Imported Sapling viewing keys will likely be saved within the pockets, and remembered throughout restarts.
z_getbalancewill present the steadiness of a Sapling deal with related to an imported Sapling viewing key. Balances for Sapling viewing keys will likely be included within the output of
includeWatchonlyparameter is ready to
- RPC strategies for viewing shielded transaction info (corresponding to
z_listreceivedbyaddress) will return info for Sapling addresses related to imported Sapling viewing keys.
Particulars about what info might be considered with these Sapling viewing keys, and what ensures you could have about that info, might be present in ZIP 310.
View shielded info in pockets transactions
This launch introduces the
z_viewtransaction RPC command. This command, given a transaction ID, will decrypt the transaction with all Sapling keys within the native pockets and return the shielded info that it will possibly get better, together with
- The deal with that every notice belongs to
- Values in each decimal ZEC/TAZ and zatoshis
- The ID of the transaction that every spent notice was obtained in
outgoingflag on every new notice, which will likely be
trueif the output isn’t for an deal with within the pockets
memoStrdiscipline for every new notice, containing its textual content memo (if its memo discipline incorporates a sound UTF-Eight string)
-maxtimeadjustmentpossibility has been eliminated; node operators ought to guarantee their node’s native time is configured correctly.
- Error messages for transactions which are rejected throughout community upgrades are extra clear.
- We’ve launched a
-txexpirynotifypossibility which, just like the
-blocknotifyconfig possibility, will carry out the configured command at any time when a transaction expires within the mempool.
z_importviewingkeyRPC strategies now return the kind of the imported spending or viewing key (Sprout or Sapling) and the corresponding cost deal with.
- Damaging heights at the moment are permitted in
getblockhash, to pick blocks backwards from the chain tip. A peak of
-1corresponds to the final identified legitimate block on the primary chain.
- A brand new RPC methodology
getexperimentalfeaturesreturns the listing of enabled experimental options.
Extra particulars concerning the modifications on this launch might be discovered within the launch notes.