ZSA stablecoin roadmap discussion
The ZSA team said it will include stablecoin support in its 2024 roadmap.
Agenda summary 5
Zebra 1.6.0 and the ZF hackathon results
Zcash Foundation · Arya, Pili, Daira
- They added key registration and result stream methods to the Zebra scan gRPC, and also put in gRPC server reflection and Zebra Book documentation.
- They improved CI for external contributor PRs, added scan work tests and then released zebrad 1.6.0. At the hackathon sprint they restored Windows support in zcash_script and also put out an alpha release of the Zebra app.
- Conrado solved the Windows problem with a one-line fix, and Str4d helped.
- There were contributions such as removing a circular dependency and replacing network match statements in tests, which are preparation for later adding custom testnet parameters and regtest.
ECC update: Zashi 1.0 preparation and TEX address support
Electric Coin Company · Str4d, Daira
- For the past 2 weeks they focused on preparing the Rust crates for Zashi 1.0.
- They wrapped up the Orchard migration work late last week with new releases of zcash_primitives, zcash_proofs, zcash_client_backend and others, and this week are doing the work needed for Orchard support.
- They added TEX address parsing support to zcash_address crate 0.3.2. After updating, apps will tell users a TEX address is an unsupported address rather than an invalid address.
- TEX support in zcash_client_backend is being added together with the proposal API that creates multiple transactions.
- New transaction creation APIs such as proposed transfer and proposed shielding go into the new Swift and Android SDKs, and the existing APIs are deprecated.
- Because of the Zashi security audit schedule, this feature must be released next week. The points initially received from the Zashi iOS audit are in public GitHub issues and will be fixed in 1.0. There is no final report yet.
Trailing Finality research
Electric Coin Company · Daira, Pili
- In an R&D meeting with Zaki Manian, who knows Comet BFT well, they got detailed answers about Comet BFT and projects that use it such as Polygon and Penumbra.
- Daira said they must write up Crosslink 2 as a document before the cryptography conference hacks on the 19th.
ZSA update and 2024 roadmap proposal
QEDIT · Vivek, Jon, Daira, Str4d
- For the asset swap ZIP-228 there was only a typo fix. The transaction test tool for Zebra was submitted as a separate repository as ECC requested.
- Simultaneous support for v5 and v6 in the Orchard crate is mostly done, and v6 support in librustzcash remains. They also refactored the test vectors to separate Orchard and ZSA.
- They said the 2024 roadmap proposal will include adding stablecoin support to Zcash, in addition to exchange-compatible features and receive-rejection controls.
- The idea is to set the privacy approach per asset and give issuers verifiable encrypted reporting that meets accountability requirements.
- Daira pointed out that the issuer's keys and the compliance department's keys must be separated, and that an encryption key shared by the whole asset is a big target, so key rotation or off-chain storage of ciphertexts is needed.
- Str4d said users must be able to control which assets they accept to prevent the risk of a wallet being paralyzed. Jon announced the plan for formal verification of verifiers at ZKProof 6.
Open discussion: the light client working group and meeting times
Zcash Wallet Community · Pacu, Dodger, Daira
- Pacu announced that the light client working group, held the same day at 17:00 UTC, will discuss transparent-source-only addresses and applying ZIP-320 across the ecosystem, and friction in distributing the ECC SDK (React Native and others).
- Dodger explained that Ywallet is built by an individual, Hanh, who lives in Asia and is maintained with ZCG support. Daira confirmed that they stepped down from the ZIP editors as planned at the end of February.
- On the time error in the calendar ICS file, they said it is sent by Zoom, so everyone should create the event themselves based on UTC.
This summary is based on the original meeting notes; check them for exact details.