Market cap $2.19 T −3.65 % over 24 hours24h volume $73.68 BBTC dominance 58.1 %ETH 10.0 %Fear & Greed 10 Extreme fearCoins 21,490

Zcash developers want 20-second blocks days after NU7, in a draft ZIP with no poll date yet

Zcash block time could drop from 25 to 20 seconds under a draft ZIP posted on 8 November. It is unreviewed, with no ZIP number and no poll date yet.

11 min read

Abstract shield over stacked isometric blocks with an hourglass and a ballot box
Table of contents
  1. NU7 went live on 6 November, and 25-second blocks are running
  2. A third cut in Zcash block time
  3. Why 20 seconds: a faster first confirmation
  4. What the 20-second draft ZIP changes, number by number
  5. The price of faster blocks: orphans, timing and who must adapt
  6. What it would mean for wallets, exchanges and holders
  7. NU7.1 was planned for the grants vote, not for block times
  8. First reactions on the forum
  9. What is still unknown

Two Zcash developers from Valar Group, Dev Ojha (ValarDragon on the forum) and Evan Forbes, want to cut the Zcash block time again, from 25 to 20 seconds, only days after the NU7 upgrade brought it down from 75 seconds. Ojha posted the proposal on the Zcash Community Forum on Sunday 8 November at 20:56 UTC, with a draft Zcash Improvement Proposal (ZIP) filed as pull request #1437 in the zcash/zips repository on GitHub.

It is only a draft. The ZIP has no number (its header reads “Unassigned”), and the pull request was still open, with no comment and no review, at 08:20 UTC on Monday 9 November, according to the GitHub API. No poll, activation height or date has been set. The authors ask for it to go into the next coinholder poll and into a small follow-up upgrade they call NU7.1.

What it would change is narrow. The expected wait for a first confirmation would fall by five seconds, or 20%. Values tied to the clock, from the 1,800 ZEC issued each day to the halving dates and the default life of a transaction, would be stretched to stay the same in hours and days. Per-block limits on shielded transactions would shrink to four fifths, so private capacity per day would not grow. The cost shows up in orphan blocks and in finer timing data for anyone watching the chain.

NU7 went live on 6 November, and 25-second blocks are running

NU7 itself activated on Friday 6 November at block 3,543,405, mined at 02:34:02 UTC according to Blockchair’s explorer data, the height that had been set in advance and that our NU7 activation page was tracking. The new pace is visible on chain: from that block to the tip at 3,554,409, read at 08:09:33 UTC on 9 November, 11,004 blocks came in 77.6 hours, an average of 25.4 seconds each. Blockchair counted 3,439 blocks over the last 24 hours, or about 25.1 seconds per block.

The draft was ready before those blocks were. Its header gives 4 November as its creation date, two days before NU7 went live, and the pull request was opened on 5 November at 16:48 UTC. The forum post that made it public came three days later.

A third cut in Zcash block time

Zcash started with blocks every 150 seconds. The Blossom upgrade, specified in ZIP 208 and activated at mainnet block 653,600, halved that to 75 seconds. NU7, through ZIP 218, took it to 25 seconds. A move to 20 seconds would be the third reduction and would make blocks seven and a half times more frequent than at launch.

Each cut pays less per block and counts the halving interval in more blocks. After NU7, 3,456 blocks a day at 0.52083333 ZEC make 1,800 ZEC; at 20 seconds, 4,320 blocks of about 0.4167 ZEC would make the same 1,800, under the same 21 million cap.

Ojha writes that 25 seconds “was never the final target, just the next step” in the original plan. In a reply on 9 November he set the goal at reliable inclusion in under a second, which he said proof-of-work block time cuts alone will not deliver.

Why 20 seconds: a faster first confirmation

The case rests on waiting time. In the authors’ words, “every transaction waits for block inclusion, even when blocks are nearly empty”. Zcash blocks are mostly near empty: Blockchair counted about 7,660 transactions in 3,439 blocks over the 24 hours to 08:09 UTC on 9 November, barely two per block. A payment still sits until the next block is found.

The forum post names three uses where those seconds matter: payments at a point of sale, deposits to exchanges, and cross-chain swaps through NEAR Intents, where market makers want at least one confirmation before they act. Swaps of shielded ZEC through NEAR Intents carry their own issues, as we reported when Zakura proposed a separate viewing key for every swap.

