← All calls
ARBORIST#86

CLI wallet and Zaino indexer architecture agreed

Participants agreed on the Zaino indexer architecture for the CLI wallet that replaces zcashd.

Agenda summary 13

  1. Follow-up on the NU6 testnet activation

    ECC, Zcash Foundation · Daira Emma, Str4d, Alfredo, Pili, Dodger, Pacu

    • The NU6 testnet activation succeeded but many users are having trouble syncing; there is no evidence of a consensus bug, and sparse connectivity is presumed to be the cause.
    • Daira Emma's zcashd node has only 2 connections and stopped at the height just before NU6 activation, and the 100-block rollback limit is not the main cause.
    • Alfredo said the core problem is that no nodes are mining, and that ZF is building a permanent mining node.
    • Str4d said existing miners may not have upgraded to NU6 and may still be mining on the old chain.
    • The NU6 activation height is not yet set in the librustzcash SDK, and they plan to set it in the next Rust crate release.
    • Pili relayed that Least Authority's preliminary NU6 audit report is mostly about mismatches between documentation and code.
  2. Zebra update: NU6 audit report

    Zcash Foundation · Marek

    • They added two new RPCs, Stop and Generate, refactored one RPC, and also made dependency updates and documentation and CI improvements.
    • The draft NU6 audit report has two findings, on documentation and error handling, and all are currently classified as suggestion level.
  3. ECC update: NU6 bug, Zashi and the wallet SDK

    ECC · Daira Emma, Str4d

    • A single mainnet user reported a problem with chain value pool balance tracking since zcashd 5.10.0.
    • They examined the changes closely but could not find the cause, and judged it not to be a blocking issue.
    • The wallet SDK changed how it exposes scan progress, showing separately the sync needed before the wallet can be used and the scan of past history.
    • They also fixed a bug related to the old Android API (API 27).
    • They are implementing the change to the confirmation selection method in the ZIP 315 draft.
    • The aim is to let notes be spent sooner while maintaining safety.
  4. Zcash Shielded Assets (ZSA) update

    QEDIT · Vivek

    • They finished the v6 transaction support work in Orchard, librustzcash and the test vector scripts, and Zebra's ZSA additions are in progress on several fronts.
    • They are discussing starting an audit of the Orchard ZSA protocol with Least Authority.
    • They resolved most of the key issues in the ZIPs repository, and work on recommended wallet behavior remains.
    • Open PRs in Halo 2 and Zcash note encryption are awaiting feedback.
    • They re-examined the asset swap ZIP-228 and began implementation changes in the Orchard repository, and discussed the direction of the user control feature with Daira Emma.
  5. Zcash Sustainability Fund (ZSF) update

    Paul Dann, Alfredo

    • They found several problems in the ZSF ZIP and are reworking it, and said they would explain the details within a few days.
    • Since end-to-end tests cannot be run in Zebra as in zcashd, they built a local testnet of zcashd and Zebra and succeeded in sending zcashd RPC tests to Zebra for verification.
    • They asked for help with a tricky problem related to async lifetimes in Zebra's Rust code.
    • Alfredo noted that adding zcashd's Python RPC test framework to Zebra could help.
  6. FROST update

    Conrado

    • They are finishing the key share refresh feature for DKG and continuing work on adding cryptographic authentication to the FROST server.
    • The goal is to deliver a FROST server usable in production within the next few months.
  7. Public announcements: GitHub board and TUM Blockchain

    Pacu, Daira Emma

    • Pacu announced that they are building a GitHub project board showing progress on each development effort, such as zcashd deprecation, hardware wallet support and block explorer support.
    • Daira Emma attended the privacy panel at the TUM Blockchain conference and made clear a position of not compromising with surveillance or compliance protocols.
  8. zcashd deprecation and CLI wallet architecture: background and overview

    ECC, Zcash Foundation · Dodger, Daira Emma, Jon, Str4d, Pili

    • Dodger explained that at last year's Zcon, ECC and ZF agreed to cooperate on deprecating zcashd and decided not to replicate its features as is but to build new software such as a CLI wallet.
    • Because ECC decided to add no more features to zcashd, major protocol upgrades are blocked on the zcashd deprecation.
    • They discussed the architecture for 7 months without settling it, Zingo Labs proposed a grant to support the CLI wallet, and ZCG is asking whether ZF and ECC engineers agree.
    • ZF has no wallet development experience, so it will follow ECC on architecture but wants to avoid putting all wallet functionality into Zebra.
    • Daira Emma explained that the full node has high complexity and attack surface, so it is split so that it handles only minimal functions and an intermediate indexer provides information for wallets.
    • Str4d summarized that the full node handles consensus, the indexer handles a cache of public information, and the scanner that knows the viewing key is kept separate from the indexer to preserve the trust boundary.
  9. Zingo Labs' Zaino proposal and indexer design discussion

    Zingo Labs · Arlo, Marek, Conrado, Str4d, Daira Emma

    • The core of Zingo's design is Zaino, which provides an indexer RPC that remotely exposes the Zebra read state service and a lightwallet gRPC from the same data, and they also prepared for the NYM mixnet.
    • The main difference from Arya's earlier design is that a lightwallet server is included inside the indexer.
    • Conrado asked whether the indexer needs to be a separate process, and if so, whether the existing lightwalletd could simply be extended.
    • Str4d answered that the current lightwallet RPC alone is not enough to replace the zcashd wallet.
    • Daira Emma thought that building something new is better for long-term maintenance than extending.
    • Str4d said whether to bundle it as a crate or separate it as a process is a deployment matter, and that logical separation is what matters.
  10. Narrowing Zaino's scope and the exchange use case

    Arlo, Str4d, Daira Emma, Rene

    • Arlo said Zingo was asked to drop wallet development from the grant and take on only the Zaino remote indexing service, and Str4d summarized that the focus is now Zaino.
    • Daira Emma said some existing wallets cannot handle exchange-scale transparent addresses, so a way to support wallets for exchanges must not be blocked.
    • Rene of the Zenith wallet said performance is the issue and that they would ask the exchange side for detailed usage patterns.
    • Str4d said the performance bottleneck lies more in the number of notes and coins to track than in the number of addresses, and recalled having simulated a scale of 200,000 notes.
    • Str4d said that when adding indexes they should avoid the zcashd problem of having to resync the node from scratch.
  11. Debate over centralized exchange priority

    Za, Pacu, Dodger, Daira Emma, Str4d

    • Za worried that a design centered on centralized exchanges could be an opportunity cost for other use cases such as DEXs.
    • Dodger and Daira Emma countered that centralized exchanges are an obstacle to the zcashd deprecation so support for them cannot be given up.
    • Pacu proposed keeping the existing RPCs as far as possible and supplementing with data conversion, considering that exchanges make only minimal effort.
    • Str4d said the indexer RPC must not expose full node control APIs so that it can be run safely as a public service.
    • It was also mentioned that including the lightwallet gRPC in Zaino has the advantage of letting it be verified with existing mobile wallets.
  12. Zaino's DB access approach

    Zingo Labs, ECC · Arlo, Daira Emma, Str4d, Marek, Arya

    • On whether direct DB access is vulnerable to timing attacks, it was discussed that separating the core state and the indexer DB as a buffer would be enough.
    • It was confirmed that a RocksDB secondary DB already uses an API that catches up with the writing process.
    • Zaino's default is direct access to the read state service, and it can run on another machine in a JSON RPC fallback mode.
  13. Grant request size and architecture agreement

    Zingo Labs, Zcash Foundation, ECC · Za, Alfredo, Pili, Daira Emma, Conrado, Arya

    • Za stated the upfront size of the ZCG request, and the retroactive portion is about $153,600 for 8 months at $80 per hour.
    • They also requested $30,000 for six months of labor for 3 new developers and $12,000 for test equipment.
    • Alfredo said the milestone amounts are $38,400, $44,800 and $38,400.
    • Pili drew the line that grant amounts are not something to comment on in this meeting.
    • Daira Emma, Conrado, Arya and others said they are satisfied with this maintainable architecture, and Pili summarized that agreement was reached.

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