The Coinholder-Directed Retroactive Grants Program is now accepting proposals for the Q4 2026 round. You can submit a proposal for your own completed work or nominate an individual, company, or project you believe should receive funding to apply for a grant. Retroactive grants provide funding for work that has already been completed and can be publicly verified. Coinholders will decide which proposals to fund through a coinholder vote scheduled for December.
Deadline to submit a proposal: November 13th at 20:00 UTC
Full Schedule:
Call for Proposals: October 30 (Fri) – November 13 (Fri) @ 20:00 UTC
Mandatory Review Period: November 16 (Mon) – December 16 (Wed) @ 20:00 UTC
Polling/Voting Period: December 17 (Thu) – December 29 (Tue) @ 20:00 UTC
Copy and paste your completed proposal into a new separate thread in the Community Grants | Retroactive Grants section of the Zcash Community Forum so the community can provide feedback on each proposal. Make sure you post a comment on your GitHub proposal with the link to your Forum post - if you do not your proposal will not be listed for the vote.
OpenZcash (all eligible applications are posted here with details)
Zcash Grants Hub (all eligible applications are posted here with details)
Understanding the Coinholder-Directed Retroactive Grants Program (CDRGP)
The Coinholder-Directed Retroactive Grants Program (CDRGP) is funded by 12% of block rewards (per ZIP 1016, in effect from November 2025 through Zcash’s third halving in 2028) plus initial capital from the Deferred Dev Fund Lockbox. Funds are held in a legally binding multisig wallet managed by Keyholder Organizations. FPF administers the program’s submission and reporting process via a grant that expires at the end of the Q4 voting period.
Who can apply
Anyone can submit a proposal — for their own completed work, or to nominate another individual, company, or project.
Grants are retroactive only: the work must already be fully completed and publicly verifiable at the time of submission. This program does not fund proposed or in-progress work.
There’s no fixed cap on request size, but grants above $50,000 require FPF to perform KYC checks before disbursement.
If a proposal is rejected by coinholders, the applicant can still resubmit it for consideration through ZCG’s milestone-based model instead.
Process
Call for Proposals — Announced each quarter via the forum, GitHub, and social channels.
Submission — Complete the proposal template on GitHub, then mirror it as a new thread in the forum’s Retroactive Grants category so the community can give feedback.
Mandatory 30-day Review Period — Proposals are discussed publicly; anyone can ask questions or raise concerns directly in the applicant’s thread.
Proposal Summary — FPF publishes a summary of all proposals before polling opens (total requested funding, treasury impact, historical outcomes).
Coinholder Poll — Each proposal is voted Yes/No individually. A minimum participation threshold of ~420,000 ZEC (~2% of supply) per proposal is required for the vote to count, and a simple majority passes. Further voting guidance will be shared prior to the vote.
I’ll be submitting a proposal in the next few days for a critical-severity vulnerability I found and reported to the Zebra team in April. I missed the Q3 window, but after seeing the strong support for the other critical reports last round, I’m putting this one forward for Q4. Programs like this help make sure that finding and reporting serious issues that keep Zcash safe, secure, and operational actually get recognized.
I’d like to submit a retroactive grant proposal for LeekWallet Zcash, an open-source DIY hardware wallet for Zcash (ESP32-S3, PCZT signing, Orchard and Ironwood) that I built and released for ZECATHON. The work is completed and public: firmware, companion apps, a Zodl fork with hardware signing, and a signed release.
I have a process question. My forum account is new and I can’t create topics yet, only reply. That has also kept me from posting my introduction to LeekWallet and my post-ZCon7 thank-you to the Zcash Foundation and, above all, to the community members who took the time to see the board and talk with me at the event.
Since the proposal has to be mirrored as a new thread in Retroactive Grants:
Could a moderator raise my trust level, or let me post in that category, so I can open the proposal thread before the November 13 deadline?
If that isn’t possible in time, is it acceptable to submit the proposal on GitHub and post it as a reply here (or have a moderator move it into its own thread), with the forum link added as a comment on the GitHub proposal?
Thank you, and thanks to everyone at ZCon7. It meant a lot.
Thanks for the mention @FPF, and for coordinating the Q4 round.
Our proposal page now includes smart tags, generated by analyzing each application’s full text and refreshed as proposals are added or updated. These help you find and compare work across topics like security research, infrastructure and cross-chain integration, alongside requested funding and the round’s timeline.
The wider Coinholder hub brings together past results, voting activity, fund tracking, verification resources and Coinholder Copilot, making it easier to follow the program and explore the data behind it.
Feedback, corrections and ideas are always welcome. We’re building this for the community. Mi casa es su casa!
Hi @FPF - I’d like to submit a retroactive grant application this round for a Zebra security advisory I reported (GHSA-j4cw-58mj-7w6v, the ZIP-244 signature-hash amplification fixed in Zebra 7.0.0; I’m credited as the reporter, @asafmod on GitHub, same handle).
My forum account is new, so I can’t create topics in the Retroactive Grants category yet - could you raise my trust level?
I need help so heres the deal. I have zec on safepal and I just input the private key to zkool but it seems not to synchronize. It’s showing up as empty. It’s been trying to reconnect but keeps on failing. So I was thinking maybe I can go to near . Com and bridge it. So I tried to connect the wallet but then it shows up as unavailable wallet. Please help
Hi! Here’s the submission links for the High Severity Remote DoS vulnerability in Zebra 6.2.0 reported to the Zcash Foundation through responsible disclosure