Abstract hourglass and lightning bolt beside a payment card, wallet and bridge
A 20-second target would cut the expected wait for a first confirmation by about five seconds.

What the 20-second draft ZIP changes, number by number

The specification keeps the 2 MB block size limit and scales most other values by 5/4 or 4/5. The main figures, against the rules NU7 put in place:

ParameterSince NU7 (25 s)Draft (20 s)
Block target spacing25 seconds20 seconds
Blocks per day3,4564,320
Halving interval5,040,000 blocks6,300,000 blocks
Scheduled subsidy at halving index 326,041,666 zatoshi20,833,333 zatoshi
Difficulty averaging window102 blocks (2,550 s)128 blocks (2,560 s)
Max Orchard or Ironwood actions per block330264
Max Sapling inputs and outputs per block300240
Default transaction expiry120 blocks150 blocks
Anchor depth (3 blocks)about 75 secondsabout 60 seconds
MAX_REORG_LENGTH node defaultat least 600at least 750
Worst-case light wallet bandwidth per day169.10 MB169.18 MB

On the subsidy, the draft requires the exact 5/4 ratio and a single rounding step: multiplying the already rounded 25-second figure by 4/5 would give 20,833,332 zatoshi, one short. It concedes that integer rounding still changes the realized schedule, so issuance is unchanged by design, not to the last zatoshi.

The shielded limits matter more. ZIP 218 set them so that someone filling blocks could not force light wallets to download and trial-decrypt more data per day than before NU7. Keeping 330 actions per block at 20 seconds would have raised that worst case by 25%. Scaled by 4/5, the daily maximum stays at 1,140,480 Orchard or Ironwood actions, plus about 78 kB a day of extra block headers. Two-action shielded transactions stay capped at 6.6 per second: the gain is latency, not private capacity.

Transparent traffic is another matter. With the 2 MB limit per block kept, the maximum transparent data per unit of time rises by 25%, a cost for full nodes’ bandwidth and disks but not for light wallets.

The price of faster blocks: orphans, timing and who must adapt

Shorter blocks give a newly mined block less time to reach other miners before a rival block appears. The losing block is orphaned and its miner earns nothing, the main risk the authors discuss. They tested 20-second blocks on a network of 80 equal miners spread over 12 regions, from New York and San Francisco to Singapore and Bangalore, with full 2 MB blocks under worst-case load.

The forum post gives 1.9% of blocks orphaned on a network running only Zakura’s node software, and 3.3% on a network split evenly between Zakura and Zebra-Andele. The bar set by the May test that supported 25-second blocks was 4.68% in the empirical test and 3.26% in the theoretical model, so they argue the 20-second design already clears it (the forum post compares the 1.9% and 3.3% results with that bar). They add that real mining is less spread out than their test network, since pools cluster geographically, and that Ethereum’s old proof-of-work chain ran at a 5.4% orphan rate. These are the authors’ own measurements and comparisons; no independent team has published a review.

The live data is less tidy. The draft ZIP says that since NU7 the orphan rate rose from 0.66% to 0.83% (0.85% a line later), while noting that average block size differed between the two periods (53 kB against 10 kB). In his forum reply on 9 November, Ojha wrote that the live orphan rate of Zcash is lower than before the upgrade, posting a screenshot rather than a figure. The two documents do not agree, and the draft still carries a to-do note on an older Zakura benchmark of 1.45%.

Abstract connected nodes, a pickaxe and a server rack under a warning sign
The authors' tests put orphan blocks at 1.9% to 3.3% with 20-second blocks.

The draft has a privacy section. “Shorter blocks give observers finer timing information without changing what individual shielded transactions reveal,” it reads. Wallets are advised to build shielded spends on an anchor three blocks deep, which would cover about 60 seconds instead of 75. If the chain rolls back past that anchor, the transaction becomes invalid, and a replacement that spends the same notes exposes the same nullifiers, which links the two. The ZIP adds that ordinary orphan measurements say nothing about how deep a rollback can go; our guide to finality and chain reorganisations explains the difference.

Some transactions would stop fitting. One with 300 Orchard actions, valid today, could never be mined after activation; the draft asks nodes to drop such transactions from their mempools at the activation height and wallets not to create them.

What it would mean for wallets, exchanges and holders

