by Paige Peterson
This is our fortnightly engineering update which happens after the conclusion of each 2-week engineering sprint. You can check out last week’s update for recent news on community and communications.
Zcashd Team This team focuses on development of the zcashd client and Zcash protocol. Follow along with team discussions in the Community Chat #zcashd-team channel.
The team is working on specifications for Blossom. They have also addressed some issues for the upcoming 2.0.3 release including an update to libzmq (which avoids a possible security vulnerability), a fix for a scalability issue with larger wallets and addressed an issue with an unstable test.
This upcoming sprint we’ll be focused on cutting and testing the 2.0.3 release candidate (Feb 4) followed by the full release (Feb 11).
Development Infrastructure Team The Development Infrastructure team ensures developers have the tools and infrastructure they need. Join this team in the #dev-infrastructure chat channel.
We are still working on getting the Windows build integrated with our CI system (buildbot). We’re also continuing to work on automating our website deploys to make them faster.
Ecosystem Team This team is intended to work on projects that interface with external parties not including the zcashd core client and handles business development in the phases after initial contact by providing technical insight and support.Insight explorer updates are completed in the zcash-hackworks repositories, now focus is on merging in the required changes to zcashd to allow bitcore and insight to run without having to maintain a custom fork of Zcash Working with multiple exchanges and wallets to support z-address adoption
Documentation Team This team drives the curation and assists in the creation of documentation. Follow along in the #documentation chat channel. Check out the official Zcash documentation.