Coinholder grants should also support ecosystem work
iJaack analyzed the last three coinholder grant rounds, showing they skew toward security and infrastructure, and asked for a way to handle BD, DevRel and outreach work.
The starting point of the post is that if the joint ZCG restructuring proposal (zcash/zips PR #1428) goes ahead, ZCG would keep its treasury but regular funding would end and coinholder grants would continue, making coinholder grants more important. The author said that lack of product awareness, partners having no one to contact, integration difficulty and weak support after onboarding came up repeatedly at Zcon.
In the three rounds the author reviewed, Q4 2025, Q1 2026 and Q3 2026, 23 of 52 proposals passed. By main purpose, developer tools had no approvals across seven proposal votes, and applications such as messaging, identity and accounting had none across eight. In Q3, $7.81 million of the $8.39 million approved (93.1%) went to security and core protocol and operations infrastructure, and everything else combined came to $578,000.
The author drew a line that Q3 included urgent follow-up work on the Orchard vulnerability, and that these numbers say nothing about the rejection rate of BD or DevRel or about the qualifications of rejected projects. They show only what has been rewarded so far and should not become the framework going forward.
For the next round, the author asked for a call for proposals that explicitly names BD, DevRel, outreach and ecosystem support, public examples of evidence that voters would find convincing for each type of work, and feedback that lets rejected applicants know how to improve. Ongoing services should also be packaged as a completed quarter of work so that there is a path to claim retroactive rewards, and the evidence should respect the privacy of the people helped.
This summary is based on the original; check the original for exact details.