Zcash Z3 updates (formerly Zcashd Deprecation)

Ecosystem Updates
48

February 7th

Hello fellow Zebras! I want to start this update with an amendment to last week’s update. RPC tests port has not been scoped yet by the Zebra team. Although they expressed their interest in doing so given the advantages that were discussed at the Zcashd Deprecation meeting. This work will be scoped and prioritized accordingly by the Zebra team following their engineering processes.

Outreach (@pili @decentralistdan @pacu):

* Status: on track

We are expecting feedback from a couple of exchanges. Thanks to the survey suggestion from @alchemydc we have captured deployment scenarios which will be very useful for what’s to come. (Check the Zallet section for more details()

Zebra

Project Roadmap board
Priority board

In case you’ve missed it, there’s an engineering update from ZF. Specifically on Zcashd Deprecation, Zebra engineers are working on some “score and drop” mechanism for misbehaving peer connections. In terms of RPC work, getrawmempool, getblocktemplate, getpeerinfo and getblockchaininfo are getting some updates and improvements. Getblocktemplate specifically will enable shielded coinbase to orchard UAs, which was something that Zaino folks are requesting for their regtest infrastructure.

Zaino (ZingoLabs)

  • status: off-track :warning:

Project Board

Milestone 2 work is progressing and the team is catching up to the previously announced delay.
The team is close to nail the “Lightwalletd replacement” feature set which is depending on these PRs

Attention to all devs! There are PRs that need review.

In-Memory backend wrap up

- status: pending review :warning:

This has been falling through the cracks a bit, we still need to provide reviews to this PR https://github.com/zcash/librustzcash/pull/1634

“Zallet” (that’s pronounced Zallè, like ballet) formerly Zcash Wallet CLI

  • Status: delayed :warning: (but rapidly catching up)

ECC has notified a deviation of 2 months from the original schedule.

tracking work on this repository.

Zallet added RPC responses (mostly errors) last week. Now is progressing by returning actual results in some of them (this means that Zallet still returns errors for many RPCs that will have to be implemented). Kudos @str4d! This takes us a bit further to one important milestone that is an alpha build that we can send to partners so they test how Zallet integrates into their current stack. We will do so also with the information produced by the outreach where we are asking partners to voice out their preferred software distribution methods. There is also substantial progress on transparent Zcash support by the gap limit implementation that @nuttycom has done that will allow zcashers to recover funds from any wallet of theirs that used transparent ZEC and followed Bitcoin account and address management conventions.

Go Zallet!

Wallet Export format

  • Status: Ahead of schedule

We asked ourselves if https://github.com/zcash/zcash/issues/6873 could be closed with what we have here

I have the pleasure to announce that issue 6873 has been closed. Here’s the Phase 1 completion announcement. Together, we keep crossing out items of the Zcashd deprecation DAG. Congratulations to Blockchain Commons and ZingoLabs for this great milestone.

Shannon, Wolf and Christopher from Blockchain Commons are already working on phase 2 of the grant, as well as @dorianvp from @zingolabs who’s implementing a reference parser which is preliminary work needed for ZeWIF

A brief recap on Phase 2:

  • Interchange specification (BC)
  • Attachment best practices (BC)
  • Review of howto and example implementation (ZingoLabs)

Thank you for reading.

Enjoy your weekend!

10 Likes