ECC restructuring and zcashd 5.6.0
ECC's restructuring was mentioned, and zcashd 5.6.0 is being prepared around the fast sync API.
Agenda summary 8
Foundation support for those affected by the ECC restructuring
Zcash Foundation · Pili
- Pili mentioned that ECC's recent restructuring affected several talented people, and asked anyone who wants the Foundation's support or wants to move into a new role in the community to get in touch.
- The Foundation will bring forward the second ZF minor grants process and announce it soon, and encouraged affected people to submit proposals and keep contributing until new opportunities arise.
Zcashd 5.6.0: lightwalletd fast sync API
Electric Coin Company · Daira, Kris
- The team is preparing the 5.6.0 release and focusing on refactoring the API between librustzcash and zcashd. A release candidate is expected around next week.
- The core of 5.6.0 is a new API that provides intermediate note commitment tree information to lightwalletd so that known notes become usable almost instantly. It is the last piece on the zcashd side for getting out of emergency mode.
- A light wallet SDK update follows within a few weeks. DAGSync does not apply to the zcashd built-in wallet.
Zebra audit results and stable release plan
Zcash Foundation · Marek
- One more release candidate will come out before the first stable release, containing network and security fixes. The user documentation (Zebra Book) was overhauled, the readme simplified and logging improved.
- The audit found one medium-severity issue and low and informational issues, and all were fixed except two performance-related ones. The auditors accepted this, no further findings are expected, and the report is being finalized.
- CI errors will be turned into PR comments, and the Abscissa version will be bumped.
FROST: speed optimization and a wallet integration proof of concept
Zcash Foundation · Deirdre, Conrado, Daira, Kris
- The IRTF draft moved on to the IRSG review stage. Changing 3-4 lines to use the existing multi-scalar multiplication in the group commitment computation made it more than 50% faster when there are many participants.
- It went into the generic layer of FROST core, so other FROST variants can gain it as well. The improvement came from implementation alone, without changing the protocol, security proof or assumptions, and a blog post is coming soon.
- Conrado built a wallet integration proof of concept that uses FROST for Sapling and Orchard spend authorization. It uses Ywallet's offline signing structure to export the sighash, randomizer and so on, then signs with FROST.
- It will be demonstrated at a community call around June 19.
- Chelsea is finishing the full security proof of re-randomized FROST (reddsa). Daira said similar proofs exist in the Sapling analysis paper and the foundational paper on re-randomization, and volunteered to review.
- Kris suggested looking at whether Ywallet's offline signing format is worth standardizing, and Conrado agreed that a standard format for transaction plans is needed.
ZSA update and the need to discuss ZSA fees
QEDIT · Vivek, Jon, Daira, Dodger
- The ZSA circuit was largely integrated into Orchard. Minor issues around split notes and nullifiers remain, and many positive and negative tests were added.
- Issuance and transfer RPCs were added to the client and rebased onto the latest zcashd, orchard and librustzcash.
- For the ZIP, old comments from the earlier PR were cleaned up, and the parts of the ZIP that will change because of implementation issues and improvements from new reviewers are in progress.
- Jon said the fee milestone was pushed to the very end. The proposal is to charge 1 ZEC for new ZSA issuance and to have ZSA transactions pay only the protocol weight so they are indistinguishable from ZEC transactions; opinions are divided and separate discussion is needed.
- Daira supported indistinguishability, since even assets with little usage need a single anonymity set to gain meaningful privacy. Daira said that if the purpose of the fee is preventing denial of service, there is no reason to distinguish them.
- Grant approval for the second stage (testnet, asset exchange) was obtained, and the goal is to unveil the testnet at Zcon4. Dodger suggested holding a separate Arborist call covering only fees, and said a community vote is also possible if needed.
Equilibrium red team preparation and DAGSync scope
Equilibrium · Equilibrium, Adi, Kris
- Equilibrium is preparing a red team exercise and sharing the problems it finds on Discord and the Zcash forum.
- When Adi asked whether DAGSync applies in 5.6.0, Kris answered that it does not apply to the zcashd built-in wallet. 5.6.0 is a change that computes additional note commitment tree data and exposes it to lightwalletd via RPC.
- Work on fetching this data on the lightwalletd side, caching it and providing it to wallets is underway, and Kris is handling the zcash client backend and the ECC wallet SDK update.
ECC roadmap and ZIP editor recruitment
Electric Coin Company · Deirdre, Nick, Daira, Conrado, Adi
- Deirdre asked how ECC's restructuring blog naming PoS ZEC as the top priority relates to ZSA and wallet priorities. Deirdre also asked what the statement about moving zcashd support and core protocol review outside ECC to the community concretely means.
- Nick said the priority remains getting out of emergency mode. The aim is to free Nighthawk, Edge and Unstoppable with three things: zcashd 5.6.0, the lightwalletd API update, and the follow-up SDK release.
- Nate is putting in place the structure for PoS research and will present it on the next call.
- The ECC wallet uses code based on iOS and Android (codename secant) as a testbed, and once emergency mode is over, the schedule for the first version will be published as a roadmap. The minimum scope is a minimal-feature light wallet client with a black-and-white high-contrast UI.
- Future zcashd support and handover to the community are not yet decided, and the plan is to produce a draft within 6-8 weeks before Zcon4. Adi welcomed that, with two node implementations, service providers get the option of switching to Zebra.
- Daira said there are currently only two ZIP editors, Daira and Deirdre, and they want to add more. Experience editing technical documents is useful and one need not be a cryptographer; people can read the responsibilities in ZIP-0 and contact the ZIPs channel on the R&D Discord.
Nighthawk global light client infrastructure and call schedule
Nighthawk Apps · Adi, Kris, Dodger, Daira
- Nighthawk announced global light client clusters in four places: North America, Europe, Singapore (Asia) and Brazil (South America).
- All are mainnet running zcashd and lightwalletd, developers and projects are invited to use this distributed infrastructure, and a Zebra-based version is also being considered.
- Kris said that an upgraded zcashd (5.6.0) needs a reindex to produce intermediate note commitment tree information, so support for a rolling approach that reindexes nodes in turn without service interruption would be good.
- Adi said they would handle it with a backup server.
- Dodger said the calls run on the ECC Zoom account, so recordings usually appear within 1-2 weeks. The time zone change (Daira said it is late in the UK and Europe) will be handled with a new link during the Zcon break.
This summary is based on the original meeting notes; check them for exact details.