← All calls
ARBORIST#114

ZIP-233 merged, Zebra 3.0

The ZIP-233 implementation PR was merged into Zebra, and the 3.0 stable release will come within days.

Agenda summary 7

  1. Zebra update

    Zcash Foundation · Marek

    • The Zebra 3 release is in progress, and the team plans to release the stable 3.0.0, aligned with NU 6.1 activation, within a few days.
    • Shielded Labs merged the ZIP 233 implementation PR that had been open for a long time.
    • It merged many RPC updates and fixes to get closer to the zcashd deprecation milestone, and quickly fixed a Dockerfile build problem.
    • Many of the PRs are from external contributors.
  2. ECC core update

    Electric Coin Company · Kris

    • The team posted a PR to update Zallet to the new Zaino chain index.
    • It is an important shift away from the light wallet protocol toward full node chain index functionality.
    • It is greatly refactoring the wallet backend, moving functionality from the SQLite-only implementation to a general backend.
    • This makes other backends such as an in-memory wallet usable, and by scanning transparent inputs and outputs directly from compact blocks it avoids queries that leak information to the light wallet server.
    • A PR for this functionality in lightwalletd is up and under review.
    • Thanks to community contributions, deterministic builds of Zallet are now possible too.
  3. zcashd deprecation update and Zallet contributor board

    Electric Coin Company, Zcash Foundation, Zingo Labs · Pili (presenting for Pacu)

    • The speaker from Zingo Labs was absent.
    • The Zaino team and ECC are working on chain index integration, which will be used to fully support Zallet and lightwalletd.
    • Some exchanges have started testing Zallet and are sending feedback and questions to Pacu and Pili.
    • On the Zallet contributor board that Pacu made, anyone can pick an open issue and contribute.
    • Priorities were set from top to bottom based on last year's survey of ecosystem participants' usage, and the wallet implementation work in the Ready column is the most important.
    • All transparent and shielded wallet developers must update their application's consensus branch ID before November 23, the NU 6.1 activation date.
  4. ZSA update

    Qedit · Pablo, Vivek

    • ECC merged the Halo 2 gadget, Sinsemilla and Zcash note encryption changes, and the Orchard ZSA changes are under review.
    • What remains to be merged are the minimal changes in Sapling crypto, librustzcash, and Zebra, which has most of the consensus rules.
    • Since Zebra is a node and a tool is needed to create v6 transactions, the team built TX Tool.
    • It demonstrated by connecting to the public ZSA testnet with Docker, and this time, in addition to issue, transfer and burn, finalize was added, so it also tests that further issuance of a finalized asset is rejected.
    • It fixed the action group shuffle problem that Daira Emma found, changing the per-asset individual shuffle into a global shuffle.
    • It applied the SIGHASH version byte in librustzcash to Orchard, Sapling and transparent, and also integrated the NSM field of ZIP 230.
    • The ZIP 233 feature flag is not tested in CI, so adding it was recommended.
    • It is changing the ZIP 317 fee calculation for ZSA.
    • New asset issuance has an extra fee, and global state is needed to know whether it is a first issuance.
    • Kris said it could be reconsidered for simplicity, and Vivek explained that it is because of the cost of a new issuance adding a row to the issuance state table.
    • As a proof of concept for swap support, it is checking whether v6 accommodates future features.
    • Alfredo suggested splitting the zcash-test-vectors PR into two, and said that it may conflict with the NSM's v6 definition and would need a rebase if the NSM is merged first.
    • When Alfredo suggested an RPC to query whether an asset has been finalized and so on, Pablo answered that it would be useful.
    • Issuance and supply are public information, and transfers are private.
  5. Network Sustainability Mechanism (NSM) update

    Shielded Labs · Mariusz, Jason

    • The ZIP 233 PR was merged.
    • The ZIP 234 and ZIP 235 PRs are being rebased and updated and will be ready by the end of the month.
    • zcash-test-vectors PR 101 has also finished incorporating feedback and is in a mergeable state.
    • Mariusz's team leaves the NSM project at the end of November, and after that the rebasing, addressing comments, and the Zebra merge of ZIP 234 and 235 will be handled by Shielded Labs.
    • The main contact is Jude Caruso, and Mark can also be contacted.
    • New engineer Jude is handling the NSM, partner support and Crosslink contributions as DevRel.
    • Philip took part in developing Tenderlink, Shielded Labs' own Tendermint implementation, and will show a wallet interface for staking at the early December workshop.
  6. Crosslink update (Trailing Finality Layer)

    Shielded Labs, Electric Coin Company · Nate

    • The goal is to finish a fully functional prototype by Q1 next year.
    • It discussed an iOS demo with the Zingo team and plans to have two example wallets at the time of the prototype.
    • The goal of milestone 4B is to link the weight of the PoS roster to test ZEC rather than arbitrary numbers, and a workshop is held on December 3.
    • It has already created the staking action field in the new transaction version, but the weights are still arbitrary values, and the ZIP 317 fee check was temporarily turned off for the demo.
    • The remaining work is to include the staking amount in the transaction balance and to build a wallet that spends Orchard notes and creates staking and unstaking actions.
    • To get early feedback from the ZIP editors, it will soon open an incomplete draft ZIP PR in the zips repository.
  7. Open discussion

    Nate, Pablo

    • Nate said some people want to bridge Bitcoin to Zcash, so ZSA is needed, and asked to be connected with Qedit.
    • Pablo answered that if contacted on Discord, they would discuss it.

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