← All calls
ARBORIST#38

Zebra 1.0.0-rc.0 tagged

Zebra tagged its first release candidate, and zcashd 5.3.0 shipped with memory optimizations.

Agenda summary 4

  1. Tagging the Zebra 1.0.0 release candidate

    Zcash Foundation · Teor

    • Zebra tagged its first release candidate. It means the team is satisfied with the consensus rules, chain sync and lightwalletd RPCs, and the goal is to get an audit within the next few months.
    • Significantly improved lightwalletd RPC performance made lightwalletd sync about twice as fast, and all RPCs now run in parallel with applying blocks to state.
    • As a breaking change, building with Rust 1.64 or later can cause the parameter download to time out because of a performance regression. Use Rust 1.63 or earlier, or the download script from the zcashd repository.
    • The image can be pulled from the zebra project on Docker Hub for testing. For security, RPC is off by default and turned on in the configuration. Contributions from former team members who left the Foundation were also mentioned.
  2. Zcashd 5.3.0 release and the mobile SDK

    Electric Coin Company · Steven

    • 5.3.0 was released that day. To avoid running out of memory during scanning and full node sync, it detects the batch scanner's memory usage and keeps it within a cap.
    • Prometheus metrics were added to show batch scanner progress and node sync height. finalorchardroot, finalRoot in getblock results, and z_gettreestate were changed to use consistent byte order.
    • One or two memory and performance optimizations will go into 5.3.1 or 5.4.0. Halo 2 recursion continues along three tracks: the front-end API, back-end split accumulation, and the full-width scalar multiplication circuit.
    • Mobile SDK fast sync is being worked on by Kris, Str4d, Pacu, Carter and the wallet teams. The iOS alpha comes next week and Android about a week after that, and the first release will also include unified address support.
  3. ZIP 317 parameters - logical actions and transparent transaction size

    Electric Coin Company · Steven, Kris, Adi

    • The purpose of ZIP 317 is fees proportional to chain usage. Logical actions put Orchard actions, Sprout joinsplits, and Sapling and transparent inputs and outputs on one unit, removing any advantage or disadvantage between pools.
    • Right after the last call, the team found an exception that a transparent transaction can be large even with few inputs and outputs. It was changed so the transparent input and output bytes divided by a standard size are reflected in logical actions.
    • Kris said arbitrary data can be put in transparent scripts, so size is used as a proxy for actions. A standard p2pkh 2-in 2-out is the same as Sapling, and multisig is about one action per signature.
    • When Adi asked why the larger of inputs and outputs is chosen for Sapling, Kris answered that it matches the fact that Orchard has equal numbers of inputs and outputs, to eliminate the economic advantage of using Sapling.
    • The enforcement method is undecided. One possible order is for wallet developers to implement first and monitor adoption, then miner selection and relay filtering, and finally enforcement by network upgrade.
  4. Open discussion - introducing the pools and ZIP 317's impact

    Electric Coin Company · Steven, Dodger, Kris, Adi

    • Steven introduced Zcash's four pools: Transparent, Sprout (the first shielded technology), Sapling (introduced around October 2018), and Orchard (based on Halo 2, activated in May of this year).
    • Sending a 2-logical-action transaction in every block costs $6.91 per day, up from the previous $0.69, based on 1,100 transactions. Sandblasting is about $2,300 per day, about $69,000 per month.
    • Dodger asked about the impact on legitimate high-volume transactions such as exchange deposit address sweeps and mining pool payouts. Steven said they would meet and explain to exchanges and mining pools as well as wallet developers.
    • Kris said initial enforcement works through miners' transaction selection, and since fees are not a consensus rule, the impact on mining pools' own payouts is small. The fee per action is under a tenth of a cent at current prices.
    • Dodger proposed a tool that calculates the cost of the new rules from a transaction ID, and Kris said it would be easy to add fee calculation to zcash_inspect, which is included in zcashd. Steven added it to the core team's list.

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