zcashd maintenance and NU6 deadline discussion
Discussion that the NU6 deadline makes the move to Zebra urgent led to a decision to recruit a task force to maintain zcashd.
Agenda summary 8
Zebra 1.5.0 and the Sapling scanning design debate
Zcash Foundation · Marek, Pili, Kris, Str4d, Daira, Dodger
- Zebra 1.5.0 was released this week. It includes networking improvements and fixes, including those reported by the Ziggurat team, and the biggest addition is shielded scanning support.
- When a Sapling viewing key is put in the config file, Zebra scans the chain and stores txids and keys, and a separate tool prints the memos. A demo of reading Zecpages posts is possible. It is a viewing-key-only feature, not a wallet.
- Citing the pain caused by the zcashd wallet being tightly coupled to the node, Kris recommended separating scanning into its own process communicating over the light client protocol.
- Str4d proposed a separate process that shares the full node's immutable DB (RocksDB) instead of using the light client protocol.
- Pili replied that this MVP is not for production use and that issues have been opened, such as running it on a separate Tokio executor to prevent timing attacks.
- Daira said the architecture should not be decided in a few minutes, and that the protocol needs careful analysis.
ECC update: Sapling extraction, NU6 and Zcashd transition
Electric Coin Company · Kris, Str4d, Nate, Dodger
- Extraction of the sapling-crypto crate from librustzcash is largely done. It was restructured to match the Orchard model and will be released after a few more changes.
- One benefit is that, for uses such as Brave, Sapling functionality can be turned off with a feature flag. Work on adding Orchard support to zcash_client_backend is progressing quickly.
- Before 5.7.0 reaches EOS in mid-January, a new Zcashd release is planned for early next week, mostly changes that raise the EOS height.
- Nate said ECC plans to gradually reduce its Zcashd support and will set up a task force to examine whether another team can take over maintenance. Kris will soon issue a call for participation.
- Kris pointed out that nodes for next year's halving must be deployed by July at the latest, and that if no one is going to implement the NU6 consensus rules in Zcashd, the network must be moved to Zebra within 5-6 months.
- Daira explained that extending the Dev Fund can be implemented fairly simply with the existing funding stream mechanism.
Trailing Finality Layer update
Electric Coin Company · Nate, Daira
- Three tasks are underway: consolidating the Crosslink documents on HackMD into the book, improving the simulator, and starting a prototype combining Zebra with CometBFT (formerly Tendermint).
- Daira implemented the educational BFT protocol Streamlet in the simulator, and tests detect safety violations. The team is also considering recording BFT safety violations on the chain as evidence when they occur.
- The plan is to finish the milestones for the three tasks by the end of January and give an in-depth Crosslink presentation on the early February Arborist Call. The staking approach or delegation, the number of validators, yield and so on are not yet decided.
- Daira also raised the trust trade-off of whether to put BFT proposers and validators on separate networks. People were directed to send opinions to the forum thread, the TFL book GitHub, or the PoS channel on the R&D Discord.
Zcash Sustainability Fund and ZIP update
Shielded Labs / Eiger · Tomek, Daira, Str4d, Jon, Pili
- Tomek added a ZSF deposit field to ZIP-230, the v6 transaction format ZIP (zips PR 745), and also posted an update to ZIP-244 for transaction IDs and signature digests (PR 748).
- Daira explained that since it breaks v5 compatibility, a separate ZIP for v6 is needed. An estimate of the impact on miners was added to the 60/40 fee split ZIP.
- Using a simplified ZIP-317 model based on the last 100,000 blocks, it was estimated that about 800 ZEC per year, about $24,000, would go to the ZSF. It was pointed out that the estimate does not filter out spam transactions and so may be an overestimate.
- Daira asked whether such a small amount is meaningful, and Nate answered that the impact grows as total fees increase and that the ZSF could serve as a destination for other fees or burning.
- ZSF is being implemented in Zebra, building on the v6 transaction PR posted by QEDIT. Pili explained that the PR is for validating the approach and not intended to be merged, and QEDIT budgeted v6 support separately from ZSA.
FROST demo and ZIP update
Zcash Foundation · Conrado, Str4d, Daira
- The work of adding socket communication to the demo is expected to finish next week. The FROST ZIP review resumed after waiting for Chelsea's security proof, and Str4d's comments are being addressed.
- They also took on writing the implementation section of the proof paper and plans to publish it on ePrint. Str4d asked why secp256k1 signatures come out as 65 bytes.
- Conrado explained that this is because that cipher suite is a NIST/SEC standard format that is not compatible with Bitcoin Schnorr.
- An external contribution PR adding a cipher suite compatible with Bitcoin Schnorr is in progress and may be ready early next year.
ZSA update and v6 transactions
QEDIT · Vivek
- The ZSA protocol ZIP is largely stable and ready to merge. Initial v6 transaction support was added to Zebra (Zebra PR 7978).
- An external tool for testing v6 transactions in Zebra is being built, and the halo2 crate changes are being coordinated for merging with ECC. There has also been progress on the issuance authorization signature changes. The atomic swap proposal was presented to ECC.
- The discussion concluded that no additional circuit changes appear necessary beyond the circuit changes for ZSA.
ZSA regulatory response proposal and exchange pressure discussion
QEDIT · Jon, Daira, Kris, Dodger
- Against the background of discussion about a possible Binance delisting, Jon said they will propose bringing forward the exchange integration standardization and consent-based identity linking features that were on the ZSA roadmap for mid-2024.
- The approach is to standardize note contents and disclose them when the user wants. Daira pointed out that the exchange-specific address proposal is circumvented if one goes through a temporary T address, and that it must be clear what the regulatory requirements are.
- Daira said features that reduce privacy beyond the requirements should not be included.
- Kris asked whether viewing keys, OVK sharing or payment disclosure are not enough, and said US-regulated exchanges already support Zcash.
- Dodger thought Binance's decision might be due to the cost of additional due diligence. Jon shared what was discussed with law enforcement at the November 30 ZK proof policy event in Washington. The discussion will continue in the forum thread.
Wrap-up: follow-up discussion format and year-end schedule
Nate, Dodger
- Nate said there were many topics for in-depth discussion and proposed arranging a separate meeting or a topic-focused open discussion. Nate asked people to send desired topics to arboristcall@zfnd.org.
- After the year-end break, the next call is the early slot on January 11 at 15:00 UTC.
This summary is based on the original meeting notes; check them for exact details.