Zebra audit report published
NCC Group published the final Zebra audit report, and the zcashd 5.6.1 hotfix was released.
Agenda summary 9
Zcashd 5.6.1 hotfix and lightwalletd release imminent
Electric Coin Company · Kris
- Hotfix 5.6.1 was released, fixing a bug 5.6.0 introduced in the Orchard wallet's note commitment tree management. Users who upgraded to 5.6.0 are advised to upgrade.
- It is known that since before 5.5.0, information about unmined notes can remain in the Orchard wallet.
- When 5.6.1 detects an inconsistency in which information needed for spending is missing, it rescans the Orchard wallet; in that case a rescan happens every time zcashd starts, which is inconvenient, and mitigation work is underway.
- The lightwalletd work is essentially finished and will be released once a few protobuf encodings are cleaned up. The librustzcash updates the ECC light wallet SDK needs to use the new infrastructure will also be finished by next week.
Work after Zebra 1.0.0
Zcash Foundation · Deirdre, Kris
- The 1.0.0 stable release was tagged about two weeks ago, and the team is integrating the latest crates such as ECC's incremental Merkle tree to support lightwalletd fast sync.
- It is running later than expected because crates moving from 0.3 to 0.4 changed serialization. Kris said the serialization code was only moved and suggested discussing it separately.
- Many PRs held back after the stable release were merged. Settings such as initial peers and logging were made easier to change in the Docker artifact.
- The contextual validation code in Zebra State, which the auditors said was hard to understand, was refactored and renamed. The next release will come soon.
Zebra audit completion report
Zcash Foundation · Deirdre
- NCC Group posted the final audit report on its blog and it will also be posted to the Zebra repository. The report is about 50 pages.
- The scope was all the Rust code of Zebrad plus some dependencies it writes or relies on directly, such as the Zcash script wrapper and Zcash proofs.
- The results were 1 medium-severity finding (the address book's management of peer address state is vulnerable) and low and informational findings, all of which have been fixed or merged.
- The remaining change is turning a panic that occurred when there were not enough blocks into an error, and it will go into 1.0.1 or 1.1.0.
- In the ed25519-zebra library, a problem where memory was not fully zeroized and a problem where secret data was logged through a debug implementation were fixed.
FROST update: demo and audit start
Zcash Foundation · Conrado
- Serde support for serialization used to exchange FROST structs was merged. A demo of everything FROST supports, including distributed key generation (DKG), is being built.
- The FROST audit starts next week with NCC. Chelsea notified the CFRG list of the specification change that hashes the public key in the binding factor computation, and there has been no objection yet. Once merged, the same change will be made in the library.
- A community call on how to apply FROST to Zcash will probably be held around next week.
ZSA update: nullifier derivation change
QEDIT · Vivek, Daira, Deirdre
- The ZIP focused on tidying equations and variable-name consistency. The implementation was rebased onto updates to the Zcash repository; Orchard and librustzcash are done, while zcashd remains.
- The nullifier derivation for split notes was changed. A final proposal that appears safe was settled on, based on suggestions from Daira and Sean, and it is reflected in the implementation but not yet in the ZIP.
- Daira explained that the nullifier derivation was changed for resistance to Faerie gold, where an attacker sees a transaction and blocks a note from being spent, and to roadblock attacks (spendability).
- Documenting the circuit changes in a separate PDF and linking it from the ZIP was discussed.
- Daira and Deirdre suggested placing it in the protocol folder of the ZIPs repository to prevent link rot, while the FROST security proof is a non-consensus document and goes in a separate FROST folder.
- Initial design ideas for asset exchange came up. To avoid the repeated revisions experienced while developing implementation and spec in parallel, the plan is to reserve a ZIP number in advance and flesh out the spec first.
Nighthawk update
Nighthawk Apps · Adi, Daira, Kris
- Parallel sync was introduced in the native iOS and Android apps, greatly improving sync speed, and performance and security were improved on top of the Secant project structure.
- For the distributed infrastructure, the team monitors the automation setup and upgraded the nodes from 5.6.0 to 5.6.1. The block explorer's mainnet and testnet frontends were also aligned with 5.6.1.
- Adi said DAGSync still has a long way to go, but parallel sync alone greatly reduced scan time. Daira and Kris said this is complementary to the other changes and that the first step of DAGSync is the librustzcash and SDK work.
hacspec implementation of Halo 2
Deirdre, Daira
- Independent master's students implemented most of Halo 2 in hacspec. hacspec is a functional subset of Rust that can be formalized in proof backends such as Coq, EasyCrypt and F*.
- It has the PLONKish arithmetization, the pasta curves and most of the Halo 2 proof system, along with a master's thesis.
- Since no formalization of Halo 2 existed before, it is significant; it actually works, but will not have the performance and memory optimizations of the ECC implementation. Deirdre said follow-up work is needed to connect it by showing it does the same thing as the production implementation.
- Daira said that even starting with weaker informal arguments than a formal proof, or quickcheck-style tests that compare on the same inputs, would greatly increase confidence, and expressed strong interest because it should be easier to maintain than Coq.
Call time zone change notice and ZIP editor recruitment
Dodger, Daira
- Dodger again announced the proposal to move the later call from 22:30 UTC to 21:00 UTC. Daira said it helps both the UK and the US west coast, and opinions can be left in the arboristcall channel on the R&D Discord.
- Daira said they are still looking for a third ZIP editor. Experience with document editing and standards helps, it is a volunteer position, and they asked people to read ZIP-0.
DAGSync status: librustzcash PRs and a common sync library
Electric Coin Company · Luca Campobasso, Kris
- Eiger's Luca, as a UniFFI grant participant, asked about the status of the DAGSync work in librustzcash and where help is needed.
- Kris said 1 incremental Merkle tree storage PR and 2 librustzcash PRs (831, 861) are under review and may be merged this week.
- The current stage is pre-DAGSync (fast spendability), not full DAGSync. The wallet queries scan ranges, including ranges to fill the note commitment tree and ranges related to wallet activity.
- What remains is the suggested scan ranges, and it is expected that even deploying full DAGSync will not need further lightwalletd changes.
- When Luca asked about a common sync library, Kris said the zcash client backend provides a common interface. However, because the two approaches manage state differently, it is uncertain whether the same API would fit.
- The discussion can continue in the walletdev channel on the R&D Discord and in the Light Client Working Group.
This summary is based on the original meeting notes; check them for exact details.