Zcash Developer Relations Engineer

Community Grants
43

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

DevRel April 2025

  • 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.:
      • This PR adds tests to verify that sending all the available funds when Fees are known upfront works properly
      • This PR implements the concept of TargetValue as a way to define the intent of matching a spend value with the available funds
      • This PR Implements the bulk of send max
  • 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
  • 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.
    • LCWG, Arborist and other community events:
3 Likes