This weekend, @adjychris posted a great summary that captures a summary of the event. This thread outlines the decisions that were made and our next steps. I’ll also post a few slides from my opening and the rationale for these decisions.
Work toward the full Zcash stack vision presented, by prioritizing based on expected and actual user adoption. Focus first on the experience for “first 100” power users who are in a position to onboard others adjacent to them.
- We will reach out to the Zcash Foundation about working together to find a path toward deprecation through zebrad with a target of 2024. Owner: @daira
- We will not add additional major features (such as ZSAs) into zcashd
- We may make minor updates to zcashd, depending on the identified path
Rationale: zcashd contains legacy code that hampers our ability to deliver more, faster. It is also duplicative with zebrad. By working with the foundation to add wallet support to zebrad and obtain parity, we can retire the code base, more easily onboard new developers and deliver more.
- We have not yet reaffirmed commitment to PoS as our first priority. Our decision will be based on how much time it will take to get to a release against other priorities. The next step is to determine a realistic timeline, to be done within the next two weeks. Owner: @daira. Supporting: @ebfull, @str4d and @nuttycom.
Rationale: We are emphasizing the delivery of capabilities that will drive adoption in the short to mid-term. With recent work, including Daira’s work on Crosslink2, and focused effort from the ECC team, we can see a path to hybrid PoW/PoS on testnet within months. But we need to factor in a number of other considerations including resource availability. If we do have a path that is months, rather than years, I’m personally in full support as it will help us unlock significant UX benefits for ZEC users.
- Based on the PoS timeline and user research, we will evaluate other potential areas for R&D. Near term candidates include: liberated payments, DEX support, bridge support. Owners: @daira and @joshs
Rationale: the team and community discussed options and weighted potential impact against complexity, cost and time. Those ideas that had the highest near term potential impact with the lowest complexity and time were weighted higher. We are working to further validate in conjunction with the Zashi team and based upon estimates for zcashd retirement and PoS work.
- We will ship Zashi 1.0 in March. Owner: Andrea. Supporting team: @adjychris, @nuttycom, @Honza, @Lukas, @Ren, @str4d
Rationale: Zashi will be our platform to deliver strong UX with rich features. We still have some work to do to finish Orchard support, background sync, Android feature parity, and a few UI changes. We need to get this to the market as quickly as possible, and iterate.
- We will conduct user research to validation hypothesis about feature prioritization. Near term candidates include: messaging app, liberated payments, DEX support, debit/gift card integration. Owner: Andrea
Rationale: The rationale under R&D is similar here based on the weight of potential impact against complexity and time. We also discussed rolling out a Zashi family of products that interoperate but with a narrow set of features. Examples include software that includes advanced features and integrates with hardware, and a standalone messaging app on top of Zcash with liberated payments for onboarding new users.
- NU6, governance and funding: Begin conversations with the community in February. Owner: @paulbrigner
- Release a new consolidated ECC roadmap in February. Owner: @joshs
- Zeboot: We will do it again, no later than this fall, but will need to rename it. Owner: Janie
I’ll post a summary of the first session below, with a bit of color on how we thought about users of early ECC products.