Zcash releases the Overwinter-compatible1.1.2
Following on the heels of a successful Zcon0, their first ever Zcash conference, the company has released the Zcash 1.1.2. The new release is compatible with the Blockchain network’s recent upgrade, OVERWINTER. 1.1.2 focuses on implementing internal changes which are needed for Sapling and the librustzcash and sapling-crypto libraries. The Overwinter upgrade was successfully activated at the block height 347,500 on June 25th and most of the ecosystem upgraded smoothly.
Sapling is Zcash’s next major protocol upgrade, which according to their blog is scheduled to release in October. The github repository, librustzcash is a static library for Zcash code assets which are written in Rust. The sapling-crypto library is another github repository which is still a work in progress. The library contains the implementation of Zcash’s “Sapling” cryptography.
The Sapling upgrade will mostly activate on Zcash’s 2nd birthday, October 28th, 2018 according to their blog post. The Sapling upgrade will bring significant efficiency improvements for shielded transactions. This will make way for widespread adoption of Zcash shielded addresses among mobile exchanges and vendors. To ensure safe activation of Sapling, the team decided to delay the upgrade citing the need for additional testing.
1.1.2, which was released yesterday is to be used to test Sapling and support for 1.1.2 will end on October 21, 2018. The exact block height at which the upgrade will activate and other parameters will be set with the release of version 2.0.0.
Here is an overview of the changes which are included in the new release:
- The configuration option for turning off EOS halt which was previously known as auto-senescence has been removed.
2. hashFinalSaplingRoot the data field has been added to getblocktemplate, the RPC call.
3. finalsaplingroot, the data field has been added to getblock and RPC calls getblockheader.
4. Encodings for Sapling addresses have been added.
5. They’ve also added a class for Sapling notes.
6. Tests for Sapling anchors have been created.
7. They’ve created test vectors for components of Sapling keys.
8. They’ve clarified the help message of signmessage, the RPC call.
- A few tests have been updated with fixes.
10. They have also executed some refactoring for code clean up.
Image via Shutterstock
Join our Telegram group