# ZF Engineering Update: 2025 Sprint 9 (Apr 28 - May 9)

**URL:** https://forum.zcashcommunity.com/t/zf-engineering-update-2025-sprint-9-apr-28-may-9/51227
**Category:** Ecosystem Updates
**Created:** [May 14, 2025, 7:28am UTC](https://forum.zcashcommunity.com/t/zf-engineering-update-2025-sprint-9-apr-28-may-9/51227 "2025-05-14T07:28:53Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![pili](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/pili/32/17303_2.png) [@pili](https://forum.zcashcommunity.com/u/pili)
#### Post date: [May 14, 2025, 7:28am UTC](https://forum.zcashcommunity.com/t/zf-engineering-update-2025-sprint-9-apr-28-may-9/51227/1 "2025-05-14T07:28:53Z")

</div>

Hi everyone,

This is the Zcash Foundation’s Engineering update for Sprint 9 (April 28th - May 9th) of 2025.

During this sprint we focused on releasing [Zebra 2.3.0](https://github.com/ZcashFoundation/zebra/releases/tag/v2.3.0) which was unfortunately delayed due to [issues with our CI integration tests with lightwalletd](https://github.com/ZcashFoundation/zebra/pull/9481) which was preventing us from ensuring that the latest release would not break anything there.

Other work this sprint included finishing off the work to [refactor the RPCs related to block template generation](https://github.com/ZcashFoundation/zebra/issues/9425) in Zebra. We also merged the PR to add the [`size` and `time` fields to the `getrawtransaction` RPC](https://github.com/ZcashFoundation/zebra/issues/9452) which completes the `getrawtransaction` RPC work in Zebra and we are looking into [updating the `validateaddress` RPC](https://github.com/ZcashFoundation/zebra/issues/9273) method to be able to support all types of addresses, including Unified and TEX address. In preparation for `zcashd` deprecation, we have been [working on integrating Zaino, Zallet and Zebra](https://github.com/ZcashFoundation/zebra/issues/9296) to be able to start running automated tests. We have also started working on [constructing shielded coinbase transactions](https://github.com/ZcashFoundation/zebra/issues/5929), starting with unified orchard addresses and [updating the `getblock` RPC](https://github.com/ZcashFoundation/zebra/issues/5449) to return data on value pools and chain supply. Finally we have been working on a [new RPC method `mempool_transactions`](https://github.com/ZcashFoundation/zebra/issues/8620) to notify RPC clients when transactions have been added or removed from the mempool.

Other requested fixes this sprint included the work to ensure the [`getblockchaininfo` RPC response returns chain upgrades in order](https://github.com/ZcashFoundation/zebra/issues/9473) to match `zcashd`, [updating the `z_gettreestate` RPC to make the `finalState` field optional](https://github.com/ZcashFoundation/zebra/issues/9445) and [improving the error message returned by zebra when it crashes on start up](https://github.com/ZcashFoundation/zebra/issues/8617) due to not being able to create or open its state database.

Finally, in order to allow downstream zebra crate consumers to have more control over the versions of their dependencies, we have [changed our dependabot settings to only update the `Cargo.lock` file](https://github.com/ZcashFoundation/zebra/issues/9398) going forward.

With the latest favourable [audit on the FROST server and client components](https://leastauthority.com/blog/audits/zcash-frost-demo/), we have now concluded our development work on the FROST reference implementation, `frost-core`, and the frost server, `frostd`, and `frost-client` until such a time as wallets wishing to integrate FROST provide additional feature requests or request help in using the FROST reference implementation. A blog post highlighting this milestone and next steps will be published later this week.

On DevOps, we spent some time investigating the issues with the `lightwalletd` tests in CI and also started looking into [optimising CI compilation times](https://github.com/ZcashFoundation/zebra/issues/9331).

Thank you for reading!