← All calls
ARBORIST#128

ZcashD retires, Ironwood imminent

ZcashD retired and its repository was archived, and the Ironwood mainnet activation is imminent.

Agenda summary 7

  1. Zebra update

    Zcash Foundation · Marek, Mark

    • Marek said there is no more zcashd and that Ironwood activates on mainnet on Monday.
    • There were five Zebra releases since the last call.
    • The first is the release candidate that activated Ironwood on testnet, and the second is 6.0.0, which fully supports Ironwood on mainnet.
    • 6.0.0 includes a miner optimization: the getblocktemplate RPC caches the shielded coinbase transaction even under short polling.
    • This is because miners call it every 0.5 seconds, while computing the proof for a shielded coinbase takes about 6 seconds.
    • The third and fifth releases are security releases, and the fourth included a feature for putting zcashd behind Zebra.
    • The team started providing reproducible signed binaries and images.
    • Windows and macOS testing in CI was stopped, so these platforms are now tier 3 support, but zebrad can still be run with Docker.
    • The minimum supported Rust version was raised to 1.88.
    • Mark shared issue 11061.
    • It is an issue where a Zebra node keeps connections with peers whose services value is 0 or whose node network is not set, which stalls block requests.
    • Many of these peers that do not serve blocks appear to be Zakura release candidate nodes, and there is a patch to reject them, on which feedback was requested.
  2. ZODL update: Ironwood

    ZODL · Pacu

    • The team is preparing a librustzcash crate release with the necessary changes, and librustzcash main can be used now.
    • The crate release comes the next day, an SDK release on Friday or Saturday, followed by an app release containing the migration flows for Keystone and ordinary seed phrase hot wallets.
    • It is finishing support for note locking, which is key to the Ironwood migration.
    • Small leftover notes (for example 0.00005 ZEC) can be used by eavesdroppers to estimate a balance, so this is a tool that lets users and app developers hold them without migrating or choose the timing.
    • It offers two flows: immediate migration and privacy-preserving migration.
    • Wallet-related questions will be taken at the light client working group at 17:00 (UTC) that day.
  3. ZODL: zcashd shutdown and Zallet update

    ZODL · Pacu, Nate

    • 61% of the organizations contacted responded that they had finished migrating, and the remaining 20-odd percent said they would update but have not responded.
    • Since there have been no reports of errors or outages, they are assumed to have migrated, and follow-up inquiries are made daily.
    • Almost 100% of mining power has moved to the new software.
    • The wrapper approach of Valar Group and ZF and the stack approach of Shielded Labs were successful.
    • No major disruption was reported, only issues like questions from those using Zebra for the first time.
    • Zallet released 1.0.0-beta.1.
    • It currently prioritizes Ironwood and user-facing software, and has not yet done automatic migration work for miners.
    • If a miner sends their Orchard balance to their own Orchard receiver, after NU 6.3 activation (July 28) it is automatically opted into Ironwood and moved.
    • Miners already shield the coinbase and then pay out to a transparent address, so no separate problems were reported.
    • Those not using Zallet use the zcashd wrapper that connects only to a Zebra node, and after July 28 even if a zcashd fork changes the end-of-life constant, it will fall out of consensus.
    • When Nate asked about a dashboard to monitor problems around the shutdown date, Pacu recommended community resources such as CipherScan (mainnet, testnet and Crosslink) and the mining pool stats on ZcashInfo.com run by Foundry.
  4. zcashd deprecation update

    ZODL, Zcash Foundation · Pacu

    • The zcashd deprecation wrapped up without problems.
    • A few days ago the zcashd repository on GitHub was archived, and the speaker said a new era of memory-safe-language nodes has begun.
    • Pacu thanked those doing the behind-the-scenes formal verification work, including Daira Emma and Tachyon's Sean Bowe, which underpins the strength of the Ironwood pool.
  5. Network Sustainability Mechanism (NSM) update

    Shielded Labs · Judah

    • With the Ironwood implementation, some of the changes related to ZIP 234 and 235 were moved or removed in the current Zebra codebase.
    • The team will consult with the Zcash Foundation's Zebra developers on how to reintegrate the NSM into the post-Ironwood implementation, schedule that this week or next, and plans to get back to NU 7 readiness.
  6. Crosslink update (Trailing Finality Layer)

    Shielded Labs, ZODL · Nate

    • A user released a tool to coordinate a hard fork that slashes a finalizer, and feature net users used it to slash an unresponsive finalizer, so BFT resumed.
    • It was described as the first dynamic hard fork in Zcash history, achieved just by using the tool, with no network reset or separate release.
    • Capacity is lower because of Ironwood and conference attendance, but the team is focusing on stability and bug fixes.
    • There have been 9 releases so far in Season 2, and the 10th is coming soon, at a pace of one per week.
    • The next release includes sync performance and network reliability improvements and a likely fix for the out-of-memory problem.
    • The workshop planned for this week was postponed to the end of August (together with the company-wide meeting).
    • When the team meets next week, it will decide the balance between bug fixes for the current season and the backlog of consensus changes that do not need backward compatibility and will be handled with a network restart, and also decide the order of the Ironwood merge.
    • It is improving project management and milestone visibility.
  7. Dynamic fees update

    Shielded Labs · Mark

    • The getstandardfee RPC was merged and released with Zebra.
    • For now it returns only the ZIP 317 standard fee of 5000 zat and a version field, and the plan is to bump the version field once a real fee estimator arrives.
    • Two wallets, Nosy and Noir, display the priority lane, and seven other wallets have promised to implement it.
    • The next step is to get wallets to follow the getstandardfee RPC.
    • Wallet work is lower priority because of Ironwood, and ensuring wallet safety and usability during the migration comes first.

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