[ZEC] ZCASH - July 20th, 2018 Weekly update (Engineering)
This week will have a more casual format for the update as most of
the teams have opted into a one-time 3 week sprint which started last
week. This is in order to reorient ourselves after a couple of
distracting weeks with Zcon0 and folks taking time off around the 4th of
July. So we’re kind of mid-sprint for this engineering update and there
are no formal summaries of work accomplished.
A meta update to the teams structure:
combined the protocol and zcashd teams. Since most of the consensus
level engineering is complete for Sapling (barring any required fixes
coming from audit results), the most urgent work for Sapling is now
wallet-level support.We’ve added a new team focused on the reference mobile wallet project, an idea introduced in the recent roadmap proposal .We’ve
also added an enterprise team which will focus on work supporting
projects like last year’s Quorum collaboration. There’s not likely to be
many updates from this team as collaborative work with other companies
is typically done under NDA until a product is announced.
Here are some in progress or review items for some of these teams. You can follow with progress in their respective projects
This team focus on development of the zcashd client.
ZIP32 (ZIP PR 157) support aka Shielded Hierarchical Deterministic WalletsSapling proof generation APIExtending RPC support for Sapling keysSapling note supportNew version of the Sapling spec is ready which now includes the completed proofs needed to support the Pedersen hash optimizations
Development Infrastructure Team
This team works on making sure developers have the tools and
infrastructure they need to efficiently collaborate, design, implement,
review, test, and ship high quality projects.
Investigating MacOS builder to resolve continued breakagecreating a Windows CI workerInvestigate current CI infrastructure to propose potential upgradesfix CentOS 7 builder
This team is the interface to
everything not directly related to zcashd or the protocol and include
support for third-party tools and services. Ecosystem projects developed
by Zcash Co. also get handled in this team. Tracking for this team is
kept private to prevent information leakage about third-parties.
Researching ways to stay in touch with third parties and give appropriate supportRamping up for Sapling education and outreach to third-parties
This team works on improving the accessibility of zcashd and Zcash overall.
investigate and formalize ReadTheDocs translation processtest GitLab as repository host (test repo: https://gitlab.com/mdr0id/test-rtd-docs 2)migration of documentation on the website to RTD (for example the UX checklist & network upgrade guide for developers)brainstorming around a feature-based wallet selection guide