@fabacab, I agree that wider adoption helps protect Zcash. My concern is making one definition of adoption a compulsory grant criterion.
Consider three projects. I cite them as examples, not as endorsements or judgements on their merits.
ZecHub receives ZCG funding for education and community work. Its 2026 ZCG grant is USD 433,079.25.
When ZecHub applies for its next grant, would ZCG have to judge not only ZecHub’s own work but also the smaller projects it funds through its DAO against ZAP’s MUST requirement? How much room would remain for experimentation?
Gleyo, which rewards contributors in shielded ZEC, received a USD 4,500 grant from ZecHub DAO, but its separate coinholder retroactive grant application was rejected.
And MeetZec is a new community project providing tools for organising local meetups. Its creator introduced it to seek feedback and contributions, and has not requested funding.
Now, purely hypothetically, suppose MeetZec sought a ZCG grant to improve its guides, translations and meetup directory. (It would more likely approach ZecHub, but bear with me.) Would it satisfy ZAP’s MUST requirement? Its contribution to adoption might be valuable but indirect, and difficult to measure in advance. What evidence would the committee need before it could approve such a grant?
I have also drafted a proposal for a ZecHub Communities sub-DAO, to fund new ambassadors, local meetups and emerging communities through a six-month pilot in 2027.
It would require a USD 57,200 line in ZecHub’s 2027 ZCG grant application, which ZCG would need to approve. Would that satisfy ZAP’s MUST requirement, when much of the value lies in incubating communities before their adoption impact can be measured?
Some grants put ZEC directly into people’s hands. Others build the knowledge, tools and communities that make using it possible. Both can be valuable, but they need different ways of judging success.
Under ZIP 1015, ZCG already has broad discretion to fund work advancing Zcash’s usability, security, privacy and adoption, including community programmes.
And ZIP 1016 says coinholders SHOULD take account of the same factors the ZCG Committee considers in deciding whether to fund a grant.
Look at how coinholders have actually voted. As I examined in The Hand of God, Q3 approved 17 of 37 proposals. Large security and protocol grants passed overwhelmingly. Gleyo and ZecMap were decisively rejected, and Gleyo, which pays people in shielded ZEC, fits ZAP’s definition of adoption better than almost anything.
We cannot tell from those tallies why. But two things follow. Broad rules do not stop funders being selective. And if work that fits ZAP’s definition struggles for funding anywhere, Q3 suggests it is in the coinholder fund, which ZAP does not expressly change.
ZAP renames the ZCG Committee and adds a compulsory adoption test to what it must consider. ZIP 1016 tells coinholders to take account of the factors that committee considers, though it points to ZIP 1015’s original list.
So does your new test carry over to coinholder grants? If so, is it only a factor coinholders SHOULD consider, or a requirement they MUST satisfy?
And if it doesn’t carry over, and the test is needed to protect Zcash against political attacks, why should it bind ZCG but not coinholders?
I’m not arguing for restricting both. I’d prefer to preserve the broad discretion of both.
I welcome your suggestion to split the proposals. Reaffirming funding for broad adoption is one thing. Making a particular definition of adoption a mandatory gateway to funding is quite another.
The revised ZIP already says the ZAP Committee MAY publish non-normative assessment guidance.
So why not leave grant assessment guidance to the committee, where it belongs?