NU6 candidates and the zcashd deprecation plan
Participants held a long discussion of NU6 candidate features, the ZIP process and the zcashd deprecation schedule.
Agenda summary 7
ECC update: zcashd 5.9.0 and follow-up work after the Zashi launch
Electric Coin Company · Daira, Kris, Str4d, Andrew Arnott
- zcashd 5.9.0 RC1 was tagged. The last working full release is about to hit its EOS halt, so this is the top priority this week, and the final 5.9.0 is to be tagged the next day.
- They fixed bugs and edge cases found during the Zashi launch. A representative one is the DB migration that ensures existing wallets' unified addresses have an Orchard receiver.
- Last week they made roadmap plans, and Josh posted the Q2 2024 roadmap on the forum. Daira added target tickets and a rough dependency graph for NU6 and NU7 deployment to the core DAG (zcash.github.io/developers).
- The problem of static binary projects breaking because of a build system bug in Xcode 15.3 was fixed in the latest iOS Swift SDK.
- They said bug reports in librustzcash that block other wallets' transaction interpretation and account recovery are now handled as top priority.
Zebra 1.6.1, per-organization DAGs, and integration test preparation
Zcash Foundation · Alfredo, Arya, Str4d, Kris
- They are improving the getblock RPC to be compatible with zcashd. At community request they added a block time field, and thanks to an external contributor the disk size at startup and shutdown is shown in human-readable units.
- Zebra 1.6.1 includes the first version of a Swagger-style OpenAPI specification for documenting the RPC.
- Regtest support is also in progress; it is meant to bring up a private network to make developing network upgrade features easier, and is part of the zcashd deprecation process.
- Arya plans to create a genesis block for regtest, add the minimal fields and then improve compatibility, and said PoW is turned off until the internal miner is restored.
- Str4d said they will land within a week a cleaned-up equihash crate that merges Teor's changes, and that the multi-parameter solver needs further work. The Zebra team's DAG generation script is failing because of its ZenHub dependency.
- ECC also uses ZenHub only as a data store and asked for cooperation on alternatives. There was a proposal to set aside dedicated time for the zcashd deprecation work on the Arborist Call, and Daira and Str4d agreed.
FROST demo stage 2
Zcash Foundation · Conrado, Dodger
- They are wrapping up stage 2 of the FROST demo, which adds internet communication, and only one PR remains to review. The server handles communication between participants and the coordinator, so the demo now works without copy and paste.
- As a next step, aiming at a solution wallets can use when deploying FROST, they are planning the server's user registration approach and encryption and authentication of communication between participants. Much of the work involves little cryptography, so they recruited contributors.
Zcash Sustainability Fund status and requirements for inclusion in NU6
Shielded Labs / Eiger · Jason McGee (written), Str4d, Daira, Dodger
- Jason McGee said in writing that the Zebra integration is about 70% complete and can be made to fit the NU6 release. Jason McGee asked about the deadline required for inclusion in NU6 and said the governance expectations, such as gathering community input, are unclear.
- Str4d said there were parts of the ZIP that were not yet clear enough to implement and welcomed the implementation progress. Str4d said that before going into NU6, the ZIP specification and both the zcashd and Zebra implementations must all match.
- Daira said that at the ZIP editors' meeting there was an opinion that more economic motivation and expected effects (funding, miner selling pressure) are needed. The key is whether the community agrees on the fee ratio and the issuance smoothing parameters.
- The related PRs are 703, 706, 718, 745 and 748. To go into NU6 it must be reflected in both Zebra and zcashd and audited, and since ZF's finances are limited, cost sharing needs to be discussed.
- There was an opinion that the audit should cover NU6 as a whole rather than per feature. If complexity is too great, they could include only the ZSF definition (the v6 transaction change and node accounting) and exclude issuance curve smoothing.
- The interaction between the Dev Fund proposals and issuance smoothing must also be analyzed.
Z|ECC Summit announcement
Electric Coin Company · Josh
- Following January's Zeboot, they decided to hold a community event every quarter, matching ECC's quarterly planning cycle, and the name is Z|ECC Summit. The next one is in San Diego in July.
- Seating is limited, and active developers in the Zcash ecosystem can register through the forum post.
Network upgrade planning: transient testnet and the ZIP process
Dodger, Str4d, Daira, Arya, Andrew Arnott
- Str4d stressed that a transient testnet refreshed weekly or biweekly is needed so people can test implementations even before things are finalized.
- The approach is to bring up a new network for each feature branch with a GitHub Action and test only consensus features without PoW. ECC's roadmap has a transient testnet for NU6 in June.
- Daira said they use the core DAG as the reference for NU6 and NU7 work dependencies. Dodger shared the checklist used for NU5. ZIPs progress from draft to proposed, implemented and active, in that order.
- Str4d suggested merging drafts into main in small units rather than long PRs, and finishing the full review and specification audit at the proposed stage. ZIP-0 says there must be a deployment method when moving to proposed.
- Dodger said the practice of doing the specification and implementation at the same time was a burden for the Zebra team, and Str4d said implementers will show up separately once an idea gains popularity.
- Andrew Arnott pointed out that ZIP-320 was implemented in wallets even though it is a draft, and raised the PR discoverability problem. Opinions were raised to publicize the difference in strictness between the consensus track and wallet-level ZIPs and to lower the barrier of the ZIP writing guide.
NU6 and NU7 candidate items
Str4d, Daira, Dodger, Kris, Arya
- The NU6 candidates are ZSA, the 3 ZIPs of ZSF, an explicit fee field, the memo bundle, and a Dev Fund funding stream change. An explicit fee lets history be displayed without looking up inputs.
- The memo bundle is a structure in which each output has a memo key instead of a 512-byte memo per output, decrypting the multiple pieces of the bundle. It helps with authenticated reply addresses and payment disclosure, and they plan to use Padme padding.
- For the Dev Fund they are steering toward proposals within what the current ZIP-207 mechanism can implement. Daira said they would propose a plan splitting it one third each among ZCG, ZF and ECC for two years.
- Detection keys (raised by Arya) and post-quantum privacy were mentioned as NU7 candidates. Detection keys have no concrete proposal so they cannot make NU6, and aiming for an upgrade next April would require being ready by August or September.
- Daira said that to prevent harvest-now-decrypt-later attacks, hybrid post-quantum note encryption could be considered. Daira said scalability and smart contracts cannot go into the same upgrade as ZSA.
- Because the NU6 specification schedule is tight, they decided to hold an additional meeting next week and deal with ZSF first. Daira added that flexibility is needed to remove an item if a security problem arises.
This summary is based on the original meeting notes; check them for exact details.