Final Blossom Goals

Since announcing the proposed Blossom goals on the Forum this past November, the Zerocoin Electric Coin Company has worked both internally and across the wider community to gather information and capacity-plan in order to achieve the proposed Blossom goals. We solicited and received feedback from the community; thank you for your passion, thoughtfulness and attention to detail.

Following this process, we’ve narrowed down the Blossom goals and further refined them. This is the resulting final list of goals for what the Company will implement and support in the Blossom series of its zcashd software:

  1. Split Founder’s Reward: The Blossom series of zcashd will decouple the three funding streams for the Zcash Foundation, Company Strategic Reserve, and the remainder. This will help to de-risk these funding streams, as previously they were all running through one stream. The current model of a single revenue stream runs the risk of being compromised, whether it is carried out by hackers, the result of a legal issue, a technical mistake of some kind, or organizational failure. In the existing model in any of these scenarios, all three revenue streams could be compromised. In this new model where we split the founders’ reward in the protocol, revenue streams that are not directly compromised will be left unaffected, akin to the notion of “reducing the blast radius” of an event.
  2. Shorter Blocktimes: The Blossom series of zcashd increases the frequency of blocks (subject to further security and performance analysis), allowing more transactions and allowing them to resolve faster. This will improve Zcash’s usability and increase how many transactions per hour the network can sustain while keeping transaction fees low.

You’ll notice that Harmony Mining is no longer on the list of goals for Blossom. During the R&D phase, we determined that the unresolved security and engineering issues of Harmony Mining could not be solved in the Blossom timeline. As a result we are postponing this goal to NU3, the upgrade occuring after Blossom in April 2020.

As a note, there are three more points along the network upgrade timeline below where we may need to abort any of these goals if we find significant issues with our approaches:

  1. As a result of specification auditing (end of February)
  2. Inability to finish the code on-time (end of March)
  3. Code auditing or testing (end of May)

Possible Regular Releases

In addition to the network upgrade goals above, the Company will be pursuing the following goals as possible regular releases. Given the limited time and engineering resources available between now and May 31st, when the code needs to be released for the Blossom upgrade, we shifted any goals able to be achieved (even in part) with a regular release outside of the Blossom network upgrade.

These goals are targeted as part of regular releases before Blossom activation at the end of October:

  1. Sprout Address Retirement: We plan to create a standard rule to disallow sending funds to a Sprout address. We will include this as part of a consensus change at a later date;
  2. Rollback Protection: We plan to put protections in place to mitigate the risks of rollbacks. This is a complex goal that will require a good amount of security analysis and discussion.

The team has begun writing specifications for the two Blossom upgrade goals, as outlined at the top of this post, and is aiming to complete the specifications by January 22. The team plans to begin work on the additional regular release goals listed over the next 2-5 months. Stay tuned for further updates as we move forward on the Blossom upgrade schedule.