← All calls
ARBORIST#41

ZIP 317 unpaid actions fix

An amendment to ZIP 317 capping unpaid actions per block and the Ledger app's v4 support issue were discussed.

Agenda summary 5

  1. Zebra update - CI stabilization, ZIP 317 and FROST

    Zcash Foundation · Deirdre

    • The CI, which repeatedly created containers on Google Cloud and connected via SSH, was unstable because of VM readiness delays and SSH key sync problems; the team found the causes and it no longer fails unnecessarily.
    • The team merged a change to do Sprout anchor checks in parallel on a rayon thread pool instead of Tokio. This is because rayon is better suited to CPU-bound work, and the team keeps looking for parts of the note commitment tree update that can be parallelized.
    • There is a preliminary implementation of ZIP 317 that picks transactions from the mempool under the new fee rules and puts them into block templates. ZIP 317 was amended the day before, so this implementation will be updated soon.
    • The FROST IETF specification is at CFRG last call, and comment collection ends this week. The Foundation plans to publish an implementation of the FROST cipher suites and a Zcash-compatible version supporting re-randomization on crates.io soon.
  2. Research and implementation update - ZSA issuance and transfer fees

    QEDIT · Jon

    • The ZSA milestones are going smoothly and issuance is done. For transfer, most of the protocol side is done and the burn work is ready for a PR, with the goal of the circuit by mid-January and a state connectable to an external testnet by the end of January.
    • Since it touches the same area as the circuits ECC is optimizing, a meeting to coordinate circuit size is needed. It was decided to merge the fee proposal directly into ZIP 317.
    • ZSA fees should be proportional to the load placed on the chain and are handled similarly to ZEC transactions. The idea of validators taking a share of the token value was discarded early because of privacy leakage and changed incentives.
    • The ZIP includes a proposal to put a 1 ZEC or 0.5 ZEC fee on issuance to prevent infinite asset spam. Daniel left QEDIT and Jon handles communication. Thanks were also extended for the ZKProof 5 event.
  3. Zondax Ledger app and v4 transaction support

    Zondax · Ainhoa, Juan Leni, Dodger, Daira, Kris

    • Zondax's Ledger app for Zcash has two obstacles in Ledger's review. A Zecwallet compatibility PR is still open, and the app supports only v4 and not v5.
    • Daira said transactions without Orchard can be sent as v4 without problems, and the only difference in v5 is the non-malleability of the txid. It was explained that Ledger's existing Bitcoin-fork app supports v5 for transparent transactions, so this could be seen as a regression.
    • Kris pointed out that wallets must be able to parse v5 transactions, and Daira said to set broader v5 support as later scope. Details will be settled in a separate meeting.
    • The Nano X has Bluetooth but cannot sideload, so a Ledger-signed release is needed, while the Nano S plus can sideload. Dodger suggested narrowing the scope first to Sapling only and desktop USB.
    • The Zecwallet-side PR is old and has conflicts, so Dodger asked Aditya. The Foundation does not control Zecwallet, so it cannot answer about future plans. It was decided to hold a Ledger, ECC and Zondax meeting.
    • Daira said the cryptographic code and the design of communication between components need an audit, and Dodger said to handle it as a separate agenda item. Zondax has received only an informal review. ECC's capacity for review is limited.
  4. Core update - zcashd 5.3.1 and the ZIP 317 amendment

    Electric Coin Company · Sean Bowe, Daira

    • 5.3.1 is due this week or next. It includes memory usage improvements, a fix for an assertion error on restart after exit when an Orchard key had been generated, and some RPC changes.
    • ZIP 317 lets low-fee transactions be included probabilistically, but the existing approach had a vulnerability that let an attacker slip in large transactions with almost zero fee. This is because a high weighted ratio makes them try to fill much of the block.
    • The new PR Daira opened introduces the concept of unpaid actions, which are not covered by fees. By limiting unpaid logical actions per block to a fixed cap, it guarantees an upper bound on the effort of processing.
    • Work on DAGSync and Halo 2 recursion also continues.
  5. Open discussion - the Orchard transaction builder

    Dodger, Adi, Kris

    • Dodger asked about the status of the Orchard transaction builder that came up on the wallet developers call. Adi said it was merged with the Light Client Working Group after the early November call, and its first meeting is held that day.
    • The current focus is improving a Rust library called the Zcash light client kit. Whether to provide the transaction builder as a script or a binary is under discussion.
    • Zingo Labs' fork of the Zecwallet CLI has an Orchard transaction example. Zingo wanted Orchard v5 support in the core Rust library, and Kris agreed to attend to discuss the transaction builder PR.

This summary is based on the original meeting notes; check them for exact details.