Zcash Community Grants Committee Google Meet Meeting: August 31, 2026
This is part one of two posts due to the length of the minutes. Second part is first comment below.
Attendance:
-
Artkor
-
Zerodartz
-
Paul
-
Hanh
-
Gguy
-
Alex (FPF resource, notetaker)
All votes unanimous except ZECsy (Hanh voted against), Zcash Arabia (Zerodartz and Artkor voted against). Paul recused himself from the PGPZ discussion.
Key Takeaways:
-
Open Grants
-
Constant-Time Hardening and Explicit Timing Semantics for Zcash Rust Cryptography
- Approved async
-
Test-Effectiveness Audit for Zebra: an independent regression witness for consensus-critical code
- Declined
-
Rvess Pay ZEC to Mobile Money Integration
- Declined
-
Zcash WalletConnect Integration
- Approved
-
Reusable Halo2 Verifier Security Testing Infrastructure (ZKCG Reference Implementation)
- Declined
-
SHPH (Post-Quantum Censorship-Resistant Network Layer)
- Declined
-
ZECsy Community Building: 12 Months of Zcash on the Ground
- Approved (through nine month milestones)
-
BTCPayServer Multi-Store GraphQL Client
- Approved
-
- Approved
-
Zcash Hack-to-Dark At Devcon 8, Mumbai
- Approved
-
Zcash Arabia (August to December 2026)
- Approved
-
Taking Zcash to the Streets: Education & Real-World Feedback in Türkiye
- Remains open
-
Recoverify: Pre-Loss Backup Recovery Verification for Zcash Wallets
- Remains open
-
Zcash World, Mumbai (Devcon 8 week)
- Remains open
-
Zcash Privacy Literacy Lab Canada
- Remains open
-
Open Grant Proposals
-
Constant-Time Hardening and Explicit Timing Semantics for Zcash Rust Cryptography
-
This proposal requests a grant for a documentation-first constant-time hardening audit of librustzcash — making timing semantics explicit (labeling constant-time vs. intentionally variable-time paths, documenting threat model assumptions, introducing compile-time guards and regression tests) without forcing constant-time behavior universally. Requesting $10,000.
-
Gguy: This has been approved. The applicant has come back with suggestions for how to make the grant more broad across more of the ecosystem. I’ll go back to the applicant with the suggested changes to do that work.
-
Hanh: We said we approve the upgraded grant but he has to set the first one as a milestone one. He’s waiting for a reply.
-
Gguy: I’ll respond.
-
Approved async
-
-
-
Test-Effectiveness Audit for Zebra: an independent regression witness for consensus-critical code
-
Applicant requests a grant to build a targeted mutation testing layer for Zebra’s consensus-critical code paths — using operators derived from real Zebra defect shapes (not random mutation), manual adjudication of surviving mutants, and a verified negative-control regression test for every confirmed gap, addressing the pattern of test-exists-test-passes-defect-recurs documented in four Zebra security advisories. Requesting $45,000.
-
Artkor: Based on ecosystem feedback and our discussion, I don’t support this proposal.
-
Hanh: The feedback was that there’s a lot of false positives and the tool doesn’t really do that well, at least on this codebase. The tool has been tried. The feedback was not impressive and created more noise than value.
-
Declined
-
-
-
Rvess Pay ZEC to Mobile Money Integration
-
Applicant requests a grant to add Zcash shielded payment infrastructure to an existing Cardano-piloted mobile money off-ramp platform, targeting KES, UGX, and TZS payouts via Relworx, with a Rust scanning service consuming compact blocks via lightwalletd, diversified Unified Addresses per quote, ZIP-321 payment URIs, and an idempotent state machine — with real-fund launch conditional on provider approval and KYC/AML controls. Requesting $32,000.
-
Artkor: In its current form, the proposal appears to involve building much of the payment infrastructure from scratch, despite existing solutions for accepting and processing Zcash payments. I think the integration itself could be valuable, but the applicant should first consider whether existing components can be reused rather than rebuilding the entire stack. For this reason, I am not ready to approve the proposal in its current form.
-
Hanh: Agreed.
-
Declined
-
-
-
Zcash WalletConnect Integration
-
Applicant proposes a browser wallet for Zcash with WalletConnect v2 integration — enabling wallet discovery, QR code/link connections, and shielded transaction signing from dApps — plus Zcash lending as a planned ecosystem feature. Requesting $50,000.
-
Gguy: I’m excited about this team and I think they’re capable of moving this integration into something useful, hopefully more broadly across Zcash. But given this will be a first for the Zcash ecosystem, I think there’s probably a little bit of experimentation that has to be within the Zcash ecosystem post grant to see where this is useful across the ecosystem.
-
Paul: I agree I think I’m hopeful that this team would be able to deliver it. So I’m excited about it as well. I approve.
-
Artkor: Even if WalletConnect is not an obviously high-demand feature for Zcash today, I am happy to approve this proposal. It is a well-established and convenient standard for connecting web applications with user wallets, and for Zcash I see it as a useful complement to ZIP-321. Importantly, I expect the result to be more than a Noir-specific integration: it should provide a reusable Zcash integration layer that other wallet and service developers can adopt. I also see potential for this to work well with projects such as ZcashNames. Given that, and the team’s strong track record, I support approving the grant.
-
Zerodartz: While I don’t see immediate super cool use cases for it, I’m sure community developers can get more creative uses for this later. And since this team has a good track record already, then I think they can do it and the budget is quite reasonable also. I’m happy to approve.
-
Hanh: This has two parts. One part is the technical aspect to implement the wallet connect protocol. There’s an SDK on several different platforms. Integration should go fairly well. I don’t foresee technical problems. The challenge is to find an entry point in the wallet connect ecosystem which is dominated by Ethereum and Ethereum ERC20 tokens. I am looking forward to seeing how they get that part done. It’s challenging, but feasible (TON is integrated). We need a strong team to move the needle in this area.
-
Approved
-
-
-
Reusable Halo2 Verifier Security Testing Infrastructure (ZKCG Reference Implementation)
-
Applicant requests a grant to build Halo2 verifier security testing infrastructure — a production test suite for ZKCG’s own verifier (fuzzing harness, 50+ malformed-proof test cases, replay/domain-separation tests, differential Halo2/RISC0 verification) plus a generalized, reusable halo2-verifier-security-patterns/ module that any Halo2-based project can adopt without rediscovering the methodology. Requesting $4,500.
-
Hanh: I asked them what they mean and I’m not quite satisfied by their answer because first they think that they would have called the Orchard bug, but I think afterwards they backpedaled a little bit. In reality, it would be testing the current implementation against itself. It cannot catch logic bugs in circuits. It may catch serialization/formatting bugs in the proof but that has a low chance of success.
-
Artkor: Additionally, after all the testing and review already carried out around Ironwood, I do not see a clear unmet need for this proposal. I reject.
-
Gguy: I also am unsure of the usefulness of this the way it’s currently described. I’m happy to be proven wrong if the applicant wants to provide evidence but my understanding of how this testing would show errors within a Halo 2 implementation doesn’t quite match up. Given we can’t see anybody asking for this right now, it’s hard to approve it.
-
Hanh: I think it’s similar to the one grant that was done a few months ago about fuzzing the zebra transaction parser. They actually found some issues. My recommendation for this one is for them to use this tool themselves. If it uncovers any problem then I’m more than happy to reassess my opinion and even do a retroactive Grant.
-
Gguy: While this technique could be useful in some instances. My understanding is it’s less useful in this instance, but if I can be proven wrong. I’m more than happy to revisit if we see value.
-
Declined
-
-
-
SHPH (Post-Quantum Censorship-Resistant Network Layer)
-
Applicant proposes a post-quantum, censorship-resistant transport layer in Rust — hybrid ML-KEM-768 + X25519 key encapsulation, discrete packet size bucketing for DPI evasion, atomic firewall killswitches, and SOCKS5 underlay routing — positioned as a privacy-preserving networking channel for Zcash nodes and users in censored environments. Requesting $25,000.
-
Hanh: The scope is very large and the problem we try to solve is very complex. This is like reinventing the wheel up to the F1 car, and they don’t have much of a track record to do that.
-
Gguy: Yeah, I think when it comes to security, reputation does carry some weight unfortunately.
-
Artkor: I agree.
-
Zerodartz: I also don’t see the benefits of this compared to TOR or NYM. I reject.
-
Declined
-
-
-
ZECsy Community Building: 12 Months of Zcash on the Ground
-
Applicant requests a 12-month full-time in-person events program: 4 mainstream crypto/tech events (Devcon 8 Mumbai, ETHDenver, CCC Camp, Blockchain.Rio), 4 Exxxotica activations with a ramped sponsorship tier approach (NJ booth → Miami seminar sponsorship → Chicago/Minneapolis larger activations), a standalone AEE/AVN scouting activation, 8 weekend workshops, and ZODL Summit attendance — staffed by a 4-person crew at crypto events, 6-person crew at Exxxotica, and the ZECsy Apprentice Program throughout. Requesting $550,000.
-
Gguy: I’d first like to share my view of what makes things like this worth funding. For me I try to think about how impactful will these efforts be when the grant stops. Will this grant contribute to organic growth in the future? I care less about how many wallets have been installed or how many people have been talked to in the moment. I care more about how many of those people are going to tell their friends, colleagues, or community about Zcash and how many of them will also use it. I have concerns about whether this grant will provide this everlasting impact. Will this team’s efforts be successful in helping foster new communities or groups? I’m not ready to approve this today, but if others do vote to approve, I would recommend that we only approve the first 9months so we can assess the team’s impact. I would hope 9months is long enough to see how impactful this team can be.
-
Paul: I really have a lot of confidence in this team. There’s aspects of what they’re doing that I think are extraordinarily valuable reaching different segments of other communities. And one of the things that comes to mind is what Emersonian posted at one point about the team saying that he recalls that he met me and Josh at a conference industry conference, I think it was mainnet in New York a few years ago, and because of that meeting and because of the booth we had and the discussions we had that brought him into the ecosystem. So even though I would agree that I would love to see a lot of organic growth coming out of this in ways that are very clear even in 9 months. I think that just because of their technical competence, their track record, that even if they only bring on someone like Emersonian, it would be worth it to me to have them out there doing the work that they’re doing. So, I personally would like to approve for 12 or nine. You know, if the committee’s more comfortable with nine, that’s fine. But I would like to give my full approval for whatever the committee is willing to do.
-
Artkor: After our meeting with this team I feel much more comfortable with approving this proposal in full. I’m ready for it.
-
Hanh: I will be rejecting. These are my notes/research for this grant:
-
-
Pros:
-
targets demographics that are usually under-represented
-
sex workers
-
adult industry
-
reliable attendance to events is hard to achieve
-
motivated
-
team well-liked by the community
-
Cons:
-
grant benefits too few people
-
grassroot movement:
-
in person conversations
-
hands on wallet installations
-
-
outcome unclear
-
what is the retention?
-
do these conversations lead to cascading impact? no evidence
-
-
trip reports are unconclusive, focus on # of activations in the order of 100.
-
are sex workers likely to become zcash supporters? no evidence
-
-
costs have escalated
-
no justification why some events would cost
-
“Each event carries a flexible side-event allowance, letting the team
shape the right activation for each city, whether that is a walking
tour in Amsterdam or a Späti takeover in Berlin.” -
$85,000 in booth/side-event costs are undefined or inconsistent: $52,000 sits in a line the applicant’s own spreadsheet labels “flexible, TBD”
-
-
Travel costs are 1/5th - 100k
- high and do not align with a grassroot effort
-
Staff Labor on top of their compensation
- Who is this staff?
-
swag 36k
-
booth 37k
-
-
Can the grant become Business Dev?
-
We ask during a ZCG call
-
Grant was updated, but most of the grant remains grassroot activation
-
Marketing/BD Consultant (Kate), ~10hrs/month $12,000
The only line explicitly tagged “BD” -
Team does not seem to have the proper experience and qualification
-
No success metric for growth
-
Conclusion:
-
overhead is too large, impact too small
-
approving 500k for what is essentially local engagement is out
of line compared to the local communities. It would not be fair to other grant and would show double standards -
Zerodartz: I’ve been going back and forth on this proposal but if we approve for nine months that would make sense to me. They already have some momentum and it does not make sense to me to not have them at any events at all. While the budget is quite large, I think the newer proposal that they revised is more in line with most of our vision and I think they’re doing the right thing. We haven’t seen perfect results quite yet, but I think we could see improvements going forward. I approve for 9 months, but I would say that it’s not the strongest proposal, but worth it to keep them going to events for the near future to then reevaluate the impact.
-
Hanh: Do you guys have any feedback for the reports they should provide so we can decide whether we continue after 9 months or not.
-
Gguy: For myself, I’d hope that by 9months this team can show evidence that their efforts have contributed to new communities and groups adopting and spreading real world use of Zcash, not just a wallets installed metric.
-
Hanh: I would need to see more than the reports they share right now which are like the number of conversations people they meet, what they install.
-
Zerodartz: I can give some feedback on this Hanh because I was at one of Violet’s small workshops and the way she described Zcash and how to use it, I think it was very simple and easy to understand for people who are not always crypto native. So I think that’s one of their main strengths.
-
Paul: Both V and Milo are quite technical and they have experience in cryptography so they’re able to speak from that perspective with a lot of authority. I think that just makes them somewhat unique. And on the issue of not being fair to some of the other groups that are asking for funding, you know, I don’t know that there’s any other group asking to do this work of traveling around to these conferences and doing this kind of evangelism at the grassroots level and in particular with these kind of different communities. I think that’s actually quite unique, we don’t have anyone out there targeting a particular community that is a likely user that you know will be using our tools and using Zcash. So I really think that even though you know it may not be perfect and I do I think you’ve done some good analysis and I think that’s very helpful for me I think it’s good enough and especially given my firsthand knowledge and experience having talked to the team at a few events myself I’m still very much in favor of this grant
-
Gguy: Given the votes today we’ve got one at 9 months and 2 at 12 months.
-
Zerodartz: I’d prefer nine months.
-
Artkor: I think nine months is a good middle ground.
-
Paul: Nine is fine with me.
-
Approved through nine month milestones
Post is too long, continues below.