← All calls
ARBORIST#51

zcashd 5.5.0 and ZIP-317

zcashd 5.5.0 was released with ZIP-317 proportional fees, and the Zebra audit entered its second phase.

Agenda summary 7

  1. Zcashd 5.5.0 release: ZIP 317 applied

    Electric Coin Company · Kris, Daira, Str4d

    • 5.5.0 came out. It implements the proportional fee ZIP 317, changing the default block construction rules and the default fee acceptance rules for miners who build block templates with zcashd. By the seeder metrics, about a quarter of the network had upgraded to 5.5.0 by the previous night.
    • The zcashd wallet was also greatly improved. The transaction creation methods that had been inconsistent since 4.7.0 were unified so that all follow the ZIP 317 fee scheme, and technical debt was cleaned up and dependencies updated.
    • 5.6.0 will include the changes lightwalletd needs to support almost instant sync. Notes in the wallet can be used immediately, and parallel out-of-order scanning, such as reverse or heuristic scanning, becomes possible.
    • Daira said that because up to 50 unpaid actions are allowed per block, transactions from wallets that have not yet upgraded can still be included.
    • Kris said the closer a transaction is to the ZIP 317 fee, the higher its chance of being selected, and that a transaction sending 500 inputs and outputs for 1000 zat is low priority.
    • Daira said sandblasting had already dropped greatly before 5.5.0 and blocks are generally small. Str4d said large transactions with many actions are still seen, and that they will be affected by the unpaid action limit once miners upgrade.
  2. Zebra audit phase 2 and rc.7

    Zcash Foundation · Deirdre

    • The team is preparing to move CI, build and deployment environments to a Terraform configuration.
    • Phase 2 of the full system audit has begun. Phase 1 focused on cryptographic implementations such as the signing implementation, proof verification and note commitment trees, and on consensus rules; phase 2 covers everything else, including networking and the state layer that checks PoW context.
    • Release candidate rc.7 came out. It has features that were merged but not yet released, including senescence (default 120 days, configurable) in line with the zcashd default, which makes an old zebrad panic and stop.
    • In line with the latest changes to ZIP 401, the Orchard mempool cost threshold was raised from 4000 to 10,000 and the low-fee penalty from 16,000 to 40,000. A panic that occasionally occurred on disconnect was also fixed.
  3. ZSA update: asset swap plan and implementation status

    QEDIT · Jon, Vivek, Kris, Daira

    • QEDIT posted on the forum, as its next plan, a proposal for asset swaps in the ZSA protocol and for running a testnet. The goal is to show it at Zcon4.
    • It is wrapping up the current grant and tidying the circuit and wallet RPC. The big task is catching up so the fork, which has run for almost a year, merges with the main code.
    • When Kris asked whether issuance and burn were implemented as a TZE, Jon answered that it is closer to something more custom. Daira said a TZE is for adding UTXO types so it is awkward, and that defining a new structure in the v6 transaction format is easier.
    • Vivek said the note commitment work in the circuit is nearly done, the client's issue bundle is complete and the RPC is being fleshed out, and the ZIP is at the stage of rearrangement and addressing remaining comments.
  4. FROST demo progress and FROST EVM

    Zcash Foundation · Conrado, Daira, Deirdre

    • The specification incorporates the IRTF chair's comments and awaits the next step toward RFC approval. The demo completed trusted dealer key generation (a binary that creates a key, splits it into shares and prints them).
    • The repair share feature, in which participants at or above the threshold recover a lost share, is also complete and can be used to generate a share for a new participant. Implementation of the broadcast channel for a Noise-authenticated communication channel has begun.
    • A FROST talk will be given at Zcon, and a talk for wallet developers is also planned. Contributor David Craven opened an issue about using FROST in the EVM, which became possible with frost-core's internals feature.
    • A FROST EVM repository was created that uses the EVM's signature recovery function for arbitrary point multiplication to save gas in signature verification. Re-randomized FROST uses the same feature.
    • In answer to Daira's question, Conrado explained that recovery works like DKG, with each helper sending a share of its share. Deirdre said DKG is not in the specification and that what the Foundation implemented will be documented in the Rust docs and the FROST book.
  5. Equilibrium update: crawler and node count

    Equilibrium · Karlo Mardesic, Daira

    • The network crawler was improved, and a p2p wiz tool that draws a node map was built. With Zcash node filtering included, the network size came out at about 200 nodes, not about 6000, and IPv6 scanning is not yet supported.
    • Most are zcashd, and zebrad nodes are under 10%. The next goal is a red team exercise on testnet, and scenarios are being prepared.
    • zcashd nodes report about 1000 in their peer lists, but Flux and Firo nodes are mixed in, and actual connections are about 30. Daira said this is because ports are not filtered and the address manager can be improved.
    • Zebra is normal because it has port filtering.
    • A successful handshake yields the full peer list, so with just the correct IPs and ports the whole network can be mapped, and this is being implemented in the crawler.
  6. Nighthawk update

    Nighthawk Apps · Adi

    • A script that automates zcashd deployment was completed for a distributed, highly available light wallet service. After the initial sync, lightwalletd can be deployed to a new region in a few minutes, and the script will be released as open source.
    • The team hopes lightwalletd 0.5, to be released at the end of this month, supports parallel and reverse scanning APIs.
    • The block explorer reflects v5 fee display and its backend was moved to a new cloud; connections to Tor nodes were stopped, and it remains reachable via a v3 onion address.
    • The wallet team is preparing for Apple's and Google's latest native architectures and for adopting the ECC mobile SDK with ZIP 317 fees.
  7. Open discussion: Zebra stable release schedule and ZSA load

    Adi, Deirdre, Kris, Vivek

    • Deirdre said release candidates are treated as beta. The plan is to release a production 1.0 after the audit and confirming fixes, within the next few months, and audit findings so far have been minor.
    • Asked when ZSA support would come, Deirdre said they have not estimated it yet but that it inherits the Orchard crate and halo2 changes, so it should not be a big job. Nothing in the ZSA design is a problem for Zebra's parallel, asynchronous architecture.
    • Kris asked about the trial decryption load ZSA puts on wallet scanning (per output or per asset), and Vivek said they would check and answer. On PoS, there is little progress because two teams are absorbed in responding to sandblasting and Zebra 1.0.

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