hi! This conversation is really inspiring but it will get lost if it’s not on its own topic. I’m flagging these last comments so that @Shawn moves them to a better suited topic.
April 2025
Executive Summary
April was a heavy hands-on month with substantial development efforts committed to answering Least Authority’s audit reports and delivering the “Send Max” functionality on librustzcash that can later be integrated to wallets that are librustzcash clients (except Ywallet that uses a fork and already has this). In the “Rel” front, Ledger and Binance took substantial part of our efforts given the locked treasury situation Binance faced due to their dependence on Ledger hardware. @aquietinvestor, @zooko and myself worked long hours along with Ledger to prioritize fixing the outstanding issues, starting with t2t support to unlock Binance which was building up as a critical concern within the community and “crypto-twitter”. We resumed the outreach by leveraging the 6.2.0 release of Zcashd and the impossible to miss long configuration flag to enable deprecated endpoints and ack’ing Zcashd’s deprecation in 2025. NEAR intents Hackathon brought a few teams to the space that we hope they’ll stay building their projects to the finish line.
Extended Report
- Zcash Z3 (Zcashd Deprecation)
- Outreach:
- Piggybacking on the release of 6.2.0, we resumed conversations with many exchanges and mining pools. Big Tech firms are requesting some timeline to be able to prioritize Zcash Z3 into their backlog. All team leaders are committed to analyze our backlog situation and remaining work to provide such input in our best effort that is not over-promising neither too padded far away in time.
- Development:
- BlockExplorer support prep work:
- Synced Testnet node on development machine. Found possible on Zebra and reported it here ZcashFoundation/zebra#9456
- this is now starting to be unblocked thanks to Zaino’s JSON RPC pull request that is in review
- Work on “send max” feature for Zallet and wallets using librustzcash: Finally implemented in several different PRs.:
- BlockExplorer support prep work:
- Development:
- Respond to LA’s Audit report for ZIP-321 Swift
- There were no vulnerabilities reported. Although they found several improvement points. Sent suggested improvements here
- Respond to LA’s Audit report for ZIP-321 Swift
- DevRel:
- NEAR Intents hackathon:
- Participated as a judge with NEAR DevRel
- Ledger:
- Per ZCG’s request I participated in a series of conversations that led to Ledger actively involving into fixing their Zcash issues as it was described on this thread
- Followed up on the Ledger anonymous Survey collected from Zcash Anons which we used to depict the current landscape for Ledger executives.
- Binance:
- Related to the point above, I actively tested Ledger’s fixes with Binance engineers to get their treasury unstuck and get liquidity to their hot wallet.
- Office Hours:
- Zingo Labs:
- Attended some ZingoLabs standups in which I interiorized on project progress, design decisions among other things.
- Red Dev:
- Weekly check in where we debugged their integration with Zebra, discussed bridge’s UI designs and project progress.
- Zingo Labs:
- LCWG, Arborist and other community events:
- Held LCWG meeting #95 and #96
- Attended formerly-twitter Space on Zcash Governance April 16th
- Attended Arborist Calls
- NEAR Intents hackathon:
May 2025
Hello! May is coming to its end! Here’s a new update on this grant.
Executive Summary
This month was very hands-on, with a lot of development around Kotling ZIP-321 library, Zcash Explorer code in Elixir and some Rust polishing the Send Max feature for librustzcash.
Also helped testing and wrapping up some other grants like ZexCavator and ZeWIF. We continue to have contact with different partners of the ecosystem who currently run Zcash nodes but at a slower pace and specifically focused on feedback about migration paths from Zcashd to Zebra from a DevOps Perspective. Given that the containerization of the Z3 stack is progressing, we will soon expect to have the next phase of the outreach unlocked and start asking feedback and testing for those artifacts. There were a lot of PR reviews related to grants coming to completion which is awesome!
Extended Report
- Zcashd Deprecation
- Outreach to Zcashd users:
- So far we got all the responses we could over messaging and current estimates and this is kind of stale. We are going to start doing 1-on-1s as soon as we have alpha builds and containers we can send them over for hands-on testing.
- Updates:
- Development:
- Started work on Zcash Block Explorer support for Zaino. Got it working and added new functionality requested by Coin Market Cap.
(tentative) There’s Transparent spending capabilities that Kris from ECC asked If I could work on which is related to the work on “send-max” I’ve been doing.- This could be worked on top of send max changes. Not planned yet.
- Wrapped-up any changes requested on the “send max” feature
- This needs another round of review by the core team. All comments have been addressed or responded to.
- Responded comments from Zancas on Regtest ZIP zcash/zips@5484134
- Outreach to Zcashd users:
- Development:
- DevRel:
- Ad Hoc Ecosystem Response:
- Coin Market Cap requirements for Total Supply and Circulating Supply
- Worked with Blockchain commons and ZCG on ZeWIF grant completion.
- Support to Unstoppable Wallet engineers on iOS SDK issues
- Ledger NU6:
- Followed up with Ledger engineers and reps on progress of Zcash fixes and paths forward for the Zcash <> Ledger relationship
- Community calls
- LCWG #97 May 15th
- LCWG #98 May 29th
- Arborist Call May 29th
- Arborist Call May 15th
- Crosslink Workshop
- PR Reviews (some are post-merge):
- Reviewed this snippet from Maya devs
- Add github continuous integration builds. BlockchainCommons/zewif-zcashd#1
- Fix ci beta lints BlockchainCommons/zewif-zcashd#2
- Use zcashd-6.2.0-compatible zcash_primitives, zcash_address, and orchard versions instead of zingolibs forked types. BlockchainCommons/zewif-zcashd#3
- Use zcash_primitives to perform parsing for protocol types. BlockchainCommons/zewif-zcashd#4
- Use protocol encodings & remove excessive decomposition of key types. BlockchainCommons/zewif#4
- Add CI workflows BlockchainCommons/zewif#5
- Remove decomposed transaction parts. BlockchainCommons/zewif#6
- Remove binary parsing BlockchainCommons/zewif#8
- Add export block height & account birthday metadata. BlockchainCommons/zewif#9
- Office Hours:
- Met with the RedDev team weekly.
- Attended some Zingo stand up meetings to interiorize myself on Zaino things.
- Ad Hoc Ecosystem Response: