← All calls
ARBORIST#107

zcashd 6.3.0 prepares for NU6.1

zcashd 6.3.0 was released, with NU6.1 testnet activation and the NSM merge under way.

Agenda summary 10

  1. Zebra update: release status and NU6.1

    Zcash Foundation · Alfredo

    • After the Zebra 2.4.0 release a DB bug was found and 2.4.1 was issued but did not work well and was withdrawn; the latest release is now 2.4.2, and 2.5.0 is released that day.
    • A release containing everything needed for NU6.1 and the testnet activation height was implemented, and the team took part in a private custom testnet session with ECC.
    • Once the release PR is merged, the tag can be applied.
    • Dorian of Zingo Labs fixed a validate address bug, and there is also a PR to allow configurable funding streams.
  2. Zebra update: CI overhaul and work in progress

    Zcash Foundation · Alfredo

    • CI, which had many problems, was stabilized through Gustavo's efforts, and a major CI refactoring is planned to reduce a structure that does too much, so ideas and complaints are welcome.
    • Work on the Python framework was put on hold because of the release but resumes next week, and Zebra and Zallet integration testing also continues.
    • Mario is working on ZIP 213.
  3. ECC update: zcashd 6.3.0 and the NU6.1 testnet

    ECC · Kris

    • Last week the team released zcashd 6.3.0 with the NU6.1 testnet update feature.
    • They coordinated testnet activation with ZF and Shielded Labs, and the three key-holding organizations generated the P2SH multisig for testnet.
    • For this, librustzcash crates from zcash_protocol through zcash_keys were released; the zcash client backend and SQLite releases were held back because the Zallet alpha needs more.
  4. ECC update: P2SH PCZT, NSM merge, next priorities

    ECC · Kris

    • Str4d made a lot of progress on PCZT support for P2SH multisig signing, and the team is also looking at integrating it into Keystone firmware.
    • Shielded Labs' main NSM PR was merged into librustzcash behind a feature flag and a config flag, and CI also has a build configuration for NU7 ZIP 233.
    • For now the focus is the Zallet release and Keystone's P2SH multisig implementation, and parts of the Bitcoin standards are being adopted for multisig setup and key derivation.
    • The team also wants to reflect ZF's coinbase construction PR and Pacu's librustzcash PR that sends the entire wallet contents, the latter to be used in Zashi for NEAR Intents swaps.
  5. ECC update: PCZT ZIP, quantum-resistance ZIP, new team member

    ECC · Str4d, Kris, Schell

    • Str4d is working on a ZIP draft of PCZT v1, which was specified last year as the PCZT Rust crate.
    • This is because v1 must be written up before the ecosystem can define v2, which supports the v6 transaction format and FROST.
    • Daira Emma is writing the quantum-resistant key derivation change as a ZIP, proposing that every Orchard shielded output in a v6 transaction be tied to a key that applies this change.
    • If quantum computers appear within a few years, signatures could be forged, so notes not tied to keys with a post-quantum element would become untrustworthy.
    • A new core team member, Schell, joined ECC, growing the staff by a third.
  6. Zingo Labs: Zaino update

    Zingo Labs, ECC · Za, Kris

    • Za said it was not a formal update: the design team is finishing a re-specification with basic primitives compatible with Crosslink, and finalized and non-finalized state become first-class state in the new Zaino.
    • The team expects the release of zainod, the lightwalletd replacement, before the next Arborist call, with block explorer support about a month after that.
    • Kris explained that Zaino provides a new chain index API abstracting finalized state (older than 100 blocks) and non-finalized state (the latest 100 blocks), which simplifies Zallet code.
    • ECC expects to be able to start using this API around the middle of next week.
  7. zcashd retirement (Z3): alpha preparation and coordination

    Zcash Foundation, ECC, Zingo Labs · Pacu

    • At that day's meeting the team drew up a rough roadmap for coordination and began preparing the Z3 alpha.
    • Zallet is the most visible front-facing element of the Z3 stack, and the team must coordinate Dockerizing the stack with ZF and decide how to distribute the Zallet alpha across platforms.
    • They start with a source build and add distribution methods, and run the initial alpha with a small group of selected partners, widening it at the judgment of ECC, ZF and Zingo engineers.
    • Alpha and beta proceed slowly so feedback does not arrive all at once and can be taken in depth.
  8. NSM update

    Shielded Labs · Jason McGee

    • The librustzcash PR was merged, and Daira Emma's comments on the Zcash test vector PR will be addressed when Mariusz, who is on vacation, returns on Monday.
    • After the ZIP 233 integration is finished, the ZIP 234 and 235 PRs will be submitted.
  9. Crosslink Milestone 3 demo and schedule

    Shielded Labs · Nate, Jason McGee, Daira Emma

    • The demo by Sam and Andrew showed a mode in which automated tests do not stop at assertion failures but show every problem, and a visualization tool that replays tests to show the link between the two chains.
    • This implementation has a two-way link but does not yet have a test for rollback past the finality point.
    • The goal is to finish Crosslink Milestone 3, which carries PoA and rough edges, by the end of this month, with a workshop on the 27th.
    • At the ZIP meeting the team received a lot of feedback on miner compatibility issues with the PoW header change, which helped.
  10. Crosslink prototype approach and simplifying PoS rewards

    Shielded Labs, ECC · Nate, Daira Emma

    • In the prototype phase, whenever the team meets a design problem that may not be compatible with mainnet, it records it as an architecture decision and chooses the fastest way to continue.
    • The goal is a fully functional prototype on its own testnet by the end of this year, with finalizers, delegation and an active roster, with no guarantee that it is actually runnable on mainnet.
    • Milestone 4 implements the entire PoS accounting rules, including finalizer registration, delegation, candidate selection, rewards and fees, and penalties.
    • The team is considering radically simplifying the reward scheme so that, once on the roster, even offline finalizers and delegators are paid issuance at the same rate, and BFT halts if not enough finalizers respond.
    • Whether performance rewards or double-signing slashing are needed will be evaluated carefully.
    • When Daira Emma asked where these simplifications are recorded, Nate said they are in a Google spreadsheet that is still incomplete, and that they would make it publicly viewable.

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