Zcash Governance Vote: 99.9% Approve 25-Second Blocks, 98.9% Preserve Halvings

Zcash network governance sentiment polls closed on September 14, 2026, with community participation reaching nearly 2.4 million ZEC, according to CoinDesk and Crypto Briefing. Holders voted 99.9% to adopt 25-second block intervals in place of the current 75-second standard, and 98.9% to preserve Bitcoin-style halving cycles roughly every four years rather than adopt a smoothed issuance model outlined in ZIP 234.

The block-time reduction would effectively triple the network's transaction throughput without altering Zcash's hard supply cap of 21 million coins. Per Crypto Briefing's reporting, shielded transactions, which provide enhanced privacy, now account for 59.3% of recent network activity. Approximately 4.89 million ZEC currently sit in shielded pools, representing about 28.9% of circulating supply by Crypto Briefing's measure. The faster block cadence addresses privacy-focused users' demand for quicker confirmation times on confidential transactions.

The halving decision carries long-term implications for miner economics. Per Crypto Briefing, each halving cuts the block reward in half. Zcash's next halving is anticipated in late 2028. The community rejected a proposal that would replace the traditional halving cycle with a smoothed issuance curve, signaling preference for Bitcoin's deflationary model. However, Crypto Briefing notes that Zcash, with a smaller market cap and less fee revenue than Bitcoin, may confront challenges sustaining miner security after repeated halvings sooner than Bitcoin has.

Polls also addressed deprecating Sprout, Zcash's original shielded transaction system, and participants favored a later start date of 2031 for reissuance timing of coins taken out of circulation, per Crypto Briefing.

Crucially, these results are advisory only. According to Crypto Briefing, implementing the accepted proposals requires further development work, comprehensive testing, and formal consensus activation through Zcash's ZIP mechanism. Developers and the community must move the sentiment results into formal specifications, peer review, and network upgrade coordination before any protocol changes take effect.