Voting for the Q3 round of the Coinholder-Directed Retroactive Grants Program closed today. Thank you to everyone who took the time to review proposals and vote.
Rejected – Would Reconsider in a Future Round at a Lower Amount
None
Abstain
None
Full vote tallies are available in your favorite vote supporting wallet.
Next steps
FPF will update the GitHub repository to reflect each proposal’s outcome. Funded grantees will be contacted directly by FPF shortly regarding KYC and the disbursement schedule. Questions can be directed to FPF via DM.
The Q4 round will be as follows (subject to minor adjustments):
Call for Proposals: October 30 (Fri) – November 13 (Fri) @ 20:00 UTC
Review Period: November 16 (Mon) – December 16 (Wed) @ 20:00 UTC
Polling/Voting Period: December 17 (Thu) – December 29 (Tue) @ 20:00 UTC
For coinholder votes, a minimum of 420,000 ZEC (2% of the total eventual supply) MUST be voted, with a simple majority cast in favor, for a grant proposal to be approved.
If the votes for Abstain are removed from the tally (which is the only way to correctly interpret “Abstain” in a voting context), then this vote meets both the required threshold (1,140,324.875 non-abstaining votes were cast) and the simple majority (66.4% of non-abstaining votes).
The other votes all had sufficiently-large margins that (at a glance) the results should be the same whether or not abstentions are counted.
Congrats! It’s great to see Zcash voters recognizing and supporting projects that contribute to the security of the ecosystem. Security is the backbone of any project, so it’s fantastic to see this being valued and supported. Keep it up!
And to all the projects that weren’t funded this round: unfortunately it didn’t work out this time, but keep building and keep going. Hopefully, there’s a next time!
For the upcoming Q4 round, could FPF publish the underlying tally with the results, including the Accept / Reject / Lower Amount / Abstain totals for every proposal?
Perhaps more importantly, what is the new-system equivalent of what @dismad did previously with the counter? Can a community member do that now with the new voting stack? If so, it would be useful to document the process for power users.
Old coin voting system: election data + public seed → run counter → results.csv → independently check result. New coin voting system: finalized public vote-chain data → query/export tally → CSV/JSON → independently apply ZIP 1016 → check published result.
Now that the voting feature is working in Vizor, Zkool and ZODL, making the public results easier to independently reproduce and check seems like a worthwhile next step.
P.S. To you purveyors of fine wallets: maybe a simple CSV export feature in the wallets of the questions + final tally data after the election is closed could be implemented. Not feature creep, honest!
The new-system “counter”. Finalized vote-chain data → convert (total_value ÷ 8) → apply ZIP 1016 (≥ 420,000 ZEC voted; Accept > Reject + Lower, abstain excluded) → compare with the published result. Three ways, each step with its expected output:
Q3 2026 result: 37 of 37 outcomes agree with ZIP 1016, quorum met on all, and every tally equals the vote chain’s finalized summary. The raw summary hashes to sha256 9b858326…6639b5, the same bytes on Valar’s server and the Zcash Foundation mirror.
What it does not do yet: re-derive the finalized summary from the encrypted shares in the vote chain’s blocks. That is the true equivalent of Dismad’s counter, and the next step if the Valar team can document it.
Wallet teams: a CSV export after the election closes would still be great. Until then, the downloads above are the same data.
Feedback welcome, especially if any number does not reproduce for you.
There is a particular proposal here where the number of Abstain votes was greater than the number of Accept votes.
Why is it marked as accepted here? Is the acceptance based on the number of Accept votes relative to the Reject votes, excluding Abstain votes?
I would assume there is a minimum percentage threshold that a proposal needs to meet in order to be considered passed/accepted. What are the criteria for accepting a proposal in the Coinholder Poll?
I just came across an earlier exchange/explanation referencing ZIP 1016.
My follow up question is: ZIP 1016 says that a proposal requires “a simple majority cast in favor,” but it doesn’t explicitly state whether Abstain votes are excluded from the calculation of that majority.
Is the simple majority therefore calculated using only Accept vs. Reject votes, with Abstain counted only toward the total ZEC voted for the 420,000 ZEC threshold? @FPF
Thanks @Monsignoree, good question. ZIP 1016 doesn’t explicitly define how Abstain is treated, so here is how FPF applied it in Q3:
Quorum: at least 420,000 ZEC must be voted on the proposal.
Approval: Accept must be a simple majority of non-abstaining votes, meaning Accept > Reject + Lower Amount. Abstain votes are excluded from the majority calculation. This is the standard meaning of “simple majority of votes cast.”
Before Q4 voting opens, we’ll publish these counting rules in the voting announcement, along with the full Accept/Reject/Abstain tallies once voting concludes.
Thanks Alex @FPF. The new ballot-question design has surfaced an edge case worth clarifying, and kudos to @Monsignoree for spotting it.
Just to make sure I understand the quorum part correctly: does ZEC cast as Abstain count toward the 420,000 ZEC minimum?
So, in formula terms: Quorum: Accept + Reject + Lower Amount + Abstain ≥ 420,000 ZEC Approval: Accept > Reject + Lower Amount
If so, that settles FPF’s current counting rule before Q4, and it would be helpful to have that stated explicitly in the Q4 voting announcement.
One related ballot-design question: did unanswered questions in Q3 default to Abstain? If so, an untouched question could still contribute a holder’s full voting power toward quorum. That seems worth looking at separately before Q4.
This is excellent, Michae2xl, excellent. As usual. OpenZcash keeps effortlessly introducing every new feature. We should not take you for granted! This takes a lot of effort.
One UX suggestion: could each proposal eventually click through to a detail page showing the full tally and decision rule visually?
I mocked up roughly what I mean below: total vote volume, the 420,000 ZEC threshold, Accept vs combined Rejects, Abstain, and the arithmetic in one view.
One small caution for now: ZIP 1016 still does not explicitly settle whether Abstain counts toward the 420,000 ZEC minimum, so I would label that as the current FPF counting rule until FPF confirms it for Q4.
Thanks Alex, that’s clear. Counting an explicit Abstain toward quorum makes sense when it is an active choice, and having that stated in the Q4 announcement settles it.
It’s great to see Zcash voters recognizing and supporting projects that contribute to the security of the ecosystem. Security is the backbone of any project, so it’s fantastic to see this being valued and supported. Keep it up!
