← All calls
ARBORIST#79

NU6 ZIP deadline and the Dev Fund

A deadline for NU6 ZIP submissions was proposed, and the design space for the Dev Fund lockbox was discussed.

Agenda summary 6

  1. ECC update: Arti (Tor) integration, ZIP-320, ZIP-317 fees

    Electric Coin Company · Kris, Str4d, Daira, Dodger

    • Str4d finished a prototype in the wallet backend that fetches exchange rates over Tor. Actions that leak information, such as submitting transactions, can also be handled by connecting to lightwalletd over Tor.
    • Arti is a Rust Tor implementation that started with support from ZOMG and others in the past, and it was easy to bundle as a library. Onion Services are still experimental, so a node-side Tor service is a long way off.
    • Daira said ZIP-320 (TEX address) support is almost done. The temporary output between two transactions has an unknown height, which required a zcash_client_sqlite DB schema change.
    • The design is complicated, so an SDK release this week is not possible, and the aim is to finish early next week.
    • A year after ZIP-317 took effect, all major wallets use ZIP-317 fees, so in the next zcashd release the default for the unpaid action limit will be lowered from 50 to 0.
    • This applies to both the mempool and block acceptance settings, miners can change it locally, and the method will be documented in the release notes. Sandblasting started again a few days ago.
  2. Zebra update: Zebra scan split and zcash_script

    Zcash Foundation · Arya

    • They updated the ECC dependencies and improved the documentation build issue on Rust beta and CI. A PR is open that removes support for starting Zebra scan from Zebra and makes it a standalone binary.
    • With a PR that uses the latest zcash_script, Zebra can use different ECC dependency versions from zcashd, and the Zebra scanner can run as a separate process using RocksDB blocks.
    • A tracking issue was created for adding an indexer service. RPC clients lack a way to be notified of the best chain tip and mempool changes, as well as a dedicated block nullifier RPC for lightwalletd, which relates to the zcashd deprecation.
  3. ECC and ZF zcashd deprecation: wallet backend work

    Electric Coin Company · Str4d, Daira

    • Zashi and the mobile SDK only store shielded funds, but the zcashd wallet can make arbitrary spends from transparent addresses, and the replacement wallet must too.
    • Kris is working on making the wallet backend's handling of transparent outputs symmetric, and the mobile SDK is not affected.
    • They plan to make zcash_client_sqlite's wallet tests generic over the wallet backend and later apply them to the wallet service as well. The long-term goal is also to port or adapt zcashd's RPC test suite and merge it in.
    • Daira said there is no need to reproduce even the bugs identically. They also made progress on a Zashi bug fix related to transparent balance handling.
  4. FROST: share refresh and the Dev Fund multisig

    Zcash Foundation · Conrado, Alfredo, Daira, Str4d, Dodger, Kris

    • The refresh share feature works but needs API improvements. There was also a problem that the FROST specification does not allow serializing the identity element, which they worked around.
    • They plan to release 2.0.0 rc-0 next week, collecting API changes in the core and cipher suite crates, and asked for API-breaking improvement proposals now.
    • Alfredo asked whether using a FROST multisig for the Dev Fund proposals is possible by November. Conrado answered that the tooling is only a command line so it is inconvenient, but it works.
    • FROST scales linearly with the number of participants, and even with 1000 it takes less than 1 second. Kris pointed out that a UTXO-based Dev Fund that runs a multisig signature for over 1000 block outputs a day is not realistic.
    • Daira said FROST is ready enough to recommend for a multisig-based Dev Fund, and that they will add a caveat to the forum post's statement that it is technically possible.
    • Dodger stressed that with repair shares, even if one person loses a key they can recover while keeping the same address, and that nested FROST, which also splits members inside an organization, is worth considering.
  5. Proposed deadline for the NU6 specification

    Electric Coin Company / ZIP editors · Kris, Str4d, Daira

    • Kris said a deadline is needed to finalize the specification going into NU6 in an implementable proposed state.
    • Kris proposed effectively completing the NU6 ZIPs by the next ZIP editors' meeting (July 16, 17:00 UTC, the week after the Z|ECC Summit).
    • Str4d explained that, counting implementation, deployment, halting of old-version nodes and audit, the time is tight if activation is based on late November.
    • ZIPs that can activate after November need not be on the same schedule, but this does not apply at the halving point. ZF will submit a survey-based Dev Fund proposal, and the other Dev Fund proposals have not yet been made concrete as ZIPs.
    • They decided the ZIP editors will set the deadline at the next meeting.
  6. Design space of the Dev Fund proposals

    Electric Coin Company · Daira, Str4d, Kris, Dodger, Alfredo

    • Daira and Str4d organized the Dev Fund design space. The key axes are a per-output UTXO model versus an in-protocol single or per-recipient reserve model.
    • Skylar's lockbox proposal is one point: put funds into a single reserve and defer the disbursement method to a later upgrade. The UTXO approach has the cost of handling over 1000 outputs and the risk of key theft.
    • For implementation, keeping the existing funding streams is easiest, followed in order of ease by a single reserve with deferred disbursement, then per-recipient reserves with withdrawal to a designated address.
    • Dodger stressed that intent should be stated first, and that political and technical considerations should be separated, so that technical possibility does not dictate intent.
    • Alfredo worried that if nothing is done at the halving, Zebra would keep sending the half reward to the same address, but Daira checked the code and confirmed it is implemented correctly.
    • Str4d asked ZIP proposers to say what support they need and suggested a Discord office hour. Kris and Daira said they can give early technical feedback.

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