This article was first published on Zcash
With the successful activation of Sapling, the Zcash Company engineering team is focused on two strategic priorities in 2019: facilitating the adoption of a shielded standard throughout the ecosystem and, designing and implementing our next protocol upgrade—dubbed Zcash Blossom.
We’re in the early phases of defining the technical goals for Blossom, which we plan to activate in October of 2019. If you’re eager to dig into those feature goals, I recommend reading my forum post, Announcing Zcash Blossom and proposed feature goals.
For this post, I’d like to focus on the process we’re using to safely ship new protocol upgrades in Zcash, which we call the Zcash Network Upgrade Pipeline. We’ve developed this process to meet a variety of goals, based on everything we’ve learned from the Zcash launch and the Overwinter and Sapling upgrades. The primary goals are to ship safely—with plenty of time for ecosystem partner integration, in collaboration across multiple organizations—in a governance agnostic manner, all while pipelining concurrent upgrades.
The Pipeline at a Glance
The Network Upgrade Pipeline defines a scheduled sequence of coordination points to bring consensus features from the speculative realm down into the production Zcash network.
This process is time-based and designed to ensure the consensus upgrades shipped to Zcash meet our historic standards for safety and quality. It is intended to support the development of multiple subsequent upgrades concurrently, thus the term “pipeline.” The Zcash Company aims to set a consistent pace of two upgrades per year, indicated as Upgrade A and Upgrade B in the diagram.
The coordination points, represented by red-outlined diamonds in this chart, signify essential, high-level milestones that ...
To keep reading, please go to the original article at: