ECC update for March 1, Roadmap Edition

Hi Zeeps,

It’s v1 roadmap week!

To be agile and unstoppable is to flow. Whatever comes, we must move with it. We adapt, curling around and over obstacles, flowing with increasing momentum and purpose.

“Be water my friend”
To realize a new system, we must be like that, we must be water.

This new system will be user-friendly, widely available, shielded-only with optional disclosure. Its supporting infrastructure will be distributed, censorship-resistant and robust. Using Zcash, it will allow people everywhere to store and use ZEC without dependence on legacy choke-points and third party limitations. Yes, we want to be able to use ZEC within the old system where we can, but we also need Zcash to stand on its own. And just like us, the token must be unleashed to flow.

This is ECC’s current roadmap. Let me share my thinking and approach.

ECC Roadmap Q1 2024.pdf (61.0 KB)


The structure of the roadmap is based on agility, flexibility and speed. It’s designed to focus on user needs, what we learn, what others in the ecosystem do, and regulatory limitations we might face. We will move quickly, and strike where there is opportunity.

It is directional rather than fixed, flowing quarter to quarter, adapting as we go. The ECC team will update and clarify the roadmap once per quarter along with goals and timelines. Twice a year, we plan to invite Zcash community developers into our planning as we did with Zeboot.

The roadmap includes dependencies and assumptions. For example, we’ll explore DEX integration as we get closer to Maya support for Zcash.

We will ship quickly, get things out into the open, listen to user feedback and continue to build momentum. We welcome your participation. If you have skills that can help us, we’d love to work with you. We’ll also build things around your work in the community, incorporating the contributions of others.


The Official ECC Zashi Wallet

We currently plan to push major releases semi-annually, with minor releases in between. Major releases will include new capabilities, with minor releases delivering fixes and incremental improvements. Market and user research will be used to focus and prioritize our efforts.

The schedule includes candidates for research in the “User and Market Research…” row and we will prioritize building based on what we learn about potential impact for user adoption against cost and complexity. Our initial target users are the “100” existing Zcash power users, who want to make use of their tokens and onboard others. They want to see the token move and we want to enable them to give the token life through their actions.

For the remainder of this quarter, we will focus engineering efforts on the Zashi 1.0 releases and begin planning for 1.1 improvements. We will also begin focused work on messaging and liberated payments, which would allow users to send ZEC to someone within a message. This will flow into the other Q2 potential areas shown in the roadmap. As of now, these other areas are candidates, not commitments.

Zcash Protocol

Our core protocol work is intended to support the capabilities surfaced through Zashi. The user and market research will drive our protocol-focused priorities.

We will continue to devote significant time to research and design of a hybrid consensus design(i.e. PoW/PoS). However, we are resource constrained and I want to ensure that we also spend significant cycles on capabilities that we can deliver in shorter periods of time. We must multithread our efforts.

As such, the specific timeline for PoS/PoW will be elastic. If we can move faster, we will. If we get help from others, we can move faster. If we have the money, and there is talent available to hire, we will hire and accelerate further. We’re happy to work with the experts in the community if they would like to participate in our protocol related efforts, which may speed up our timeline.

I hope you are excited and motivated by all the possibilities we have in front of us!

A few other things we’ve been working on this week:


I was at ETHDenver most of the week, and I’m barely standing after days of meetings and late nights, or were those early mornings. A few chunks of time spent:

Scheming with the Brave team on use cases we can unlock for shielded users of the Brave wallet
Getting perspective and sharing our plans with the Grayscale team
Talking to a couple teams about potential partnerships and addressing concerns
Meeting with a couple potential financial partners
Catching up with old friends and ECCers including a mini Zeboot reunion of sorts with a number of folks that were in town

It was so good to see so many friends throughout the week!


@str4d @nuttycom @Lukas @Honza all continue to crank!

Thanks to @earthrise, the iOS portion of the security audit was completed with a few things to address but no show stoppers.

Work included Orchard support, ZIP 317 implementation, and we remain on track to release the iOS wallet later this month.

Android Beta version 0.2.0 was released that includes periodic background sync and an updated UI. We are currently on track to release the Android 1.0 wallet late April.

Andrea also got us up on a new product management tool and set up the process for how we’ll manage the entire product lifecycle.

