zcash script API simplified
Conrado's simplified zcash script API entered the review stage.
Agenda summary 7
Zebra update: Zebra scan, ECC dependencies, the simple zcash_script API
Zcash Foundation · Alfredo, Conrado, Kris
- Progress was limited because of attending the ZKProof workshop. They fixed a note commitment tree serialization bug and finished the ECC dependency upgrade, and will merge Zebra PR 8568 soon.
- Marek opened a PR to zcash_client_backend (librustzcash PR 1400) that lets types be passed between threads and asked ECC for review. It is not urgent.
- After surveying the zcashd deprecation requirements list on the forum, most of it is already in Zebra or needs wallet support that does not exist yet.
- They narrowed the scope of Zebra scan to running it as a separate process rather than a new repository, so the keys stay outside Zebra.
- Conrado changed the zcash_script API so that instead of a C++ transaction pointer it takes the transparent transaction verification parameters and a callback to compute the sighash.
- zcash_script now has no Rust crate dependencies other than the C++ code, and Kris said it also becomes easier to compare-test side by side with a Rust replacement implementation.
ECC update: zcashd 5.9.1 and Zashi exchange rate conversion
Electric Coin Company · Kris, Daira, Pacu
- zcashd 5.9.1 contains the TEX address generation utility API requested by Binance and a minor exception fix in the P2P protocol. Daira corrected that this is not ZIP-320 support, only a utility API for TEX address validation.
- In the incrementalmerkletree and shardtree crates, they fixed a bug where, in a very narrow case near the end of a note commitment tree shard, the witness could not be computed and funds were temporarily unspendable.
- For exchange rate conversion, so that the wallet user's IP is not exposed to the rate provider, they built a prototype in which lightwalletd proxies the request.
- They are also considering having lightwalletd fetch signed exchange rate data and having the client verify the signature, but only two places provide signed data and it is uncertain whether they have ZEC.
- They are pursuing both the signature approach and the TLS proxy approach, and the client could use both together. The client should also run a plausibility check on the value along with an average or median. Zashi 1.1 features are also in smooth development.
zcashd deprecation: Rust zcash_script and the transition plan
Electric Coin Company · Kris, Daira
- Sean and Kris advanced the work of porting the transparent script interpreter to pure Rust by a few hours.
- It is needed to support the transparent functionality that replaces the zcashd wallet, and it aims to remove the burden of having to keep maintaining C++ code after the zcashd deprecation.
- The plan is to complete the pure Rust implementation in NU6, have full nodes keep consensus with the existing C++ interpreter while running the Rust implementation in parallel to check the results match, and switch the whole network in NU7.
- Daira said this transition does not have to be tied to NU7 and that if it is late it does not block NU7. Most transparent scripts are P2SH used like P2PKH, and multisig and some HTLCs make up the rest.
- Str4d plans to restore the script distribution analysis tool and run the new interpreter over the entire chain history.
ZSA update
QEDIT · Vivek, Daira
- They added a halo2 gadget trait that generalizes the existing lookup range check for use in both the Orchard ZSA circuit and the existing Orchard circuit, and tested that it has no effect on the existing Orchard circuit's layout.
- They plan to submit a PR to the halo2 repository soon. The Orchard crate has stabilized on top of 0.8, and some work remains in librustzcash.
- On the zcash_note_encryption PR, ECC said it has not been able to review yet but that it is high priority. For the test vectors, they will first submit a PR that separates out the Orchard ZSA work, and submit the changes to the transaction structure and the issuance bundle separately afterward.
- They are also answering and fixing the ZIP issues.
FROST demo update
Zcash Foundation · Conrado, Pacu
- The stage 2 PR of the demo shown at Zcon was merged so the same demo can be tried directly, and documentation was written to match.
- Natalie is working on the refresh share feature, submitted a trusted dealer key generation PR and is working on distributed key generation (DKG) support. After that they continue work on the FROST server the demo uses.
- Pacu, with the FROST team's support, built a proof of concept (POC) called frost-uniffi-sdk, and said this feedback helps improve the API.
ZKProof 6 summary: Plonkish standardization
Electric Coin Company · Daira
- The Plonkish standardization work led by Daira, Str4d and Mary Maller is going well. They found two bugs in the specification during a session, and they are easy to fix. The current stage is defining the encoding of Plonkish circuits.
- Plonkish is an arithmetization used by Halo2 and others and is more complex than R1CS. Standardization would improve interoperability between different proof systems and circuit languages and make it easier to write circuits in high-level languages.
Announcement: the Z|ECC event
Electric Coin Company · Daira, Pili
- The next gathering is Z|ECC in San Diego in July, announced on ECC's Twitter and the forum.
- The next Arborist Call is June 13 at 21:00 UTC.
This summary is based on the original meeting notes; check them for exact details.