Hello fellow Zebras! Another week, another update on Zcashd deprecation!
Outreach (@pili @decentralistdan @pacu):
- Status: on track
We have collected and prioritized partners for the outreach. We divided the different contacts in three tiers (1, 2, 3) and already reached out to tiers 1 and 2. We started to receive responses for the outreach which will be an essential input for Zcash developers. We are focusing on knowing which are the RPCs used by those who run Zcashd nodes among other contextual information that helps us know more about Zcashd infrastructure usage.
For privacy reasons there’s a lot of information that can’t be publicly shared with you all. I’m sure that you will understand. 
Zaino:
- Status: on track
Zaino’s Github repo is pretty loaded with issues. Each one of them is labeled with their corresponding milestone among other informative tags.
I created a kanban board for Zaino. It’s outside ZingoLabs’ org to save ZEC. Otherwise it would require Zingo to pay github for an extra user for me and we can momentarily use this one perfectly fine.
This board only has milestones 1 and 2 (for now) in order not to clog the board just for the sake of it.
Zaino devs are currently working on milestone 1.
In-Memory backend wrap up
- Status: On track
Eric and Willem from ChainSafe, Kris and Str4d from ECC and myself met last monday to talk about how to merge ChainSafe’s work on librustzcash back to upstream. There’s a lot of boiler plate code Eric and Willem had to create to convert some Rust data structures into Javascript objects. That code isn’t “useless” but it’s in an odd place in terms of a valuable general-purpose contribution to upstream, whereas there’s other portions of the In-Memory wallet code what we Do want merged back upstream.
While ChainSafe has gone the extra mile to contribute upstream and make their contributions be useful to the wide ecosystem of Zcash developers, we still have to figure out this last bit, which is a non-trivial effort on their side.
This work will enable one of the critical path branches of the Zcashd deprecation DAG so we are particularly interested on this being completed along with the release of their great library WebZ.js 
Zcashd wallet’s successor
Agree on overall architecture
This is an ongoing discussion that will shape the incoming years of the Zcash wallet ecosystem
- Status: on track (no changes since last week)
Zebra
No introduction needed!
@pili just published ZF’s engineering update! Go read it
There’s work related to implementing a Regtest mode that is equivalent to the one provided by Zcashd.
Zcashd deprecation RPC analysis
Yesterday ECC, ZF, Zingo and ZF folks met in the weekly Zcashd Deprecation sync meeting and we discussed
There are some outstanding questions on how to proceed on already deprecated methods on Zcashd that are being revealed to be highly used by current users.
[Action items]
- If you have ideas, please post them below!
- If you run Zcash infrastructure and have input about this, reach out!
Block Explorer Support
There’s a lot of work needed to be able to support block explorers. Overall, the major point to bring up is that Zaino will have a key role here, given that Explorers will have to point to it to get the information related to the blockchain. This has many benefits. Zaino is easier to scale horizontally than nodes. Also, nodes don’t learn about transactions queried by the block explorer.
A list of RPCs related to Block Explorers is being curated and maintained by Pili. (Kudos!)