Network Upgrade 4: Canopy
The 4.0.0 release supports the Canopy activation on mainnet, which will occur at a block height of 1046400 (mid-November), following the targeted EOS halt of our 3.1.0 release. Please upgrade to this release, or any subsequent release, in order to follow the Canopy network upgrade on mainnet.
The following ZIPs are being deployed:
- ZIP 207: Funding Streams
- ZIP 211: Disabling Addition of New Value to the Sprout Value Pool
- ZIP 212: Allow Recipient to Derive Sapling Ephemeral Secret from Note Plaintext
- ZIP 214: Consensus rules for a Zcash Development Fund
- ZIP 215: Explicitly Defining and Modifying Ed25519 Validation Rules
In order to help the ecosystem prepare for the mainnet activation, Canopy has already been activated on the Zcash testnet. Any node version 3.1.0 or higher, including this release, supports Canopy on testnet as well.
Disabling new value in the Sprout value pool
After the mainnet activation of Canopy, it will not be possible to send funds to Sprout z-addresses from any other kind of address, as described in ZIP 211. It will still be possible to send funds from a Sprout z-address and to send funds between Sprout addresses. Users of Sprout z-addresses are encouraged to use Sapling z-addresses instead and to migrate their remaining Sprout funds into a Sapling z-address using the migration utility in zcashd: set migrate=1 in your zcash.conf file, or use the z_setmigration RPC.
