Update: After reviewing the feedback from the community and discussing it internally, we’ve decided not to move forward with our proposal for a smaller NU7. Introducing another upgrade at this stage would create too much disruption for the ecosystem, especially given how much work is already underway across multiple fronts. In addition, questions raised about the release schedule highlighted that our proposed timeline for implementation was likely unrealistic once all the necessary steps were taken into account. We want to be constructive and collaborative in this process, which is why we think the best path forward is to step back.
While we will not be pursuing this specific proposal, we still believe there are opportunities for Shielded Labs to help improve the network upgrade process so that upgrades can ship faster and on a more regular cadence. That will be our focus going forward.
Our proposal for a smaller NU7 was meant to explore whether we could help Zcash regain momentum, reduce pressure on core engineering teams by taking greater ownership of the upgrade lifecycle, and streamline coordination with ecosystem partners. Ultimately, our motivation was driven by our desire to accelerate Crosslink. Since Crosslink will eventually require going through the full upgrade process, conducting a smaller upgrade now would give us an opportunity to build relationships, improve coordination, and address challenges in advance, which would ultimately make that larger effort more efficient. Although we are not pursuing that path, we still see opportunities to apply the same thinking to the upgrade process more broadly.
One way Shielded Labs can help is by contributing to process changes that make upgrades more predictable and less prone to the kind of delays we have seen in the past. This means putting greater emphasis on scope control and speed, accepting that some level of disruption is unavoidable, and prioritizing smaller, incremental steps over large, all-encompassing upgrades. Instead of tying releases to when every feature is ready, upgrades should follow a schedule, with features included as they mature. Running a dedicated testnet focused on faster upgrade cycles could also help us practice this approach in a controlled environment, allowing us to refine coordination, timing, and delivery before mainnet activation.
Another area where Shielded Labs can add value is by focusing on the needs of exchanges, mining pools, and other key partners. By speaking directly with them, understanding their requirements, and helping them adapt, we can lighten the workload on the core engineering teams and improve the overall upgrade experience. In practice, this could mean acting as software maintainers and providing responsive support, supplying libraries where needed, or even splitting partners into categories and tailoring solutions based on their setup. Taking on this role allows for greater specialization and customer focus, while also enabling work to be parallelized and decoupled across the ecosystem. The result would be a more efficient and resilient upgrade process that reduces bottlenecks and builds confidence that Zcash can deliver on a regular schedule.
We want to lead by challenging assumptions about what users and partners actually need during upgrades. For example, a common belief is that consecutive transaction format changes are highly disruptive for exchanges and create major obstacles that slow down the entire ecosystem. However, @pacu’s recent outreach to exchanges indicates that this impact may not be as severe as often assumed. In a conversation on Telegram, Binance described a straightforward workflow of reviewing the changelog, testing in QA, and promoting to production; they also build and parse transactions in house from node RPC data and said the most helpful support would be clear change documentation and example mainnet transactions. This points to communication and preparation as the primary constraints, not the transaction format changes.
Insights like this highlight the importance of direct engagement with exchanges and mining pools to understand their workflows, tailor support to their requirements, and ensure that scope decisions reflect real needs. Shielded Labs is well positioned to provide that kind of customer focus, which supports scope control and makes a schedule-based release cadence more achievable.
Our next step is to bring on someone at Shielded Labs who can take responsibility for this work. The role will require a solid understanding of consensus so they can advise and support engineering teams, as well as the ability to manage relationships with relevant stakeholders. It is similar to a developer-relations position in that it combines technical knowledge with communication and coordination skills. Having a dedicated person in this role will allow Shielded Labs to help accelerate Zcash and ship network upgrades faster and on a predictable schedule.
We want to thank @nuttycom, @arya2, @daira, and @str4d for their thoughtful comments and feedback. Their input helped highlight important considerations around timelines, scope, and implementation that informed our decision not to move forward. We also appreciate the broader discussion that this proposal generated within the community, and the net impact will help move the upgrade process in the right direction. Shielded Labs values open dialogue and constructive engagement, and we are committed to being receptive to feedback and making adjustments when needed. We look forward to continuing to collaborate to help Zcash advance.