← All calls
ARBORIST#46

Feature-specific testnets and Zebra rc5

Zebra became ready for mining pool testing, and how to stand up feature-specific testnets was discussed at length.

Agenda summary 11

  1. Zebra rc.5 - mining RPCs complete

    Zcash Foundation · Marek

    • Zebra rc.5 is being released. The mining-related RPC implementation is complete and ready for testing with mining pools, so the team asked pool operators to test and give feedback.
    • The team fixed the lightwalletd regression to support the latest lightwalletd and made rollbacks of unconfirmed chains happen immediately. The note commitment tree is now stored in the DB so it is not recomputed on rollback.
    • Improvements such as removing duplicated redpallas code were included. The team implemented the consensus rules of finalized network upgrades, and on every start Zebra checks that it is following the consensus chain.
  2. FROST end-to-end proof-of-concept plan

    Zcash Foundation · Deirdre, Daira

    • The team is planning an end-to-end proof of concept for FROST signing in a distributed environment. Small binaries show key setup and signing of arbitrary messages in separate processes, serving as a demo for applications to follow.
    • It starts at the level of copying messages between terminals and grows into a networking library that handles authenticated channels and an implementation of the broadcast channel protocol.
    • Noise (probably the IK pattern) will be used for authenticated channels, with the echo broadcast specification applied on top. The goal is not scalability but a small, clear, correct implementation.
  3. Zcashd 5.4.1 and the feature deprecation framework

    Electric Coin Company · Str4d, Kris

    • 5.4.1 fixed the wallet update delay, and also fixed the problem where the options of the feature deprecation framework from 5.0.0 did not work in the config file and worked only on the command line.
    • Deprecation has two phases. Phase 1 announces it in the release notes and provides a flag to disable the feature in advance; after at least 18 weeks, phase 2 disables it by default, though it can be re-enabled with a flag. The purpose is to learn how it is being used and prepare migration paths.
    • ZIP 216 is being applied retroactively to zcashd. The team confirmed that everything visible to consensus before NU5 satisfies the rule, so it is treated as having been active from the start, and the code gets simpler.
    • Type safety improvements to the Rust crates will also come with the next crate release.
  4. The two-step payment API and ZIP 317 block construction

    Electric Coin Company · Str4d, Kris

    • A two-step API was added to the transaction builder for light clients. It first receives a proposal as a ZIP 321 URI, lets the user check the privacy properties and required fee in advance, and then finalizes it.
    • It will soon be applied to the mobile SDK and zcashd as well, replacing z_sendmany.
    • The ZIP 317 block construction implementation is essentially complete, and the RPC tests that assumed a fixed fee are being fixed, so it will ship well tested.
    • zcashd RPC uses positional-argument JSON-RPC, so the fee argument cannot be set separately. The plan is to introduce a value meaning the default fee (probably -1) so that the ZIP 317 rules apply.
    • A PR for the incremental Merkle tree crate, in the DAGSync line of work, is being reviewed.
    • For the problem of creating Orchard transactions on 32-bit Android, bugs were found in incrementalmerkletree and pasta_curves and are expected to be resolved with patch releases.
  5. Mempool fee filtering and mining pool selection

    Teor, Daira, Str4d, Nate

    • The random eviction of ZIP 401 will be updated to use the new default fee. zcashd fixed block selection by, for example, queueing children whose parent transactions have not been selected first.
    • Daira said they are considering a policy to block relay of transactions with more than 50 unpaid actions, since they cannot get into a block anyway.
    • Teor said the same issue is open for Zebra and suggested discussing consistency of the two nodes' mempool filters at the ZIP sync.
    • Zebra has already implemented ZIP 317 for block construction, with only the relay rules remaining. Since Zebra implements only ZIP 317, the same policy applies once it switches. Mining support is experimental, and there is one known rare concurrency-related bug.
    • zcashd has an RPC for manipulating transaction priority, but after ZIP 317 is introduced the priority logic goes away. Mining pools' own payment prioritization is possible with existing APIs, and the team asked to be told which RPCs are in use.
  6. Suspected Zebra miscompilation and Orchard dummy notes

    Zcash Foundation · Teor, Daira, Str4d

    • In Zebra, the team found that halo proof test vectors fail on nightly builds while passing on stable. A Rust miscompilation is suspected, and it was confirmed on a 64-bit environment.
    • Daira and Str4d said it is most likely a nightly issue separate from the 32-bit problem.
    • In the ZSA ZIP editing discussion, the question of whether to keep Orchard's dummy note scheme or unify it with split notes became an issue. There was a reason dummy notes were kept earlier but nobody remembers it, so the team will check previous meetings again.
    • Daira thought that for a new asset the asset base point becomes valid through an on-chain issuance transaction, but ZEC has no such transaction, so special handling is needed. Str4d corrected this: no special handling is needed, because split notes work by binding to an existing note.
  7. Asynchronous research discussion forum proposal

    Electric Coin Company · Nate, Jack

    • Nate said Discord is chat-centered, so a space for long-form asynchronous research discussion is needed, citing forums like ethresear.ch as an example.
    • Jack said a permissioned section accessible only to certain groups can be created on the Zcash community forum, and can be set to public or fully private. A section was recently created for the mobile wallet group, and one can be set up in a short time.
  8. Feature-specific testnet discussion - need and the zcashd feature framework

    Nate, Str4d, Daira, Teor, Deirdre, Adi

    • Teor asked when ZSA would be integrated into NU6, and Daira said they do not know yet but hope it is included in NU6. Str4d said whether the circuits QEDIT built will match the result of the ZIP editing is a separate matter.
    • Nate said they want to make it easy to stand up independent testnets per feature.
    • Str4d said zcashd's feature framework can turn on features at a fake network upgrade point with a runtime flag, and an independent network can be created with a separate parameter set and testnet in a box.
    • Nate wanted the Ethereum-style approach where you only write the testnet name in the config, and Str4d said to check whether Ethereum's multiple testnets are for parallel global state rather than consensus rules.
  9. Feature-specific testnet discussion - the Zebra approach and wrap-up

    Nate, Str4d, Daira, Teor, Deirdre, Adi

    • Teor explained Zebra's Rust feature approach and the need for a new DNS seeder.
    • Deirdre thought that if there are no consensus rule conflicts, feature branch builds and the existing testnet are enough. Jack and Daira mentioned staging with one testnet for the next upgrade, since demand for testing current and next rules diverges.
    • When Adi asked about exposing only RPC on a closed testnet, Str4d answered that regtest mode can do it. It depends on whether the testnet's purpose is consensus interoperability or mining and lightwalletd testing.
    • It was decided to collaborate on a testnet setup guide and to hear opinions from Ethereum and QEDIT.
  10. Zcash Minor Grants program announcement

    Zcash Foundation · Jack Gavigan

    • The Zcash Foundation started the Minor Grants program this week. The main grant program was renamed Zcash Community Grants, and Minor Grants complement it.
    • It is up to $25,000 per grant with an initial budget of $75,000, funded from the Foundation's share of the Dev Fund. The Foundation screens for suitability and then asks ZCAP for its opinion to make selections.
    • The application deadline is Monday, March 20, UTC morning. There is no restriction on field, but the Foundation will judge fit with its mission and 501(c)(3) constraints, and feasibility.
  11. Network monitoring and mining reward inquiry

    Jack, Adi, Daira, Str4d, Teor

    • On Teor's proposal for stronger network monitoring, Jack said to ask Ziggurat to present the current state and make it a future meeting agenda item, and Adi welcomed it too.
    • Adi relayed inquiries from two individual miners saying mining rewards suddenly dropped starting this January. They said mining toward shielded pools had increased while difficulty stayed the same.
    • Daira mentioned that existing miners may have moved to shielded coinbase, which has no 100-block wait. Str4d and Daira thought it is not a protocol problem but a pool distribution matter, and that with the same hash rate the total rewards are also the same.
    • Teor listed possibilities such as mining on a fork that became orphaned, changes to a pool's reward scheme, and stale templates. Marek also mentioned the case of other miners leaving the pool. Jack said there is too little information and recommended posting details on the forum.

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