Orchard circuit layout bug fix
A Halo 2 circuit layout bug that made Orchard proofs fail on 32-bit environments was resolved and will be included in the next crates.
Agenda summary 9
Zebra test mining and audit progress
Zcash Foundation · Pili
- The default mining feature implementation for Zebra is complete. Several team members are contacting mining pools to ask whether they are willing to test, and if pool operators or solo miners want to test, the team assigns a contact to support them.
- In recent weeks the team took a break from the 20% time it spends on personal Zebra-related projects, and will publish the results as blog posts.
- The team received the first update from the Zebra audit team and began creating an issue for each finding.
Orchard circuit layout bug
Electric Coin Company · Jack Grigg, Daira, Nathan
- A circuit layout problem was found in Halo 2 Orchard proofs on 32-bit environments and has been resolved. Part of the layout depended on the behavior of an unstable sort function, so a change would alter the verifying key.
- According to Daira, 32-bit platforms and recent Rust versions (after 1.69 or 1.70) were affected.
- The fix will be included in the next orchard crate and Rust crate updates such as zcash_primitives 0.11, and is waiting on a reddsa release.
- In theory it could have affected consensus, but nobody runs consensus nodes on 32-bit, and zcashd would likely have caught it in tests during the latest Rust upgrade.
- The actual impact was that Orchard funds could not be spent in the affected wallets; no funds were lost.
- Kris said the overhaul of the zcashd wallet's transaction construction internals is nearly done, and that ZIP 317 support for the wallet and for mined block construction goes into 5.5.0. 5.5.0 is expected in 3 to 4 weeks.
FROST RFC approval and implementation updates
Zcash Foundation · Conrado, Deirdre
- The RFC received review from the CFRG chair, mostly editorial issues, so the goal is to address them this week and move to the next approval stage.
- Natalie is implementing in FROST the ability to recover a lost share. Participants at or above the threshold help via the protocol, and only the lost share is restored without reconstructing the whole secret.
- A FROST demo program (share generation and signing) is planned, doubling as flow verification and a developer example. A recommended implementation of the broadcast channel needed for key generation is also in the planning stage.
- The core and re-randomization crates were just published, and the FROST crates are all 0.1.0. reddsa's re-randomized FROST support is under ZIP 312 review, so it is an experimental feature that is off by default.
ZSA update and spec corrections
QEDIT · Vivek, Daira, Nathan
- Meetings to finalize the ZIP are going well. The asset identifier definition was changed internally and the naming tidied, and issuance key derivation follows the ZIP 32 procedure but is set independently of Orchard keys.
- The discussion on using split notes instead of dummy notes for ZEC notes as well is unresolved, and Daira will review it. The circuit needs a per-asset base point, so variable-base scalar multiplication is being implemented in the value commitment, and an issuance RPC was added to the client.
- QEDIT is planning follow-up ZSA proposals including atomic swaps and NU6 items. Daira said there will be a protocol spec update containing retroactive application of ZIP 216 and small Sapling-related corrections.
- Nathan said they are considering the Zcash community forum or GitHub Discussions as candidates for an asynchronous research discussion forum.
ZIP 317 timeline and 5.5.0
Electric Coin Company · Jack Grigg, Kris
- zcashd 5.5.0 is expected in 3 to 4 weeks, and what sits upstream of the 5.5.0 node in the developer DAG is included. It includes the Halo 2 32-bit fix and ZIP 317.
- 5.5.0 puts ZIP 317 block production and fee selection into the zcashd block generator and wallet. After that, mobile SDKs only need to enable the already-deployed feature.
- Zebra implemented ZIP 317 for block production, and has no wallet. Kris said that even for wallets that do not use the SDK directly, such as Zecwallet Lite and Ywallet, the necessary parts are in librustzcash.
FROST adoption discussion - ECC wallet and zcashd
Jack Gavigan, Jack Grigg, Nathan, Deirdre
- Asked whether ECC plans to put FROST into zcashd or a wallet, Jack Grigg said there are currently no plans.
- They said shielded multisig is better as a separate binary outside zcashd, and that a partially created transaction, the Zcash counterpart of PSBT, must come first.
- Nathan said the first ECC wallet will contain only very basic features, and FROST could be explored to reduce the sharp edges of secret management such as social recovery, but there is no roadmap.
- Deirdre explained that the requirements for FROST signing and key generation differ. Trusted keygen with a dealer is easier and a full DKG needs a broadcast channel, and they said the team can help find a design suited to the usage environment.
- Jack Grigg proposed a local 2FA-style use case like Casa's, where a device acts as dealer and spending is done with 3-of-5 devices. They said a presentation at the biweekly community wallet developers meeting would also be welcome.
Zebra audit and responding to eclipse attacks
Zcash Foundation · Deirdre, Daira, Jack Grigg, Jack Gavigan
- An auditor from the audit firm NCC asked about the history of responding to network-level eclipse attacks, so Deirdre asked whether the zcashd side had analyzed it.
- Daira said zcashd has complex code (built up in Bitcoin Core) that groups addresses by subnet and the like, but they do not know how effective it is. Zebra does not appear to have origin-based handling.
- Jack Grigg cited limiting outbound connections to one per group so that inbound data cannot dictate outbound ones. Because the chain is shared global state, a single outside connection is enough to recover, so it is more resilient than pure P2P.
- The DNS seeder also uses heuristics such as protocol compliance, version and height compatibility, and long-term uptime. Jack Gavigan said to lower its priority and defer it to a new DNS seeder and a technical debt review.
Funding route for security researcher grants
Deirdre, Jack Grigg, Daira, Jack Gavigan
- Deirdre asked about the funding route for researchers who would analyze the security of the Zcash protocol.
- Jack Gavigan suggested, depending on size, a Minor Grant (deadline in 11 days) or Zcash Community Grants, and told them to post the idea on the forum first.
The Halo 2 specification and PLONKish arithmetization
Deirdre, Jack Grigg, Daira, Jack Gavigan
- For a researcher who wants to implement Halo 2 in a formal specification language, Jack Grigg said Section 4.2 of the Halo 2 book is the formal description of the currently deployed proof system.
- Daira said an independent implementation is possible but requires some reverse engineering, and there has not yet been a review cross-checking it against the code.
- The name Halo 2 does not imply a Halo 3 will appear, and after adding recursion it is still called Halo 2. Because there is no trusted setup, migration is easy even if the circuit changes, and supporting two arithmetizations is a big undertaking.
- Daira introduced a way to represent non-zero rotations with abstract columns and hints. Abstract columns shrink the circuit and make analysis easier, and incorrect hints cause no correctness problem. They roughly estimated the performance difference of compiling the abstraction at about 3x.
- Daira and Jack Grigg said PLONKish contains all known arithmetization optimizations and has more freedom in multiplication than R1CS, so it will be kept going forward.
This summary is based on the original meeting notes; check them for exact details.