Memo key: note plaintext vs KDF debate
Participants debated whether to put the memo bundle key in the note plaintext or derive it with a KDF.
Agenda summary 7
ECC update: Binance TEX address RPC and Zashi exchange rate conversion
Electric Coin Company · Kris, Str4d
- They are catching up on wallet maintenance and bug fixes that came from the Zashi launch after ZconV. Binance asked for a zcashd RPC method that can check TEX address conversion, and after discussion they agreed to add it.
- This is because Binance said it would not proceed otherwise. They discussed the approach to Zashi's exchange rate conversion.
- The goal is an approach in which exchange rates are obtained verifiably so lightwalletd cannot manipulate them, no unnecessary information is exposed to the rate server, and it is robust against rate manipulation.
- Most cryptocurrency exchange rate APIs do not account for this, but they thought it would be possible on top of existing APIs. They also continued the discussion of NU6 and NU6 memos.
Zebra 1.7.0 and the regtest tutorial
Zcash Foundation · Alfredo
- They released Zebra 1.7.0 on the Monday before ZconV started. The key items are regtest and custom testnet support.
- Because of concerns, they reverted the end of support period, which they had said on the last call was extended from 16 to 20 weeks, back to 16 weeks like zcashd. They are writing a regtest tutorial for using the new features.
- They also resumed upgrading the ECC dependencies Zebra had fallen behind on (zcash_primitives, zcash_client_backend, zcash_proofs and others), but it is not easy.
- A PR fixing the gettreestate bug reported by Andrew Arnott is open.
ECC and ZF zcashd deprecation work
Electric Coin Company / Zcash Foundation · Str4d, Kris
- They discussed further the composition and division of responsibilities of the scanning and indexing services, and also confirmed follow-up work to sort out the kinds of data needed to build the services.
- Work is in progress to integrate the Rust script engine implementation being ported from C++ into the zcash_script Rust library.
- It can be cross-tested against the existing C++ verifier, and even once complete, for safety it is likely to be switched over by a network upgrade, as with the past Libsodium replacement. They are heavily refactoring the zcash_primitives transaction builder.
- The purpose is to let applications that do not use the Sapling dependency (Brave ships only transparent and Orchard) drop the Sapling crate, and separating signature creation from the build also makes integrating the hardware wallet signing stack easier.
ZSA ZIPs and the integration meeting
ZIP editors / QEDIT · Str4d, Daira
- The regular spec design meeting between the ZIP editors and QEDIT, which ran for several months, has now become an integration meeting that reflects the accumulated changes in the codebase. This week's meeting covered the parts to reflect first in note encryption and the halo2 gadget changes.
- ZIP-227 currently requires full nodes to track only finalized assets.
- There was discussion that a rule like ZIP-209, which tracks the total issued amount per asset so the value does not go negative, is also needed, and they are also discussing whether to distinguish the fees for defining a new asset from those for additional issuance of an existing asset.
- They organized design considerations for asset name collisions and wallet UX. ZSA wallet recommendations could be added to ZIP-315 or become a separate ZIP.
FROST demo and the TFL talk
Zcash Foundation / Electric Coin Company · Conrado, Daira
- It was presented at ZconV, and once the last PR is merged anyone can run the demo themselves. It is a demo that runs FROST on different machines through a server.
- To make the server production-grade, they are refactoring to implement a user registration mechanism, encryption and authentication. Natalie is finishing the refresh shares feature.
- Daira corrected that they gave a TFL talk at ZconV and that there is no new news on this call. All talks can be watched on the Zcash Foundation YouTube channel.
Announcement: the My First Zcash workbook
Mass Adoption · Jack Gavigan
- Elise introduced the educational workbook My First Zcash that they worked on. It covers money, decentralized cryptocurrency and an introduction to Zcash.
- The community completed it together, and it is on GitHub, where you can leave feedback as issues.
Memo bundle design: whether to derive the memo key with a KDF
Electric Coin Company · Str4d, Daira, Kris, Conrado, Arya
- Hanh proposed deriving the memo key from a shared secret with a KDF instead of putting it in the note plaintext. The draft is the simple approach of replacing the memo field in the note plaintext with the memo bundle decryption key.
- In the KDF approach each output gets its own unique memo key, so sharing a memo requires a separate structural memo. If the shared memo is given to all recipients there is no data saving, and the small key fragments could reveal whether a memo is shared.
- Daira, Kris, Conrado and Arya preferred the original design of putting a 32-byte key in the note plaintext, because the indirect structure is complex and makes circuit proofs harder.
- Grounds were also given that shared memos matter, as in the example of Ywallet replicating the same memo into each change output. Str4d pointed out the advantage that the KDF approach is a step closer to fine-grained payment disclosure that reveals only the note value and hides the memo.
- The experience was also mentioned that Sprout used two keys, payment disclosure was hard, and Sapling reverted this. A memo bundle can be encrypted with any key, so the KDF key could be added as a wallet standard outside consensus.
- They also discussed a nested memo approach in which an authenticated reply address is included only once and referenced from each recipient's memo.
This summary is based on the original meeting notes; check them for exact details.