Community Engagement

We began a process to more actively engage the community to gauge sentiment on key decisions and issues. Look for more on that from @paulbrigner next week!

ECC Brand and Website


@adjychris and @zeneo are currently updating the ECC brand and website to better reflect the new ECC, as well as content for Zashi. It’s looking badass fitting. Look for that to come out along with the Zashi iOS release. The team also plans to give you a much prettier version of the roadmap, updated once a quarter.


We’re still working through models and ideas for improved and streamlined financial and treasury management. As I mentioned in a prior post, we have a number of assets but have limitations due to liquidity and lock ups. All in all, I’m feeling pretty good about where we sit. That said, the current dev fund uncertainty makes some of this challenging.

You + Us

Those of us at Zeboot agreed that we need to do it again! I don’t yet have a name for the next one, but we’re tentatively looking at options for July to coincide with our Q3 planning. Man, that seems like such a long time from now. But I think it works well with all the other things going on.

Feeling the flow yet? Yeah, me too.



Thanks for posting another ECC update this week. I always enjoy reading your posts.

I have a question regarding the POS. Since you mentioned that you have limited resources, what about ZCG getting a Grant to support Hybrid PoW/PoS (or funding ECC?) I think we should focus on the Hybrid PoW/PoS transition more than anything else right now.

There are a lot of great developers in the Zcash community, and I’m sure they can help speed up the POS transition.


I like these updates


Totally agree. Hybrid PoS should be highest priority.

1 Like

Great update @joshs, as a zodler u have my respect :saluting_face:. Don’t lose focus and keep building!


Why do you think this?

What happened to ZSAs?


ZSAs are on there, in the Zashi timeline:

Not sure about the protocol level changes required though. Approx Q1 next year, I assume because of wanting Zcashd fully depreciated before activation?

Also, welcome back to the forum @Matthewdgreen :slightly_smiling_face:



Qedit pivoted to working on ZSAs in zebrad as we’re retiring zcashd. We’re going to explore adding them to Zashi as early as Q3, assuming there is something available to test.

Earliest potential activation for ZSAs is NU7 / Q1 '05.


[ECC R&D Engineering manager hat]

Yes, exactly. Since ECC does not intend to implement new major consensus features like ZSAs in zcashd, our expectation is that whatever NU activates ZSAs will cause any remaining zcashd nodes to stop following consensus (unless someone else implements them for zcashd). Therefore, zebrad must be ready for zcashd users to migrate to it before that happens.

As @joshs says, Q1 2025 is the earliest that an NU containing ZSAs could realistically activate. (Not '05, he’s making me feel old ! :sweat_smile: )


Who knows, Josh could be referring to 1905 or 2105 :joy:


Well written post that has some great elemental/philosophical undertones that invigorate the adventurous spirit of navigating the expansive water ahead. 2024 - z-Cash - Enter The Dragon. <3

P.S. I think its become a nautical map. :wink:


Love the roadmap, this is exactly what Zcash and the community needs :tada::clap:.

I hear you :eyes:.

1 Like

I think the timelines are incredibly optimistic. We’re already into Q2, and there’s supposed to be ZSA integration by Q3? I’ll take the over on that.

However, if you actually hire and onboard more engineers, it might be justifiable.

And what do “Cross chain activities” even mean? I think this roadmap can use less breadth and more focus, overall.

Q1…not Q2…

Those are potential areas of research and design, not delivery dates. We believe the best case for ZSAs in the protocol is Q1 of next year.


In the real world, most SEC reporting companies are not launching products up until the end of the month. Sprints are typically wrapping up this week and next so enough data can be gathered for the earnings report(s).

Time to hire another engineer or three.

1 Like

POS is not good. POW gives intrinsic value of a coin. Otherwise we should adopt PPC

So I’ve just downloaded de Zashi wallet.
For receiving I see only Unified Address ( addresses that starts with u) and transparent addresses ( addresses that start with t)
Where are the shielded addresses ? you know the ones that makes you anonymous and respect your privacy? where are the z type o addresses?

Also it says that can’t transfer transparent addresses? what is this?


u addys are the new z addys :wink:
aka u addy includes z addy, u(orchard) addy and t (transparent) addy