November 5 has been the pencilled-in date for the next Zcash upgrade for weeks. On October 22, 2026, it became possible for the first time to check whether that date holds. The upgrade's depl
November 5 has been the pencilled-in date for the next Zcash upgrade for weeks. On October 22, 2026, it became possible for the first time to check whether that date holds. The upgrade's deployment document now names a fixed block height, and that height together with the current state of the blockchain produces a window that sits just beside it.
The documented facts: ZIP 259, the document governing the rollout of NU7, lists block 3,543,405 as the mainnet activation height. The Zcash blockchain stood at block 3,527,079 on October 22. Our assessment follows further down: a height in the document does not turn the target date into a commitment from the developers, but it shifts the evidence considerably.
ZIP stands for Zcash Improvement Proposal. It is the format in which the project records its protocol changes, comparable to the BIPs at Bitcoin. Among those documents, ZIP 259 is the organisational one: it governs how and when the upgrade reaches the network. What NU7 changes in substance sits in the other documents.
Two numbers now appear in that document that were not there before. The activation height for the testnet reads 4,465,026, the one for mainnet 3,543,405. Added to that is the consensus branch identifier, 0x77190AD9. That identifier is the value by which a wallet and a node recognise which rule set makes a transaction valid. The document also records that every activation height must be divisible by three, which holds for 3,543,405.
On October 21, cryptoticker.io reported that the same figure was circulating but was entered in no project document, and that six NU7 documents carried the status Draft. That has changed. A count of all eight documents belonging to NU7 returns the status Proposed for every single one as of October 22, 2026: revision 2 of ZIP 207, revision 3 of ZIP 214, plus ZIP 218, ZIP 235, ZIP 237, ZIP 2003, ZIP 2008 and ZIP 259 itself. None sits on Draft any longer. cryptoticker.io compiled this count itself on October 22, 2026; the basis is the eight NU7 documents in the project's public ZIP directory.
Proposed is the stage above Draft and below Final in the project's system. A document at Proposed is fully drafted and intended for implementation, but not yet effective in the network. For holders, that means the contents are settled enough to prepare for.
The two numbers turn into a deadline. Between the state of the blockchain on October 22, 2026, and the activation height lie 16,326 blocks. That number is the real clock of the upgrade, because the network knows no calendar date. It counts blocks, and when the 3,543,405th of them appears depends solely on how quickly miners find the remaining ones.
Zcash has so far targeted a gap of 75 seconds between two blocks. Running the 16,326 outstanding blocks against that target value gives 14.17 days. Measured from the afternoon of October 22, the network therefore arrives on November 6, 2026, at around 01:00 UTC, that is, in the night going into Friday.
The target is an aim, not a promise. How quickly blocks actually appear varies with the computing power in the network and with the difficulty adjustment that evens out that variation. In the 24 hours before October 22, 2026, the Zcash network produced 1,145 blocks. That works out at 75.5 seconds per block, half a percent above the target value.
The deviation is small, but its leverage across two weeks is measurable. With the measured pace instead of the target value, activation moves back by a good two hours, to November 6, 2026, at around 03:00 UTC. cryptoticker.io compiled these figures itself as well, on October 22, 2026, on the basis of the block height and the block count of the preceding 24 hours.
Which rule set a machine follows after activation is decided by the software on the node, not by the calendar.
That allows the widely quoted date to be placed. November 5, which appears in news reports and in calendar round-ups, is the estimate that arises when you start from a slightly earlier block height or calculate in a different time zone. The calculation from October 22 leads both variants into the same window: the night of November 5 going into November 6, 2026.
In practical terms the difference between the two days is secondary, the character of the deadline is not. A block height cannot be moved without changing the document. If miners speed up, the date arrives earlier. If you need to get something done before activation, it is safer to plan around the weekend before November 5.
One part of the document has been overlooked in the coverage so far, even though it is what explains the time window in the first place. ZIP 200, the general rule set for network upgrades at Zcash, contains two safeguards. The first requires the activation height to sit above the end-of-support height of the last software version without support for the upgrade. The second recommends allowing around three months to pass between the first supporting software release and activation.
For NU7, ZIP 259 explicitly suspends both. The document describes the exception as limited to this one upgrade and records that it does not change the planning rules for future upgrades. That exception is precisely why a good two weeks can lie between a recorded height and activation instead of a quarter.
The suspension has a consequence that the document names itself. Because the end-of-support height no longer bites, machines running outdated software will not drop off the network at the moment of activation. Those machines keep running and follow the rule set that applied before NU7. The document therefore requires the accompanying communication to warn operators explicitly to update their software ahead of activation.
A node in that state is not a silent outage but a wrong answer. It displays blocks and balances under the old rules while the rest of the network works under the new ones. That affects nobody who holds their ZEC at an exchange or in an ordinary wallet. It affects everyone who runs a machine of their own and relies on what it displays, for instance when taking payment in a shop.
In substance, NU7 is more than a faster sequence of blocks. ZIP 235 provides that 60 percent of the transaction fees in a block are removed from circulation instead of going entirely to the miners. The remainder stays with the miners. Mechanically that works like a running tightening on the fee side, whose scale rises and falls with the number of transactions.
ZIP 237 introduces a mechanism that holds removed amounts and sums not claimed by miners in a public balance and can spend them again later without altering the halving schedule. On that, ZIP 259 records one sentence that is probably the most important in the whole document for holders: the changes do not raise the cap of 21 million ZEC. Amounts spent out of that balance had previously been taken out of circulation in the same quantity. Around 17.0 million ZEC are currently in circulation.
A threefold higher block frequency means three times as many opportunities to fit shielded transactions in. Because every shielded action costs computing time when it is verified and when a wallet syncs, NU7 brings in upper limits for them, per pool and for the network as a whole. That caps how expensive a block can become for the machines in the network in the worst case. If you sync your wallet regularly, you will notice nothing of it in normal operation.
The target gap between two blocks falls from 75 to 25 seconds with ZIP 218. Around 1,150 blocks a day become around 3,450. A confirmation arrives three times faster, and the same number of confirmations is therefore reached earlier. If you use a fixed number of confirmations as a safety threshold, you should reassess that threshold after the upgrade, because six confirmations cover a third of the previous span of time once the switch is made. A hardware wallet needs no setting for that, a payment stream of your own in a shop does.
From the activation height onward, the network no longer accepts version 4 transactions.
On the market, October 22 went considerably worse for Zcash than for the rest of the front rank. ZEC trades at $1,206.57, after $1,358.62 at the daily high and $1,187.54 at the daily low. The loss over 24 hours comes to 10.5 percent, the span between high and low to $171. Market capitalisation stands at $20.5 billion, trading turnover over the past 24 hours at $1.18 billion. That puts ZEC in tenth place among the largest cryptocurrencies by market capitalisation.
Over longer periods the picture looks different. On a weekly view there is a loss of 2.0 percent, over 30 days one of 20.6 percent, over twelve months by contrast a gain of 392.5 percent. The all-time high of $3,191.93, which Zcash reached in October 2016, remains 62.2 percent away.
The day was weak for the market as a whole. Bitcoin lost 4.1 percent, Ethereum 4.5 percent. Zcash, down 10.5 percent, therefore falls around two and a half times as hard as Bitcoin. Among the 25 largest cryptocurrencies, ZEC is the biggest loser on the day; behind it follow Near Protocol, down 8.2 percent, and Cardano, down 7.8 percent.
That an asset gives up more than the market on weak days after an annual gain of almost 400 percent is the usual mechanic: positions that sit far in profit are sold first, and leveraged positions on such assets are closed out on smaller moves. Added to that is a date occupying the entire market. The US Federal Reserve decides on interest rates on October 27 and 28, 2026, and the Federal Reserve meeting calendar lists those two days as a regular meeting. The upgrade and the rate decision thus fall into the same two weeks.
From the editorial team's point of view, October 22 is progress for NU7 but not a commitment. Three points can be documented in favour: height 3,543,405 now sits in the deployment document and no longer only in a proposal. All eight NU7 documents carry the status Proposed. And the block calculation independently leads into the same window the developers have been naming for weeks.
Against it stands the fact that the project's official upgrade page still carried the sentence on the same day that the activation height for NU7 had not yet been set. As long as the project page and the deployment document diverge, the date remains a derivation from documents and not a public confirmation. If you have to move balances, plan for the earlier of the two dates rather than waiting for an announcement. A total loss remains possible with any cryptocurrency.
The point at which the upgrade touches balances is ZIP 2003. It declares version 4 transactions invalid as soon as NU7 is active. Version 5 and version 6 stay valid, and no new format is added. The ban hits all version 4 transactions, including purely transparent ones and Sapling transactions. What matters is the consequence ZIP 259 names: because transfers out of the Sprout pool can only be represented as a version 4 transaction, balances still sitting in the Sprout pool at activation become unspendable. Sprout is the oldest shielded pool at Zcash and has been superseded for years. The holdings affected are those that have not been moved since. Three steps make sense now:
The two documents on which this article rests are publicly available: the deployment document ZIP 259 with the activation heights, and the NU7 page of the Zcash project, on which the height was still listed as not set on October 22.
(As of October 22, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)
