← All calls
ARBORIST#82

NU6 lockbox implementation and zcashd deprecation

NU6 lockbox implementation is progressing in both nodes, and collaboration on the zcashd deprecation was discussed.

Agenda summary 14

  1. ECC and ZF NU6 update

    ECC, Zcash Foundation · Kris, Daira Emma, Arya, Str4d, Pili, Alfredo

    • Since both final Dev Fund candidates lead to a lockbox via funding streams, the two teams implemented the lockbox feature first.
    • Lockbox PRs are open in both Zebra and zcashd, and since the ZIP is a draft and only some parameters may change, they are keeping the two implementations consistent.
    • The runoff vote is targeted for around next Monday, and they plan to finish assigning the ZIP numbers and finalizing the parameters at the Tuesday ZIP editors' meeting.
    • The August 8 testnet activation is tight given the release schedule, and they decided to set the activation height just before the release.
    • Zebra aims to release on the Friday or Monday just before testnet activation.
    • They confirmed that the lockbox balance ZIP is already included in the draft NU6 deployment ZIP.
  2. Discussion of lockbox governance and the protocol decision structure

    Jon, Str4d, Daira Emma, Dodger, Kris

    • Jon worried that if the lockbox's disbursement method is later decided by a ZIP, too much burden will fall on the ZIP editing process.
    • Str4d answered that what is actually implemented and deployed in nodes is decisive.
    • Daira Emma explained that full node implementations gain legitimacy from ZIPs and coinholder votes, and that actual consensus is decided by the majority-mining chain.
    • Dodger summarized that the ZIP editors' role is checking the completeness of the specification and the security review, and that deciding protocol changes currently requires agreement between ECC and ZF.
    • Kris said that zcashd is planned to end without upgrading for NU7, so there is no need to consider the possibility of the two specifications conflicting after NU7.
    • They decided not to conclude this time on how ECC's withdrawal from the trademark agreement affects future upgrade decisions, and to sort it out later.
  3. Zebra update

    Zcash Foundation · Alfredo

    • In the roughly 3 weeks since the last release, 1.8.0, they improved the CI test framework settings so that tests pass more easily.
    • They moved the scanner code into a new binary and merged it, updated the docs, and added a tonic server to zebra-rpc as part of the indexer work.
    • They added an NU6 variant without an activation height, and opened a lockbox PR and are aligning its output with the zcashd team.
    • Yesterday they merged a configurable testnet funding stream, making it possible to test NU6 features in Zebra Regtest mode.
    • They also fixed the lightwalletd getblockchaininfo RPC issue.
    • The Hyper dependency went up a major version and they dealt with it, and they are looking at reducing or eliminating Hyper use in the future.
  4. ECC update: ZIP-320 / zcashd 5.10

    ECC · Str4d, Daira Emma

    • They merged the ZIP-320 change, and while fixing bugs in other parts of the stack that testing revealed, aim to include it in next week's SDK release.
    • In zcashd, the PR lowering the free action limit to 0 failed because of an old fee calculation test, and they plan to fix that and then release 5.10.0.
    • The next zcashd release is likely to be 5.10.0 within a few weeks, and they are arranging for it to go out together with the NU6 code.
  5. ECC update: Tor exchange rate lookup and zcashd deprecation staffing

    ECC · Str4d, Kris, Daira Emma

    • Exchange rate lookup over Tor was merged into the Rust crates and uses the Arti backend, taking 5 to 10 seconds on desktop and up to 20 seconds on mobile.
    • In the mobile SDK it is provided through a ZEC/USD exchange rate subscription value and a refresh API.
    • Sending transactions over Tor and the lightwalletd gRPC connection are also goals afterward, but because tonic does not expose the needed APIs they proceed as side work.
    • Greg Pfeil is joining the work on the zcashd deprecation and finishing the zcash_script library, and the transparent address bug they are fixing is also directly tied to the deprecation.
  6. zcashd deprecation roadmap and how to contribute

    ECC, Zcash Foundation · Jason McGee, Str4d, Pili

    • Mentioning the deprecation roadmap and the API list Hanh compiled, Jason McGee asked whether there are owners and a status checklist so that ZCG can support it.
    • Str4d pointed to the deprecation DAG and librustzcash issue 1350 and asked anyone who uses it to tell them in the issue.
    • With people who want to take part, they decided to set up a regular check-in meeting.
    • The Zebra team is tracking a new built-in wallet architecture, a block explorer and hardware wallet support as milestones.
    • Pili asked people to tell them about use cases Zebra does not meet.
  7. Deprecation architecture and discussion of replacing lightwalletd

    ECC, Zcash Foundation, Zingo Labs · Str4d, AloeareV, Zancas, Arya, Dodger, Daira Emma

    • Str4d described a structure split into a consensus node, indexer, scanner and wallet service, and in an exchange configuration everything other than the wallet can be bundled into one process.
    • Zingo Labs' AloeareV is working on a Rust-based lightwalletd replacement and an NYM server.
    • Zancas said they would put Zebra regtest into Zingo's end-to-end tests to find missing RPCs.
    • Zebra regtest is usable apart from the invalidateblock and reconsiderblock RPCs.
    • Dodger summarized that replacing lightwalletd is not a required path for the deprecation and that the core is the built-in wallet replacement for exchanges.
    • Daira Emma added that to satisfy the exchange use case, a component that takes over the role lightwalletd handled may be needed.
  8. Zcash Shielded Assets (ZSA) update

    QEDIT · Vivek, Jon

    • For the Halo 2 generalization they put up a foundational PR containing only the interfaces, and plan to put up the actual changes as 3 PRs in consultation with ECC.
    • The librustzcash, Orchard and Python test vector work wrapped up and passed verification of the new transaction format.
    • Following confirmation that NU6 has no transaction format change, they are reverting the v7 transaction code back to v6.
    • Jon explained that the v6 PR of the Zcash transaction tool for Zebra is about to be merged and is the entry point for testing ZSA issuance and transfers with Docker.
    • During the test vector work they filled in ambiguous parts of the ZIP, and changed the format order to move the burn transaction before the binding signature.
    • They asked for feedback on the ZSA fee ZIP and the asset swap ZIP because activity is low, and swaps need a format refactoring that uses action groups.
  9. ZSA asset swap and asset acceptance grant proposal

    QEDIT · Jon, Vivek, Daira Emma, Pacu

    • QEDIT submitted to ZCG a proposal to focus staff on the trade acceptance and rejection ZIP and a concrete implementation of asset swaps, and said it would implement it by early December.
    • Asset acceptance works by the sender conveying intent off-chain and the recipient binding acceptance via the swap mechanism and proving it in zero knowledge.
    • As use cases, they gave declining a payment that someone else makes at a restaurant and an exchange that does not want deposits of a particular asset.
    • When Pacu asked whether it could be used to prevent Ethereum-style spam tokens, Jon answered that that is the motivation.
    • Daira Emma summarized that per-transfer acceptance and rejection is more flexible than a token allowlist, and that an allowlist can be implemented at the wallet level.
    • Daira Emma said QEDIT took the cancelled grant process gracefully.
  10. Zcash Sustainability Fund (ZSF) update

    Tomek, Jason McGee, Str4d

    • Tomek is running ZSF integration tests on Zebra regtest, and solved the lightwalletd integration problem with Arya's help.
    • Tomek plans to put up code for review as early as next week.
    • Str4d answered that since zcashd will not receive big consensus changes, if the zcashd deprecation is late then ZSA is also late, and ZSF depends on implementation complexity.
    • Str4d explained that NU numbers are only guidelines, and that the better tested and more clearly scoped a change is, the easier it is to put into a particular upgrade.
  11. FROST update

    Conrado, Dodger, Str4d, Daira Emma

    • They merged the key share refresh (refresh shares) feature for trusted dealer key generation, and are working on the refresh for distributed key generation.
    • The structural change that turns the aggregator back into a coordinator is under review.
    • The FROST demo's signing tool uses Ywallet code and mixes an old ECC crate with local changes, so they plan to identify the needed API changes and discuss them with ECC.
    • With no feedback on API changes since 2.0.0-rc0, they plan to release the final 2.0.0 soon.
    • Str4d announced that the FROST ZIP draft for Zcash has been merged and published on the ZIPs site, and that PR 883, which covers the key generation method, is open.
    • Dodger reminded everyone that this ZIP must be moved to final status.
  12. Request for Trailing Finality collaboration

    Pacu

    • Pacu asked whether any team is interested in the Trailing Finality work.
    • Pacu pointed out that some exchanges require 100 confirmations, so users must wait with their funds locked, which is a big problem.
    • Pacu said they plan to cover this issue on the privacy blog and would welcome any team already working on it or willing to join.
  13. Coordination process between ZCG and node implementations

    ZCG, Zcash Foundation · Jason McGee, Daira Emma, Jon, Pili

    • Prompted by the cancelled stablecoin grant, Jason McGee said ZCG will attend the Arborist call to share new proposals.
    • ZCG wants confirmation from the engineering community on technical feasibility and risk, not community consensus.
    • Daira Emma said node implementations are busy and may miss proposals, so low-bandwidth sharing of proposals is needed.
    • Daira Emma also offered the view that controversial and non-controversial features should be separated into different grants.
    • Jon said that the more concrete and well organized a proposal is, the easier it is to get feedback, and Pili said ZF will keep giving feedback.
  14. Discussion of a grant review channel and the ZSA testnet

    ZCG, QEDIT · Dodger, Jason McGee, Daira Emma, Arya, Jon

    • Dodger was wary of adding more to an Arborist call that already runs over time, and Jason McGee suggested a dedicated Discord channel.
    • They decided to start with the Arborist call and move if time runs short.
    • In response to Arya's question, Jon answered that they will soon release ZSA's own testnet and let anyone run it themselves.
    • This testnet is a remaining deliverable from the previous grant.

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