For services that count confirmations in blocks, the arithmetic is direct. An exchange that credits a ZEC deposit after 10 blocks would wait about 200 seconds instead of 250. The authors say the ZIP asks no one to lower a confirmation count, and that services setting policy by elapsed time or by accumulated work need to change nothing. To an objection raised in the 25-second debate by the forum user shielded-nate, that shorter blocks mean less security per confirmation, they reply, citing another user, that protection against a minority attacker grows exponentially with each confirmation, so a count only has to rise slightly to stay as safe.

Wallet makers would raise the default expiry from 120 to 150 blocks, still about 50 minutes, and node software would get new defaults for reorg depth and block downloads. All of it would come in a separate network upgrade: every node operator, miner and exchange running a Zcash node would have to upgrade again, weeks or months after NU7.

For holders, supply is untouched by design, and a payment would confirm a few seconds sooner. Our Zcash (ZEC) page covers how the coin and its shielded pools work.

NU7.1 was planned for the grants vote, not for block times

The name NU7.1 comes from a timeline published on 5 November by the five organisations that coordinate Zcash’s coinholder voting: Project Tachyon, Shielded Labs, Valar Group, the Zcash Foundation and ZODL. That timeline is about the future of Zcash Community Grants and its share of the Dev Fund, the dispute behind Sean Bowe’s plan to end the grants’ 8% cut. Proposals were due by Sunday 8 November at 11:59 pm UTC, the poll questions are to be published on 9 November for feedback until 15 November, and polls for coinholders and community panels run from 16 to 30 November.

If rough consensus emerges, engineering teams and miners would then agree a date for NU7.1, whose main purpose is to implement the approved grants ZIP. “Major features and transaction format changes are outside the scope of this upgrade,” the organisers wrote, while leaving room for smaller improvements that the engineering teams judge they can ship safely by the target date.

Ojha replied in that thread at 20:59 UTC on 8 November, three minutes after posting his proposal, asking for the 20-second reduction to be included in this poll as well; he called it technically ready and low risk. Valar Group, his employer, is one of the five coordinating organisations.

Not everyone wants the two mixed: another user, Julian, asked the same evening that funding choices and technical changes be kept as separate voting questions, so that someone could back one without the other. Whether block time will be on the ballot was not known on Monday morning. The draft also touches the grants’ machinery: before it can move to Proposed status, its authors must still settle how funding-stream end heights and the NSM reissuance trigger work under a second spacing change, two items they flag as open.

First reactions on the forum

By 08:15 UTC on 9 November the thread had three replies. A user named zeckzodel said he was generally in favour but asked whether 20 seconds is really the optimum, or whether 17 or 21.4 seconds would score better on the data already available. Ojha answered that usability is the goal, that the chain’s peak load of about 80 KB per second would rise to about 100 KB per second, “tiny quantities” in his words, and that the next large gain should come from doubling the maximum block size.

A third user, Milton, argued that truly low latency needs a different consensus algorithm, and doubted that could happen without a fork, given the opposition to proof of stake among Zcash users on X. No statement from the Zcash Foundation, Shielded Labs, ZODL or any exchange had appeared by then, and no ZIP editor had commented on the pull request.

What is still unknown

Beyond the missing ZIP number and activation height, nobody has said whether the organisers will add the change to the 16 to 30 November poll, or whether the miners and pools who carry the orphan risk support it.

ZEC traded near $1,192 at 08:09 UTC on 9 November according to Blockchair, on a morning when total crypto market capitalisation was down 6.7% over 24 hours; no source links the move to the proposal. The next dates to watch are the publication of the poll questions on 9 November and the close of feedback on 15 November.

Sources

  1. Zcash Community Forum: Proposal: Lower Zcash block target spacing from 25s to 20s (8 November 2026) forum.zcashcommunity.com
  2. GitHub, zcash/zips pull request #1437: Draft ZIP, reduce block target spacing from 25 to 20 seconds github.com
  3. Zcash Community Forum: ZCG and the Dev Fund, timeline for proposals and polling (5 November 2026) forum.zcashcommunity.com
  4. ZIP 218: 25-second block target spacing zips.z.cash
  5. ZIP 208: Shorter block target spacing (Blossom) zips.z.cash
  6. Blockchair: Zcash block 3,543,405 (NU7 activation, 6 November 2026) blockchair.com

Leave a Reply

Your email address will not be published. Required fields are marked *