{"id":7398,"date":"2026-10-21T09:59:57","date_gmt":"2026-10-21T09:59:57","guid":{"rendered":"https:\/\/cryptolinks.com\/news\/?p=7398"},"modified":"2026-10-21T09:59:57","modified_gmt":"2026-10-21T09:59:57","slug":"zcash-nu7-activation","status":"publish","type":"post","link":"https:\/\/cryptolinks.com\/news\/zcash-nu7-activation","title":{"rendered":"Zcash NU7: ZEC Rallies as November 5 Target Nears\u2014What 25-Second Blocks, Sprout and Fees Mean"},"content":{"rendered":"<p>Zcash is rallying as its next network upgrade gets a more precise launch target. At my October 21 market check, ZEC was up <strong>12.86% over the previous 24 hours<\/strong>. Developers have agreed to target <strong>NU7 at mainnet block 3,543,405<\/strong>, currently estimated around <strong>November 5, 2026<\/strong>. If the deployment is finalized, the upgrade will target 25-second blocks, retire legacy Sprout spending and change how transaction fees support future mining rewards.<\/p>\n<p><strong>Status and market-data note (October 21, 2026):<\/strong> Research cutoff <strong>08:55 UTC<\/strong>; CoinMarketCap readings were checked at approximately <strong>08:51\u201308:54 UTC<\/strong> across dynamically updating pages. Block 3,543,405 is the <strong>agreed proposed height<\/strong>, not yet a completed activation. November 5 is a <strong>calendar estimate, not a guaranteed time<\/strong>. At this cutoff, <a href=\"https:\/\/zips.z.cash\/zip-0259\" rel=\"noopener\">ZIP 259<\/a> still showed the mainnet activation height as \u201cTBD,\u201d while the <a href=\"https:\/\/github.com\/zcash\/zips\/pull\/1405\" rel=\"noopener\">October 20 height proposal<\/a> remained open. The <a href=\"https:\/\/zakura.com\/nu7\/\" rel=\"noopener\">Zakura NU7 dashboard<\/a> showed mainnet as pending.<\/p>\n<p><strong>Important for legacy Sprout holders:<\/strong> If your ZEC remains in a <strong>Sprout shielded address<\/strong> (typically starting with <code>zc<\/code>), NU7&#8217;s version-4 transaction prohibition would make those funds <strong>unspendable under the rules active from block 3,543,405<\/strong>. This is not a warning for all shielded wallets. Verify your wallet and seek help with a compatible <strong>Sprout-to-Sapling migration<\/strong> <em>before<\/em> activation. The <a href=\"https:\/\/zcash.readthedocs.io\/en\/master\/rtd_pages\/sapling_turnstile.html\" rel=\"noopener\">Zcash project&#8217;s legacy migration documentation<\/a> describes the original process, but its <code>zcashd<\/code> software has been deprecated; do not assume an old instruction works unchanged today. Preserve backups and never share a seed phrase, spending key or <code>wallet.dat<\/code> with a website or stranger.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-7404\" src=\"https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Why-is-Zcash-rising-today.png\" alt=\"Why is Zcash rising today\" width=\"2304\" height=\"1296\" srcset=\"https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Why-is-Zcash-rising-today.png 2304w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Why-is-Zcash-rising-today-300x169.png 300w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Why-is-Zcash-rising-today-1024x576.png 1024w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Why-is-Zcash-rising-today-768x432.png 768w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Why-is-Zcash-rising-today-1536x864.png 1536w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Why-is-Zcash-rising-today-2048x1152.png 2048w\" sizes=\"auto, (max-width: 2304px) 100vw, 2304px\" \/><\/p>\n<h2>Why is Zcash rising today?<\/h2>\n<p>The market move is real; the explanation is less certain. Here is the compact snapshot I used rather than mixing a daily candle with a rolling return or a one-off intraday spike.<\/p>\n<table>\n<thead>\n<tr>\n<th>Metric<\/th>\n<th>Value<\/th>\n<th>Measurement window<\/th>\n<th>Source<\/th>\n<th>Observation<\/th>\n<th>Limitation<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>ZEC price<\/td>\n<td><strong>$1,272.43<\/strong><\/td>\n<td>Spot-market aggregate snapshot<\/td>\n<td><a href=\"https:\/\/coinmarketcap.com\/currencies\/zcash\/\" rel=\"noopener\">CoinMarketCap ZEC<\/a><\/td>\n<td>Approx. 08:51 UTC, Oct. 21<\/td>\n<td>Live aggregate, not a single venue&#8217;s executable quote<\/td>\n<\/tr>\n<tr>\n<td>ZEC change<\/td>\n<td><strong>+12.86%<\/strong><\/td>\n<td>Rolling prior 24 hours<\/td>\n<td><a href=\"https:\/\/coinmarketcap.com\/currencies\/zcash\/\" rel=\"noopener\">CoinMarketCap ZEC<\/a><\/td>\n<td>Approx. 08:51 UTC<\/td>\n<td>Changes continuously<\/td>\n<\/tr>\n<tr>\n<td>ZEC trading range<\/td>\n<td><strong>$1,123.29\u2013$1,286.46<\/strong><\/td>\n<td>Rolling 24-hour low\u2013high<\/td>\n<td><a href=\"https:\/\/coinmarketcap.com\/currencies\/zcash\/\" rel=\"noopener\">CoinMarketCap ZEC<\/a><\/td>\n<td>Approx. 08:51 UTC<\/td>\n<td>Not a UTC calendar-day candle<\/td>\n<\/tr>\n<tr>\n<td>ZEC trading volume<\/td>\n<td><strong>About $1.16 billion<\/strong><\/td>\n<td>Rolling 24-hour turnover<\/td>\n<td><a href=\"https:\/\/coinmarketcap.com\/currencies\/zcash\/\" rel=\"noopener\">CoinMarketCap ZEC<\/a><\/td>\n<td>Approx. 08:51 UTC<\/td>\n<td>Gross traded volume, not capital inflow; page displayed a +63.42% volume-change indicator without a separately archived comparison series<\/td>\n<\/tr>\n<tr>\n<td>Bitcoin (BTC)<\/td>\n<td><strong>+1.98%<\/strong><\/td>\n<td>Rolling prior 24 hours<\/td>\n<td><a href=\"https:\/\/coinmarketcap.com\/currencies\/bitcoin\/\" rel=\"noopener\">CoinMarketCap BTC<\/a><\/td>\n<td>Approx. 08:52\u201308:54 UTC<\/td>\n<td>Close in time, but not synchronized tick by tick<\/td>\n<\/tr>\n<tr>\n<td>Monero (XMR)<\/td>\n<td><strong>+5.19%<\/strong><\/td>\n<td>Rolling prior 24 hours<\/td>\n<td><a href=\"https:\/\/coinmarketcap.com\/currencies\/monero\/\" rel=\"noopener\">CoinMarketCap XMR<\/a><\/td>\n<td>Approx. 08:52\u201308:54 UTC<\/td>\n<td>Same snapshot caveat<\/td>\n<\/tr>\n<tr>\n<td>Dash (DASH)<\/td>\n<td><strong>+1.62%<\/strong><\/td>\n<td>Rolling prior 24 hours<\/td>\n<td><a href=\"https:\/\/coinmarketcap.com\/currencies\/dash\/\" rel=\"noopener\">CoinMarketCap DASH<\/a><\/td>\n<td>Approx. 08:52\u201308:54 UTC<\/td>\n<td>Same snapshot caveat<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Three possible forces deserve separate attention.<\/p>\n<p><strong>First, a clearer upgrade milestone.<\/strong> The broad November target was public back on <strong>September 17<\/strong>, when ecosystem participants outlined the <a href=\"https:\/\/forum.zcashcommunity.com\/t\/nu7-timeline\/57655\" rel=\"noopener\">NU7 schedule<\/a>. The new information on <strong>October 20<\/strong> was the precise activation height, recorded in an <a href=\"https:\/\/github.com\/zcash\/zips\/pull\/1405\" rel=\"noopener\">open specification pull request<\/a> and reflected on Zakura&#8217;s dashboard. That reduces one uncertainty, even though it does not remove implementation or network risk.<\/p>\n<p><strong>Second, a stronger wider market.<\/strong> Bitcoin was also positive in the checked rolling window, so ZEC was not rising in isolation. The much smaller increases in XMR and DASH show that this particular ZEC move cannot simply be described as every privacy coin moving together. There may be renewed attention on privacy-focused assets, but price action alone does not demonstrate an increase in private payments or shielded adoption. For the longer-running context, I would compare this session with <a href=\"https:\/\/cryptolinks.com\/news\/zcash-price-privacy-coin-rally\">Cryptolinks&#8217; earlier ZEC privacy-coin rally analysis<\/a> and its <a href=\"https:\/\/cryptolinks.com\/privacy-coins\">privacy coins directory<\/a>.<\/p>\n<p><strong>Third, momentum and positioning.<\/strong> ZEC&#8217;s sharp move could reflect traders responding to the news, existing momentum or short-term speculation. Without a timestamp-aligned futures, funding and liquidation dataset, I would not label today&#8217;s gain a proven short squeeze, a wave of institutional buying or a direct one-to-one consequence of the NU7 decision. Readers who want that market distinction can review the <a href=\"https:\/\/cryptolinks.com\/crypto-futures-derivatives\">Cryptolinks crypto futures and derivatives guide<\/a>.<\/p>\n<p>For me, the strongest defensible conclusion is that the <strong>rally coincided with fresh deployment clarity against a positive market backdrop<\/strong>. The available data cannot allocate a precise percentage of ZEC&#8217;s price move to each cause.<\/p>\n<h2>What exactly did developers agree on for NU7?<\/h2>\n<p>The sequence matters:<\/p>\n<ul>\n<li><strong>September 17:<\/strong> A community timeline named <strong>November 5<\/strong> as the intended mainnet date and <strong>October 20<\/strong> as the decision point; these were planning targets, not activated chain rules.<\/li>\n<li><strong>October 4:<\/strong> NU7 activated on <strong>public testnet at block 4,465,026<\/strong>, earlier than the originally estimated October 6 date. <a href=\"https:\/\/forum.zcashcommunity.com\/t\/zf-engineering-update-21-september-5-october-2026\/58059\" rel=\"noopener\">Zcash Foundation engineering reporting<\/a> and <a href=\"https:\/\/unchainedcrypto.com\/zcash-activates-nu7-on-public-testnet-opening-a-trial-run-for-25-second-blocks\/\" rel=\"noopener\">Unchained&#8217;s testnet report<\/a> corroborate that event.<\/li>\n<li><strong>October 20:<\/strong> Following the testnet period, the ZIP editors agreed on <strong>mainnet block 3,543,405<\/strong>. The <a href=\"https:\/\/github.com\/zcash\/zips\/pull\/1405\" rel=\"noopener\">pull request proposing the height<\/a> had two approvals but remained open at my cutoff.<\/li>\n<li><strong>October 21:<\/strong> The <a href=\"https:\/\/zips.z.cash\/zip-0259\" rel=\"noopener\">deployment ZIP<\/a> still read <strong>Draft<\/strong> and <strong>Mainnet: TBD<\/strong>. The released <a href=\"https:\/\/github.com\/ZcashFoundation\/zebra\/releases\/tag\/v7.0.0-rc.0\" rel=\"noopener\">Zebra 7.0.0-rc.0<\/a> and <a href=\"https:\/\/github.com\/zakura-core\/zakura\/releases\/tag\/v1.6.0\" rel=\"noopener\">Zakura 1.6.0<\/a> supported the testnet rollout; I had not verified a stable mainnet release incorporating the newly agreed height.<\/li>\n<\/ul>\n<p>That is why \u201cdevelopers agreed on an activation height\u201d is accurate, while \u201cNU7 is live on mainnet\u201d is not. Blocks arrive through mining, not on a calendar alarm. The actual date depends on when the network reaches <strong>3,543,405<\/strong>, and a production rollout still requires compatible software and operator readiness.<\/p>\n<p>I would keep the <a href=\"https:\/\/github.com\/ZcashFoundation\/zebra\/issues\/11674\" rel=\"noopener\">Zebra mainnet readiness tracker<\/a> open. It documents remaining release and synchronization work; the next check is whether those issues are resolved and operators can upgrade safely before the height.<\/p>\n<h2>What do 25-second Zcash blocks actually change?<\/h2>\n<p>The biggest headline feature is straightforward: NU7 changes the <strong>target average interval<\/strong> between blocks from <strong>75 seconds to 25 seconds<\/strong> under <a href=\"https:\/\/zips.z.cash\/zip-0218\" rel=\"noopener\">ZIP 218<\/a>. A block is a batch of confirmed transactions. More frequent blocks should improve how quickly an eligible payment gets its first inclusion opportunity.<\/p>\n<p>But <strong>target block time is not a promise that every block will take exactly 25 seconds<\/strong>. Proof-of-work block discovery varies. A broadcast transaction still has to reach miners, qualify for inclusion and avoid being displaced by more competitive transactions. After inclusion, a recipient decides how many confirmations to require; that policy does not automatically change when a protocol target changes.<\/p>\n<p>For a <strong>hypothetical<\/strong> service waiting for three blocks at the respective target averages, the nominal interval associated with three confirmations changes from about <strong>225 seconds (3 \u00d7 75)<\/strong> to <strong>75 seconds (3 \u00d7 25)<\/strong>. This assumes the same confirmation count, steady average block production and prompt transaction inclusion. It does <strong>not<\/strong> mean that three confirmations provide identical reversal protection under every network or attack scenario, nor does it establish instant or deterministic finality. An exchange can continue requiring its own number of blocks or an elapsed-time policy.<\/p>\n<p>Throughput has constraints too. NU7 specifies a <strong>330-unit shared shielded-action budget per block<\/strong>, alongside individual Orchard, Ironwood and Sapling limits. Under the proposal&#8217;s defined two-action Orchard transaction model, theoretical capacity rises from approximately <strong>2.9 to 6.6 transactions per second<\/strong>\u2014roughly 2.3 times, not automatically three times, and not a universal throughput figure for all payment types. Validation load, propagation, mempool behavior and wallet synchronization still matter. <a href=\"https:\/\/zips.z.cash\/zip-0218\" rel=\"noopener\">ZIP 218<\/a> explains those trade-offs.<\/p>\n<p>The testnet offers useful preliminary evidence, not a performance guarantee. The <a href=\"https:\/\/zakura.com\/nu7\/\" rel=\"noopener\">Zakura dashboard<\/a> was <strong>not providing a fresh live reading<\/strong> at the research cutoff; its stored observation was built <strong>October 20 at 22:13 UTC<\/strong> and displayed a <strong>median 18.0-second gap across its last 300 observed intervals<\/strong>. A median below 25 seconds is not a contradiction: the mean target and the distribution&#8217;s median are different statistics. I would avoid comparing that small testnet window with an unrelated mainnet sample or declaring the post-upgrade experience proven before mainnet runs the same rules.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-7402\" src=\"https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Does-NU7-end-shielded-Zcash-What-Sprout-holders-should-do.png\" alt=\"Does NU7 end shielded Zcash What Sprout holders should do\" width=\"2304\" height=\"1296\" srcset=\"https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Does-NU7-end-shielded-Zcash-What-Sprout-holders-should-do.png 2304w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Does-NU7-end-shielded-Zcash-What-Sprout-holders-should-do-300x169.png 300w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Does-NU7-end-shielded-Zcash-What-Sprout-holders-should-do-1024x576.png 1024w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Does-NU7-end-shielded-Zcash-What-Sprout-holders-should-do-768x432.png 768w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Does-NU7-end-shielded-Zcash-What-Sprout-holders-should-do-1536x864.png 1536w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Does-NU7-end-shielded-Zcash-What-Sprout-holders-should-do-2048x1152.png 2048w\" sizes=\"auto, (max-width: 2304px) 100vw, 2304px\" \/><\/p>\n<h2>Does NU7 end shielded Zcash? What Sprout holders should do<\/h2>\n<p><strong>No. NU7 does not end shielded Zcash.<\/strong> The planned consensus rule disallows <strong>transaction version 4<\/strong>, while <strong>versions 5 and 6<\/strong> remain valid formats. That distinction matters because v4 can contain transparent-only and Sapling activity as well as Sprout transfers. Services still creating v4 transactions need to switch to supported versions. <a href=\"https:\/\/zips.z.cash\/zip-2003\" rel=\"noopener\">ZIP 2003<\/a> and <a href=\"https:\/\/zips.z.cash\/zip-0259\" rel=\"noopener\">ZIP 259<\/a> specify the rule.<\/p>\n<p>Sprout is the exceptional case. It was Zcash&#8217;s original shielded pool, and <strong>its funds can only be spent using the transaction formats being prohibited<\/strong>. At the activation height, any ZEC left in Sprout would therefore lack a supported spending path under NU7 consensus. That is a real access risk, but not a claim that those coins are cryptographically destroyed: the specification explicitly leaves open the theoretical possibility of a future recovery rule, with <strong>no guarantee that one will ever be introduced<\/strong>.<\/p>\n<p>If you have an old <code>zc...<\/code> shielded address, a legacy <code>wallet.dat<\/code> or old <code>zcashd<\/code> records, treat this as a specialized recovery problem. Confirm that you actually control Sprout notes, preserve copies of your wallet material, and follow the <a href=\"https:\/\/zcash.readthedocs.io\/en\/master\/rtd_pages\/sapling_turnstile.html\" rel=\"noopener\">original Zcash Sprout-to-Sapling documentation<\/a> only after checking present-day software compatibility. The historical <a href=\"https:\/\/github.com\/zcash\/zcash\/releases\/tag\/v6.12.0\" rel=\"noopener\">zcashd 6.12.0 release notes<\/a> describe a faster migration tool, but <code>zcashd<\/code> has since been retired as a maintained full-node solution. There is no safe, universal one-click procedure I can endorse for every old wallet. The governing deadline is <strong>block 3,543,405<\/strong>, not a guaranteed wall-clock moment on November 5.<\/p>\n<p>For modern transparent, Sapling, Orchard or other supported holdings, the issue is different: make sure the wallet, custodian or signing service produces supported transactions and supports the upgraded chain. A normal software update and a migration <strong>out of the Sprout pool<\/strong> are not the same operation. If you are comparing wallet custody options, start with the <a href=\"https:\/\/cryptolinks.com\/cryptocurrency-wallet\">Cryptolinks wallet directory<\/a>, but check the actual provider&#8217;s NU7 announcement before taking action.<\/p>\n<h2>How the NU7 fee changes and Network Sustainability Mechanism work<\/h2>\n<p>The <strong>Network Sustainability Mechanism (NSM)<\/strong> is frequently described as a fee burn. That is an incomplete description.<\/p>\n<p>Under <a href=\"https:\/\/zips.z.cash\/zip-0235\" rel=\"noopener\">ZIP 235<\/a>, NU7 removes <strong>60% of the total transaction fees in each block<\/strong> from circulating issuance, rounding down to whole zatoshis. The remaining <strong>40%<\/strong> is available to the miner under the ordinary fee-allocation rules. The removed portion is accounted for in a public consensus-state <strong>NSM Value Balance<\/strong>, not placed into an ordinary discretionary wallet and not permanently destroyed.<\/p>\n<p><strong>Illustrative example:<\/strong> Suppose all transactions in one block pay <strong>0.01 ZEC<\/strong> in aggregate fees. The scheduled accounting would send <strong>0.006 ZEC<\/strong> to the NSM balance and make <strong>0.004 ZEC<\/strong> available to the miner. That splits the fees already paid; it does <strong>not<\/strong> mean a user&#8217;s transaction fee rises by 60%, falls by 60% or becomes free.<\/p>\n<p>Under the <strong>halving-preserving design in <a href=\"https:\/\/zips.z.cash\/zip-0237\" rel=\"noopener\">ZIP 237<\/a><\/strong>, the accumulated balance becomes eligible for automatic additional block-subsidy issuance at a later network height, while the existing halving framework remains in place. The October 20 <a href=\"https:\/\/github.com\/zcash\/zips\/pull\/1405\" rel=\"noopener\">open activation-height proposal<\/a> includes <strong>block 8,939,664<\/strong> as the calculated mainnet NSM reissuance start\u2014projected around <strong>February 2031<\/strong>, subject to finalized deployment rules and the actual chain cadence. This is a consensus rule for future rewards, not a discretionary promise to pay a particular holder.<\/p>\n<p>Shorter blocks also require smaller scheduled rewards <strong>per block<\/strong> to avoid tripling ZEC issued per day. <a href=\"https:\/\/zips.z.cash\/zip-0218\" rel=\"noopener\">ZIP 218<\/a> divides the scheduled per-block subsidy by approximately three and adjusts remaining block-height-based halving intervals to preserve their wall-clock timing. Tiny rounding differences exist, but the consensus design preserves the <strong>21-million-ZEC supply cap<\/strong>. Scheduled issuance, issued\/circulating supply and ZEC temporarily recorded in the NSM balance are different quantities; \u201c60% of fees are permanently burned\u201d and \u201cZcash becomes automatically deflationary\u201d are not conclusions supported by the deployed design.<\/p>\n<p>One more distinction is worth making: Zcash also has a <strong>separate conventional-wallet-fee proposal, <a href=\"https:\/\/zips.z.cash\/zip-2009\" rel=\"noopener\">ZIP 2009<\/a><\/strong>, reducing the <em>marginal fee recommendation<\/em> from 5,000 to 1,000 zatoshis per logical action. The Zebra release candidate schedules that mainnet policy transition at <strong>block 3,590,000<\/strong>, after the proposed NU7 activation height. That is <strong>not the same change<\/strong> as the NSM&#8217;s 60\/40 fee allocation and should not be presented as proof NU7 itself cuts every user&#8217;s fees.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-7405\" src=\"https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-before-and-after-NU7-the-practical-changes.png\" alt=\"Zcash before and after NU7 the practical changes\" width=\"2304\" height=\"1296\" srcset=\"https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-before-and-after-NU7-the-practical-changes.png 2304w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-before-and-after-NU7-the-practical-changes-300x169.png 300w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-before-and-after-NU7-the-practical-changes-1024x576.png 1024w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-before-and-after-NU7-the-practical-changes-768x432.png 768w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-before-and-after-NU7-the-practical-changes-1536x864.png 1536w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-before-and-after-NU7-the-practical-changes-2048x1152.png 2048w\" sizes=\"auto, (max-width: 2304px) 100vw, 2304px\" \/><\/p>\n<h2>Zcash before and after NU7: the practical changes<\/h2>\n<table>\n<thead>\n<tr>\n<th>Topic<\/th>\n<th>Before NU7<\/th>\n<th>Scheduled change<\/th>\n<th>Practical implication<\/th>\n<th>Important limitation<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Block production<\/td>\n<td>75-second target<\/td>\n<td>25-second target<\/td>\n<td>More frequent inclusion opportunities<\/td>\n<td>Individual gaps and settlement policies still vary<\/td>\n<\/tr>\n<tr>\n<td>Confirmation experience<\/td>\n<td>Based on existing block cadence<\/td>\n<td>Shorter nominal time for a fixed block count<\/td>\n<td>Some recipients may credit sooner<\/td>\n<td>Same confirmation count is not a universal security equivalence<\/td>\n<\/tr>\n<tr>\n<td>Transaction versions<\/td>\n<td>v4, v5 and v6 can be valid under existing rules<\/td>\n<td>v4 prohibited; v5\/v6 remain<\/td>\n<td>Transaction builders must use supported versions<\/td>\n<td>Even v5\/v6 signatures may need to be recreated across the branch change<\/td>\n<\/tr>\n<tr>\n<td>Legacy Sprout balances<\/td>\n<td>Spending path exists through v4-compatible tooling<\/td>\n<td>No supported spending path under NU7 rules<\/td>\n<td>Owners must address legacy balances before activation<\/td>\n<td>No guaranteed later recovery<\/td>\n<\/tr>\n<tr>\n<td>Collected transaction fees<\/td>\n<td>Normally available to miner under pre-NU7 rules<\/td>\n<td>60% NSM; 40% miner<\/td>\n<td>Part of fees may support future mining rewards<\/td>\n<td>Not a 60% change to fees quoted to users<\/td>\n<\/tr>\n<tr>\n<td>Issuance and halvings<\/td>\n<td>75-second block-based schedule<\/td>\n<td>Lower per-block subsidy; intervals rescaled<\/td>\n<td>Maintains roughly the same issuance pace by time<\/td>\n<td>Small rounding effects; reserve reissuance starts later<\/td>\n<\/tr>\n<tr>\n<td>Node readiness<\/td>\n<td>Pre-NU7 software follows existing consensus<\/td>\n<td>Operators need confirmed compatible mainnet versions<\/td>\n<td>Reduce the risk of a consensus split<\/td>\n<td>Testnet releases alone do not establish mainnet readiness<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Who actually needs to do something?<\/h3>\n<table>\n<thead>\n<tr>\n<th>Reader<\/th>\n<th>Action<\/th>\n<th>Where to check<\/th>\n<th>When<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Ordinary ZEC holder<\/td>\n<td>Usually no special pool migration; confirm wallet\/custodian support<\/td>\n<td>Wallet provider notices; <a href=\"https:\/\/z.cash\/upgrade\/nu7\/\">Zcash upgrade overview<\/a><\/td>\n<td>Before proposed mainnet height<\/td>\n<\/tr>\n<tr>\n<td>Sprout holder<\/td>\n<td><strong>Urgently assess and complete a compatible exit from Sprout<\/strong><\/td>\n<td><a href=\"https:\/\/zcash.readthedocs.io\/en\/master\/rtd_pages\/sapling_turnstile.html\" rel=\"noopener\">Legacy migration guide<\/a> and official provider\/support channels<\/td>\n<td><strong>Before block 3,543,405<\/strong><\/td>\n<\/tr>\n<tr>\n<td>Miner or mining-pool operator<\/td>\n<td>Confirm the pool&#8217;s consensus node and mining templates support NU7<\/td>\n<td><a href=\"https:\/\/github.com\/ZcashFoundation\/zebra\/releases\" rel=\"noopener\">Zebra release notes<\/a> and <a href=\"https:\/\/github.com\/ZcashFoundation\/zebra\/issues\/11674\" rel=\"noopener\">readiness tracker<\/a><\/td>\n<td>Ahead of activation<\/td>\n<\/tr>\n<tr>\n<td>Full-node\/indexer operator<\/td>\n<td>Wait for and install a verified mainnet-compatible release; check state and monitoring<\/td>\n<td><a href=\"https:\/\/github.com\/ZcashFoundation\/zebra\/issues\/11674\" rel=\"noopener\">Zebra tracker<\/a>; <a href=\"https:\/\/github.com\/zakura-core\/zakura\/releases\" rel=\"noopener\">Zakura releases<\/a><\/td>\n<td>Before activation, with backups<\/td>\n<\/tr>\n<tr>\n<td>Wallet developer or exchange<\/td>\n<td>Check v4 creation, signing branch IDs, confirmation rules, deposits and indexing<\/td>\n<td><a href=\"https:\/\/zips.z.cash\/zip-0259\" rel=\"noopener\">ZIP 259<\/a> and provider operational notices<\/td>\n<td>Complete testing before activation<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-7403\" src=\"https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/What-I-would-watch-next-3.png\" alt=\"What I would watch next (3)\" width=\"2304\" height=\"1296\" srcset=\"https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/What-I-would-watch-next-3.png 2304w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/What-I-would-watch-next-3-300x169.png 300w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/What-I-would-watch-next-3-1024x576.png 1024w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/What-I-would-watch-next-3-768x432.png 768w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/What-I-would-watch-next-3-1536x864.png 1536w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/What-I-would-watch-next-3-2048x1152.png 2048w\" sizes=\"auto, (max-width: 2304px) 100vw, 2304px\" \/><\/h2>\n<h2>What I would watch next<\/h2>\n<p>A date on a roadmap can help traders focus. A stable network after activation is stronger evidence of execution.<\/p>\n<p>Before NU7 activates, I would check whether the exact height is merged into <strong>ZIP 259<\/strong>, whether Zebra and Zakura both publish <strong>mainnet-ready releases<\/strong> containing it, and whether exchanges, miners, indexers and wallets confirm their rollout plans. I would also watch the open Zebra synchronization and release work, rather than treating a successful public testnet start as the end of testing.<\/p>\n<p>After the network reaches <strong>block 3,543,405<\/strong>, the measurements that matter are more concrete: whether upgraded nodes agree on the chain, the distribution of block intervals over a substantial mainnet sample, stale blocks and reorganizations, wallet-sync performance, and actual confirmation experience at clearly stated recipient policies. The NSM balance and fee split should also match what the new consensus rules prescribe. A single favorable testnet median or a few unusually fast blocks cannot settle those questions.<\/p>\n<p>The distinction I would focus on is this: <strong>NU7 can make Zcash more responsive without making every transfer instantly final, and it can recycle fees without permanently burning them.<\/strong> For most holders, the event is primarily a compatibility milestone. For anyone still using Sprout, it is a time-sensitive access issue. Those are more useful conclusions than trying to turn today&#8217;s price move into a guarantee about tomorrow.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-7400\" src=\"https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-NU7-frequently-asked-questions.png\" alt=\"Zcash NU7 frequently asked questions.\" width=\"2304\" height=\"1296\" srcset=\"https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-NU7-frequently-asked-questions.png 2304w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-NU7-frequently-asked-questions-300x169.png 300w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-NU7-frequently-asked-questions-1024x576.png 1024w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-NU7-frequently-asked-questions-768x432.png 768w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-NU7-frequently-asked-questions-1536x864.png 1536w, https:\/\/cryptolinks.com\/news\/wp-content\/uploads\/2026\/10\/Zcash-NU7-frequently-asked-questions-2048x1152.png 2048w\" sizes=\"auto, (max-width: 2304px) 100vw, 2304px\" \/><\/p>\n<h2>Zcash NU7: frequently asked questions<\/h2>\n<h3>When will Zcash NU7 activate?<\/h3>\n<p>Developers agreed to target <strong>mainnet block 3,543,405<\/strong>, estimated around <strong>November 5, 2026<\/strong>. At the October 21, 08:55 UTC research cutoff, the height still needed to be incorporated into the final deployment specification and compatible mainnet releases; activation had <strong>not<\/strong> happened.<\/p>\n<h3>Will NU7 make every Zcash payment three times faster?<\/h3>\n<p>No. It changes the <strong>target block spacing<\/strong> from 75 to 25 seconds, which can reduce waiting time for confirmations. Real confirmation intervals, transaction inclusion, exchange policies and proof-of-work reorganization risks remain variable.<\/p>\n<h3>Will I lose ZEC if I use a shielded wallet?<\/h3>\n<p><strong>Not merely because it is shielded.<\/strong> The exceptional risk applies to <strong>funds left in Sprout<\/strong>, which depend on transactions NU7 would prohibit. Other supported pools and v5\/v6 transaction formats are not being retired by that rule.<\/p>\n<h3>Are 60% of Zcash fees burned forever?<\/h3>\n<p>No. NU7&#8217;s planned rules remove that portion of <strong>aggregate block fees<\/strong> from circulation and account for it in the NSM balance, from which value can later be reissued automatically through mining subsidies under the specified schedule.<\/p>\n<h3>Does the upgrade change Zcash&#8217;s 21 million maximum supply?<\/h3>\n<p>No. The design preserves the maximum cap and adapts per-block rewards and halving heights to the shorter target interval, with minor rounding effects.<\/p>\n<p><strong>Further reading:<\/strong> <a href=\"https:\/\/cryptolinks.com\/\">Cryptolinks homepage<\/a> \u00b7 <a href=\"https:\/\/cryptolinks.com\/news\/\">Latest cryptocurrency news<\/a> \u00b7 <a href=\"https:\/\/cryptolinks.com\/2159\/zcash\">Zcash guide<\/a> \u00b7 <a href=\"https:\/\/cryptolinks.com\/privacy-coins\">Privacy coins and tokens<\/a> \u00b7 <a href=\"https:\/\/cryptolinks.com\/news\/zcash-price-privacy-coin-rally\">Previous Zcash rally coverage<\/a> \u00b7 <a href=\"https:\/\/cryptolinks.com\/news\/zcash-zec-drama-in-2026\">Zcash governance coverage<\/a>.<\/p>\n<p><em>Cryptolinks editorial disclosure: This article is informational reporting and analysis, not personalized investment advice. Crypto prices, software-release status and network measurements change. Readers should verify current official notices before moving funds or upgrading infrastructure. No direct developer interviews, personal ZEC trades or independently operated test nodes are claimed here.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>ZEC gained 12.86% in a checked 24-hour snapshot as Zcash developers agreed on NU7 block 3,543,405. Here\u2019s what the November target, Sprout sunset, faster blocks and fee recycling mean.<\/p>\n","protected":false},"author":1,"featured_media":7401,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[71,478,575,572,571,573,574,569,570],"class_list":["post-7398","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-blockchain","tag-crypto-markets","tag-network-sustainability-mechanism","tag-network-upgrades","tag-nu7","tag-privacy-coins","tag-sprout","tag-zcash","tag-zec"],"_links":{"self":[{"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/posts\/7398","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/comments?post=7398"}],"version-history":[{"count":2,"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/posts\/7398\/revisions"}],"predecessor-version":[{"id":7406,"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/posts\/7398\/revisions\/7406"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/media\/7401"}],"wp:attachment":[{"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/media?parent=7398"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/categories?post=7398"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cryptolinks.com\/news\/wp-json\/wp\/v2\/tags?post=7398"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}