← All calls
ARBORIST#30

Zebra DNS seeder and Tokio

Zebra became able to serve as a lightwalletd backend, and the DNS seeder problem caused by Flux nodes was also resolved.

Agenda summary 5

  1. Zebra update - lightwalletd backend and DNS seeder fix

    Zcash Foundation · Conrado

    • Work on using Zebra as a lightwalletd backend is mostly done, and testing with wallets such as Nighthawk and Zecwallet is complete.
    • One test failure that occurs only in CI remains and is being investigated, and the team said it hopes it is a CI problem rather than a bug.
    • The reason the DNS seeder looked offline was that Flux nodes, a Zcash fork, surged to about 8,000 and the minimum protocol version had not been enforced.
    • Because a DNS seeder returns only a list of IPs, it should return only peers on the default port, but Zebra's seeder returned peers regardless of port, causing the Flux port problem, and this was fixed and deployed.
    • The team also asked for the separate DNS seeder run by former Foundation employee George to be updated, and reported a bug in which some zcashd nodes return Flux peers.
  2. Zebra update - Tokio Console support and preparing a stable release

    Zcash Foundation · Conrado

    • Over the past two weeks, Tokio Console support was added to Zebra. It is a tool for viewing the number of running async tasks, CPU usage and causes of blocking in the terminal.
    • Warnings that workers are not registered for some tasks appeared and are being investigated, and the next step is to analyze the output to find room to improve performance and stability.
    • Usability work such as cleaning up CI documentation and improving the Zebra config file format is under way, and the goal is to put out a release candidate soon.
    • Dodger asked at what point Flux forked relative to the removal of zcashd's remote shutdown (alert) mechanism, and Daira confirmed that Flux changed the alert key.
  3. Zcashd update

    Electric Coin Company · Steven

    • Work on cxx.rs, which replaces hand-written FFI between Rust and C++ with a safer approach, progressed, and Str4d handled it until their vacation.
    • The Zcash address library was updated to expose parser errors externally, and cargo-vet was integrated for dependency verification.
    • To avoid CI fluctuations around the NU5 activation, API work related to Halo recursion was paused for a while and is now proceeding again.
    • An overhaul of the CI system that greatly improves build and test times and stability is due to be deployed soon.
  4. NU5 ecosystem update - Coinbase response

    Electric Coin Company · Steven

    • Coinbase's institutional division finished testing several weeks before NU5 activation, but the team learned late that the retail division uses a separate, older codebase.
    • ECC spent about a week and a half after NU5 activation working through problems with Coinbase, and Str4d played a big role.
    • Coinbase asked for a way to avoid having to parse transactions itself, and ECC is considering adopting UNIFFI, which generates bindings for several languages.
  5. NU5 ecosystem update - wallets and explorers

    Electric Coin Company · Steven

    • All versions of Nighthawk, Unstoppable, Edge and ZecWalletLite are working normally and Ledger has also been restored. Coinmetrics and block explorers are also normal.
    • There is an update to the getrawtransaction and decoderawtransaction RPCs that shows details such as the number of Orchard actions, and it is due to be included in zcashd 5.1.0.
    • 5.1.0 is due on a roughly 6-week cycle after 5.0.0, and they said it is not a situation that requires a hotfix or a halt.

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