STOP! Do you know what you are voting for?

Please read before voting!!!

In the currently open ZCAP poll you will come across this question:

  1. In principle, would you support the introduction of a new funding mechanism to replace the current Dev Fund when it expires in November 2024?

Before you go selecting anything. STOP! and read it again.

Voting Yes, means you support the Dev Fund extension (or rather a new Dev Fund). Voting No, means you dont support a new Dev Fund.

@Dodger am I understanding the question correctly? Please clarify.


I’m a ZCAP member, and just voted on this. This Q was poorly worded.


Correct, with the caveat that there is no specific proposal on the table. This is merely to assess community sentiment.


Thank you!

1 Like

Can anyone vote? I am getting an error “you are not elegible to vote” message.

1 Like

I agree. Poorly worded indeed, I wouldn’t give too much value to the outcome of this vote as it relates to this confusing question.


I answered incorrectly then. I interpreted the words “funding mechanism” as in the source of funding.
To me, the question is asking if ZF should be funded, not from block rewards, but from other sources such as earned income, investment income, or donations from the community.


Yes, I can easily see how ‘new funding mechanism’ could be interpreted as ‘a funding mechanism that is different from the current funding mechanism, i.e. block rewards’


I was stumped by the wording also, because it is as clear as day that the community has a minimum of 3 opinions about the block rewards

  1. retain the block reward as-is
  2. retain the block reward in a new form
  3. remove the block reward

The wording as-is is simply incompetance in leadership. Responsibly constructing a poll question isn’t rocket science. Part of me is wondering if the confusing, binary wording was intending to coerce more ZCAP voters into selecting “Yes” than “No”


There is a 4th option as well, which may also fall under your #2 with a little more detail.

  1. Retain the block reward as is plus add a TXN fee model. That is, let block rewards run their natural course to 0 over time (the sooner the better) until we reach the 21m cap. Then at the same time introduce a fee structure to begin the process of transitioning to a market based system ASAP. Note: it appears the Sustainability Fund is seeking to take the TXN fees as we move to a TXN fee model. If this is working as it appears, it would effectively phase out the ECC and Foundation over time as block rewards are eliminated. Is this what we want? I think No. The Sustainability Fund should be under the Foundation or the ECC and not a new org directly collecting TXN fees. Ideally TXN fees are also designed to cut out the middle men while at the same time directly paying the miners, the blockchain fee for core blockchain development, the respective token yield, and app developers. So for example a 2% TXN fee gets split between these 4 parties (not necessarily equally; but dynamically set), respectively. As we add additional assets, the ecosystem would hopefully generate enough transaction volume such that the transaction fees can be kept low (match competition), offer value to people looking to transact privately (EG the high transaction volume coins will almost certainly be stablecoins), and earn a profit as evidenced by yield or a burn mechanism (preferrable yield give the 21m cap).
1 Like

The transaction fee modification as a funding system should be its own discussion imo.

1 Like

I dont think we should be doing one without the other; its an integrated approach to develop an ecosystem. Parsing these things out separately makes it impossible to develop the ideal or working ecosystem. TXN fees and Block rewards are intricately connected. (Also, it appears there are new orgs already vying to capture the future fees. So that another reason to address it now).

We have a funding need and the question is how is it funded? We really have three levers to pull on: 1) issuance/inflation 2) Fees and 3) community donations. So all three need to be considered at the same time to develop a model that works and ultimately issuance needs to be completely removed with a 21m cap. Issuance/inflation can work only with a burn and its considered viable only when the burn is greater than issuance. But we dont have that model. So that means we need to move to fees now (get the structure working) while over time removing inflation/block rewards.


From a business perspective, I agree with all of your points. But the reality of things are different, because this decision has got to be completed prior to November 2024.

Considering that the Zcash bureaucrats and builders have alredy been under stress the entire past year, while continuing through a state of distress for the foreseeable future, there aren’t enough resources available to adequately re-engineer the fee model to be ready for mainnet by November 2024.

It leaves the ecosystem in a situation where the debates are limited to who gets how much (if anything at all) until after the halving next year.

1 Like

Interesting thread from last year. Given Dodger’s recent ZCAP polls, which continue to ignore all feedback and criticism, I wonder how the regulators would view ZF’s Executive Director’s persistent attempts to manipulate community consensus in favor of direct funding for ZF.


They’d presumably feel the same way, seeing Josh push for another year of direct ECC funding. I don’t think there is a problem with either. I know a lot of people are feeling under represented in polling… speaking for myself, I’ve never even seen my proposal mentioned by polling done by either ECC or ZF… talk about feeling censored out of the debate.

Despite this process requiring the selection/ implementation of a formal ZIP proposal, there has been totally inadequate polling about specific proposal preferences. :man_shrugging:

To me we’ve got to accept the reality here, there are two powerful organizations that drive the Zcash story, and now at this Dev Fund debate juncture, they’ll be the two main competing parties.

Jack has one strategy, Josh has another. Suggesting manipulation doesn’t feel right to me.

1 Like

Does your proposal require adding orgs’ addresses to the protocol? Trying to understand.

Mine involves two direct Dev Fund adminsters (ZF, FPF) who will be recipients for their own operations, and who would also distribute funds to ECC, ZCG, ZecHub, and Qedit.

The duration is 4 years, and I’m calling for the same mandated “non-direct funding model” initiative that Josh has already broke soil for.

1 Like

Didn’t get this part. Does being an administer mean that your wallet gets added to the protocol or does that mean something else?

Yes, they are direct wallet addresses receiving funds from the protocol. (exactly like today, or like what Josh is proposing for another year).

I am using the term adminster in the sense of recommending exactly what ZF does today for the ZCG. They receive the ZCG block rewards, custody them, and distribute them to ZCG without discretion.

Under my proposal, the same would be done by FPF also, and the recipients of the adminstered funds (we could call them indirect block rewards) would be ZCG, ECC, Qedit, and ZecHub.

Edit breaking news from the FPF will impact my proposal, updates will be T.b.d.


Got it. Then it’s simple.

The key difference between direct and non-direct funding models is that direct models add wallets of individual orgs straight into the protocol, while non-direct funding models do not.

Your proposal falls into the direct funding category. Based on the info you just provided, that is a fact. Alternative surveys polled respondents on both, direct and non-direct funding models at the category level without specifying all of the proposals in each category. Your proposal was, in fact, represented in all of those surveys. All surveys that gave respondents an option to choose between non-direct and direct models came back with clear data: respondents prefer non-direct funding.

The old Dev Fund that is about to expire allowed two org wallets to be added to the protocol and receive direct funding for 4 years. Your proposal would ensure that two org wallets would be added to the protocol and receive direct funding for 4 years. At a high level, your proposal is identical to the dev fund expiring in November. There is nothing “same” between your proposal and non-direct funding model. Again, polls that give respondents both categories to vote on, show that the majority would not support proposals in the direct funding model category. I do not anticipate majority support for your proposal, given the category it’s in, but we’ll know for sure when the community votes on the actual ZIPs.

Also, Josh’s proposal for extension advocates for a transition to a non-direct funding model in under a year. To me, it’s clear that a smooth and speedy transition away from direct funding is the main goal of that plan.

1 Like