ZcashD retirement delayed to early 2026
Emergency response to the price surge pushed the ZcashD retirement steps back to early 2026.
Agenda summary 8
Zebra update
Zcash Foundation · Arya
- A release candidate for the NU 6.1 rollout was tagged and published.
- It also includes a fix for the initial-sync performance regression, cutting sync from 24 hours to about 8 hours.
- Assembly code was added to the script output of the getrawtransaction and getblock RPCs, and a build problem was fixed.
- PRs refactoring the state service and other service traits were merged, and error-type improvements for requests such as commit checkpoint verified and commit semantically verified are in progress.
- A PR is open to cut build time by using a RocksDB installed on the system.
ECC core update
Electric Coin Company · Str4d
- As the price rise brought more Zashi users and a flood of bug reports, the team spent much of the past two weeks fixing root causes in core Rust crates such as zcash_client_backend.
- They fixed state-management problems exposed by the introduction of mempool detection, and problems with the reduced-confirmations handling shipped in September and October.
- The send max feature has been carried through to the Swift SDK layer.
- Support for one-time transparent (ephemeral) addresses, for uses not handed directly to users such as swap refund addresses, has been merged into the SDK layer and is at the bug-fixing stage.
- A second Zallet alpha will come soon, with bug fixes and user feedback included.
- Thanks to Anton of StageX, the next release will offer reproducible builds.
- Kris is working on account deletion in the wallet backend, to solve the problem that Zashi currently has to be reset to disconnect a Keystone device.
Zaino update
Zingo Labs · Za
- Considerable progress was made on integrating the chain index interface to support Zallet, expected to land before the next Arborist call.
- Existing code is being moved to a trait-based generic pattern to reduce duplication.
- Test infrastructure is being upgraded to verify chain-fork handling, and it must be upgraded to use the service traits of Zebra 3.0.
- The next priority is adding transparent data to compact blocks, to reduce how much of the transparent transactions a user cares about is exposed to the server.
- Four block explorer RPCs are under review.
zcashd retirement update
Electric Coin Company, Zcash Foundation, Zingo Labs · Pacu, Daira Emma
- Review of retiring lightwalletd has begun.
- lightwalletd is receiving the last feature, adding transparent data to the compact block processor; this is also being implemented in Zaino, and porting lightwalletd features to Zaino is nearing completion.
- The RPCs for block explorers are nearly done, so the Nighthawk block explorer is ready to be integrated with Zebra and Zaino.
- Indexing transparent data from the genesis block lets users who have held transparent ZEC since the early days bring it into a modern shielded wallet, and it also helps Ledger support shielded ZEC.
- However, lightwalletd sync can take a long time.
- Daira Emma explained that including transparent information in blocks improves privacy and simplifies the complex logic that tried to work around it.
- Pacu said urgent production work has pushed the zcashd retirement work down the priority list, so the retirement steps are only possible in early 2026.
- A ready-to-start task board is being built in the Zallet repository for collaboration.
ZSA discussion
Daira Emma, Nate, Alfredo
- Qedit did not attend this time slot.
- Nate said some people want to bridge Bitcoin to ZSA and they would connect them with Qedit.
- Daira Emma reported that work has started on extending PCZT to support ZSA.
- According to Alfredo, ECC postponed the Orchard ZSA review because of last-minute bug fixes, and they understand it will start around next week.
- Daira Emma also said they hope to start soon.
Network Sustainability Mechanism (NSM) update
Shielded Labs · Jason
- The ZIP 233 PR was updated and rebased; it passed all CI checks and tests and is only waiting to be merged.
- Daira Emma apologized that the review is their part and they had not yet done it.
Crosslink update (Trailing Finality Layer)
Shielded Labs, Electric Coin Company · Nate, Jason, Daira Emma, Alfredo
- Some on X argue for PoW and say Crosslink should be postponed, but the plan is unchanged.
- The plan is to finish the prototype, tidy up the specification and assess confidence, then rewrite the production code and harden the design.
- Milestone 4a is finished.
- A recurring crash bug from the previous workshop was fixed so most participants got onto the roster, and internally the team switched from Malachite to its own BFT implementation, which runs without problems.
- Milestone 4b is adding a delegation field to transactions.
- For now the visualization tool creates fee-free transactions using fake units; the real wallet stack will be connected later, aiming for a workshop in early December.
- Daira Emma advised using Zallet, which can be used long term, instead of the Zcash dev tool.
- An external audit of the economic design will come after the prototype stage, and the roadmap is to finish the prototype by mid-Q1 next year.
- Jason asked for comments on the staking design blog post published this week.
- When Alfredo asked when the ZIPs would be written, Nate answered that work would start in early next year, around the time of the prototype.
Open discussion: quantum recoverability, Zallet sync status, ping RPC
Daira Emma, Alfredo, Str4d, Arya
- Daira Emma said the long-prepared quantum recoverability draft is ready for review and asked someone familiar with post-quantum security analysis to review it.
- Alfredo said that testing is hard because Zallet's sync height cannot be seen except in logs, and requested a status-check RPC.
- Str4d replied that, unlike zcashd's regtest-only sync logic, it is better to design it as a separate RPC.
- Str4d suggested a general health API indicating things such as whether the node is following the chain tip, which could contain a regtest-only field.
- They agreed to open an issue and discuss it.
- Arya asked whether Zebra would implement zcashd's ping RPC and the latency field of getpeerinfo.
- Str4d and Daira Emma answered that ping is for debugging and has been abused in side-channel attacks, so it is better not to implement it.
This summary is based on the original meeting notes; check them for exact details.