Zcash Opens NU7.1 Miner Signal as Zebra 7.2 Beta Enters Testing

BTCLiveETHLiveSOLLiveXRPLiveBNBLiveDOGELiveADALiveAVAXLive
CHARTING PARTNERTradingViewAdvanced charts, indicators and market tools.OPEN CHARTS →
Start with today’s trader mapBefore you leave: see the cross-asset levels, confirmations, invalidations and catalysts NetNapz is tracking for the next session.DAILY TRADER BRIEF →STRATEGY DESK →

ZCASH · NU7.1 GOVERNANCE · miner-sentiment pilot starts at block 3,591,200 · Zebra 7.2.0-beta.1 in testing

Published 5 October 2026 · Materially updated 19 November 2026

Zcash Opens NU7.1 Miner Signal as Zebra 7.2 Beta Enters Testing

Editorial illustration of the Zcash symbol, privacy shield and blockchain blocks accelerating from 75 seconds to 25 seconds

NetNapz editorial illustration. Illustrative image; it does not depict a live network event.

The Zcash Foundation has opened a first on-chain miner-sentiment pilot for NU7.1 alongside its advisory-panel poll. Separately, Zebra 7.2.0-beta.1 adds mining, propagation, synchronization and opt-in pruning changes for controlled testing; production nodes should remain on stable 7.1.0.

19 November update — first miner-sentiment pilot starts at block 3,591,200

The Zcash Foundation’s 19 November announcement opens an on-chain miner-sentiment pilot alongside the NU7.1 Zcash Community Advisory Panel poll. Miners and pools can place a short ballot in each block’s coinbase from block 3,591,200 through 3,629,650, inclusive. The Foundation estimates a window from 20 November at 00:00 UTC to 1 December at 02:59 UTC, but the block heights—not the calendar estimates—define the actual window.

Each block carries its own public ballot, and a miner or pool can change its selection between blocks. The Foundation’s forum notice links the technical definition, ballot builder and public tally. This measures ballots contained in blocks; it is not a one-person-one-vote poll and should not be described as a direct hashrate referendum without a separate methodology.

The pilot asks the same five questions as the advisory-panel poll: whether to wind down Zcash Community Grants; create a Future Dev and Legal Defense Fund; adopt the Zcash Adoption Pool proposal; retain current grant funding and operations; and, subject to safe implementation, reduce the target block time from 25 seconds to 20 seconds. The Foundation’s ZCAP notice explicitly describes that poll as advisory and says the parallel groups’ results will be compared after voting.

Status and verification: NetNapz verified the Foundation announcement, the stated height window and the five questions. At this check the miner window had not yet reached its opening height. No result, participation rate, protocol change, funding transfer or 20-second block schedule is established.

NetNapz assessment: the pilot adds a transparent signal from operators who build blocks, but it does not decide NU7.1 by itself. The useful follow-up is participation across independently identified pools, the final ballot distribution after the end height and how those results compare with the other advisory groups. Token price or a single pool’s position would not substitute for the published tally.

19 November update — miners and pools get a 7.2 beta; stable 7.1 remains the production default

The Zcash Foundation’s 19 November release introduces Zebra 7.2.0-beta.1 for miners, mining pools and the node operators supporting them. The Foundation asks those operators to run the beta beside Zebra 7.1.0 and compare real workloads. It explicitly says production nodes should stay on stable 7.1.0.

The beta aims to deliver block templates sooner, reduce repeated verification, relay blocks and mempool transactions faster, and use compact block relay between supporting peers. It also adds opt-in pruning. The Foundation reports one measured mainnet database falling from about 282 GB to about 15 GB, but that observation is not a universal disk guarantee and operators still need additional space for initial synchronization and compaction.

Pruning retains at least 10,000 recent blocks plus the state needed to validate, mine and submit blocks. It is off by default, cannot be used with a zcashd sidecar and places pruned data in a separate database directory. The release warns operators to stop the node, back up data and follow the migration guide before moving an archive.

The separate fast-tree-sync option uses peer-supplied note-commitment roots checked against Zebra checkpoints. The Foundation describes it as a one-way database change that stable 7.1.0 and direct-database tools cannot read. Nodes serving wallets should leave it off because tree-state requests can be unavailable at fast-synced heights. A node that enables pruning or fast tree sync cannot simply switch its database back to 7.1.0.

The beta upgrades compatible 7.0.0 or 7.1.0 state to format 29.2.0 in place without a resync, according to the release. Its container tag is zfnd/zebra:7.2.0-beta.1 or edge; latest remains on 7.1.0. Both builds retain an end-of-support window around 10 December, so the test does not remove the need for a later supported release.

Status and verification: NetNapz verified the Foundation’s beta announcement and operator guidance. It did not run the software, benchmark mining latency, reproduce the reported pruning measurement or verify pool adoption.

NetNapz assessment: the beta targets operational bottlenecks made more important by NU7’s 25-second block target, but its value depends on controlled miner and pool results. The Foundation’s instruction to keep production on 7.1.0 is the decision-useful boundary. A beta tag does not establish network-wide performance gains, reduced mining centralization or a ZEC price effect.

18 November update — Zebra 7.1.0 closes sync and memory-exhaustion paths

The Zcash Foundation's 16 November release says Zebra 7.1.0 fixes ten security advisories. Most involved ways a network peer could stall initial synchronization or consume excessive memory; others affected already-synchronized nodes, wallet-facing address-balance requests and mempool verification work.

Among the confirmed fixes, forged blocks can no longer halt synchronization at the checkpoint handoff, rewritten coinbase heights are rejected before they can poison sync queues, and recent-block indexes are shared and bounded to reduce memory exhaustion from blocks dense with transparent outputs. Concurrent getaddressbalance or lightwalletd requests no longer copy all recent block data, closing another memory-exhaustion path.

The Foundation advises miners, mining pools, node operators, exchanges, wallet services and lightwalletd operators to upgrade. It says ordinary ZEC holders and wallet users do not need to act. Moving from stable Zebra 7.0.0 to 7.1.0 requires no database migration or resync, although Rust library users face breaking API changes and operators using the removed experimental Elasticsearch feature must change configuration.

The release adds sync-restart, block-error and memory metrics, retries peer discovery when a node loses outbound peers, and tightens limits around the health endpoint and peer requests. The Foundation says 7.1.0 is supported until around 10 December 2026, after which its built-in end-of-support behavior will stop the node; operators therefore still need a subsequent upgrade plan.

NetNapz assessment: the fixes materially strengthen the production client after NU7, but publication of patches does not prove universal operator adoption. The practical follow-up is the proportion of miners, exchanges, wallets and public services running a supported build, plus any post-release incident reports. No ZEC price claim or chain-wide exploit loss is inferred from the advisories.

Evidence checked: 18 November 2026. The Foundation's release and its linked advisory descriptions were checked; this report does not claim independent reproduction of the vulnerabilities.

6 November update — activation height crossed

At the 6 November check, ZecBlock marked block 3,543,405 canonical, while its upgrade tracker listed NU7 as active and showed a later tip at 3,543,576. The official ZIP 259 deployment specification assigns NU7 to that mainnet height. Together, the specified rule and observed chain support reporting activation, replacing this article’s earlier pending-height status.

The Foundation’s stable-release explanation sets a 25-second block target, with per-block subsidy adjustments preserving the time-based issuance schedule. A target is not a measured post-upgrade average. NetNapz has not independently measured block intervals, audited chain continuity or verified every wallet, exchange and mining pool’s compatibility.

NetNapz assessment: the next reporting test is sustained operation and service compatibility, rather than another countdown. An explorer’s canonical-chain observation is useful evidence of the milestone, but cannot establish that all infrastructure providers have resumed deposits, withdrawals or normal operation.

Evidence checked: 6 November 2026, 04:42 UTC. No exact activation timestamp or ZEC price reaction is asserted. Earlier sections below preserve the history and evidence available on their stated dates.

30 October update — Zebra 7.1.0-alpha.0 adds mining-pool interfaces

The Zcash Foundation published Zebra 7.1.0-alpha.0 on 30 October 2026 from its next branch. The Foundation labels it a pre-release for testing rather than the stable operator default. Stable Zebra 7.0.0 remains the rollback baseline described below.

The alpha removes timer waits between new transactions or blocks arriving and miners receiving updated work. It also adds legacy JSON-RPC batch support for pool software, optional ZMQ hashblock notifications, the preciousblock RPC and mining metrics. These are software capabilities, not evidence that mining pools have adopted the build or that block propagation has improved across the live network.

The release retains Zebra 7.0.0’s state format, allowing testers to switch back without a resync, but it introduces three stricter configuration checks. Its container tags are 7.1.0-alpha.0 and edge, rather than latest, and its Rust crates are not published to crates.io.

NetNapz assessment: the build is a meaningful readiness step for miners and pools, but its alpha status limits the conclusion. Operators should treat it as a controlled test candidate and keep stable 7.0.0 available; production adoption, performance gains and NU7 activation outcomes require separate evidence.

22 October update — stable Zebra 7.0.0 released

The Zcash Foundation published stable Zebra 7.0.0 on 22 October 2026. The signed release sets NU7 mainnet activation at block 3,543,405 and says mainnet nodes must upgrade before that height to remain on the consensus chain. Publication converts the earlier release expectation into a verified software milestone; it does not mean NU7 has already activated.

The stable release moves Zebra’s state database from format v28 to v29. The migration does not require a resync, but Zebra 6.x cannot read the migrated v29 database. The Foundation advises operators to back up the state/v28 directory before upgrading if they may need to roll back. Operators must also review breaking configuration, RPC and direct-database-reader changes described in the release-candidate notes.

The release adds the agreed mainnet activation height and protocol version 170190, updates the embedded compatibility sidecar for NU7, and includes peer, synchronization and denial-of-service hardening. The Foundation says this build has an eight-week support window rather than the usual 12 weeks, so upgrade planning should account for its shorter end-of-support period.

NetNapz assessment: stable binaries materially improve operator readiness, but activation still depends on the chain reaching block 3,543,405 and on miners, nodes, wallets, indexers and other infrastructure upgrading successfully. A tagged release is not evidence that every downstream integration is ready.

21 October update — activation height agreed; stable release was pending

Developers have agreed on mainnet block 3,543,405 as the NU7 activation target. The official ZIP repository change, opened 20 October, says the height was agreed at a ZIP editor meeting and records two approvals. At this check it remained open, with final specification changes still required alongside the merge; the published ZIP 259 still showed Mainnet: TBD. Our earlier wording that no height had been selected was therefore incomplete.

The community timeline points to approximately 5 November 2026. This is an estimate, not a fixed activation time: the network must reach the specified block. The Zebra mainnet-readiness tracker also records the agreed height, with an estimate near the start of 6 November UTC based on the 20 October chain tip. Calendar estimates can shift with actual block production.

Community source and thanks: Rogue Infrastructure Group (@RogueInfra) drew our attention to the height and said Zebra 7.0.0 is expected on 22 October 2026, allowing operators time to upgrade before older versions stop. We appreciate the correction. The release date is attributed to their update supplied to NetNapz; we have not independently confirmed that date in an official release announcement.

The Foundation’s 21 October engineering update says sync fixes are merged for the next release, likely Zebra 7.0.0, and warns that Zebra 6.4.x stops itself around 2 November. At the 21 October check, the official release list still showed 7.0.0-rc.0 as the latest release and the 7.0.0 publication checklist remained open. Stable 7.0.0 was subsequently published on 22 October, as described above.

NetNapz assessment: selection of a block height makes the rollout plan more concrete. Operators should follow the official release and upgrade instructions as they are published; an expected release date does not establish that a stable mainnet-compatible binary is already available.

What is verified

The 2 October Zcash Foundation release says Zebra 7.0.0-rc.0 is the first release candidate for NU7 and will activate on public testnet at block 4,465,026, expected around 6 October 2026. Testnet operators must upgrade to remain on the NU7 chain. That announcement concerned testnet and did not include a mainnet height; it should not be read as current advice to defer mainnet preparations now that a target height has been agreed.

The upgrade’s draft deployment specification, ZIP 259, corroborates the intended consensus scope: 25-second target blocks, shielded-action limits, a Network Sustainability Mechanism and retirement of version-4 transactions. The specification remains draft. As checked on 19 October, it specifies minimum network protocol versions of 170180 for testnet and 170190 for mainnet; remaining open items include assigning the mainnet activation height, calculating the associated mainnet NSM reissuance height, and adding reference implementations and test vectors for the NSM Value Balance. That distinction matters: code reaching public testnet is a real engineering milestone, but it is not proof that mainnet deployment is complete or risk-free.

Why faster blocks matter

NU7 targets one block every 25 seconds instead of 75. If the network behaves as designed, first-confirmation latency should fall by roughly two-thirds. That can improve the user experience for point-of-sale payments, exchange deposits and cross-chain systems that wait for a fixed number of confirmations.

The design does not triple daily ZEC issuance. The Foundation says remaining halving intervals are lengthened in block-count terms and each scheduled block reward is divided by three, preserving the time-based issuance schedule and the 21 million supply cap. Faster blocks also require tighter resource controls: NU7 caps shielded actions per block and applies a shared budget across pools to prevent higher block frequency from becoming an easy denial-of-service vector.

The new security-budget mechanism

The proposed Network Sustainability Mechanism changes how transaction fees are handled. Under the release candidate, miners retain 40% of each block’s fees while 60% moves into a transparent consensus reserve. A small portion of that reserve is intended to be reissued in future block rewards, beginning under a later schedule.

The economic aim is to smooth the transition from subsidy-funded security toward fee-funded security as issuance declines. It does not create free yield or expand the maximum ZEC supply: the reserve consists of value previously removed from circulation, and later reissuance is bounded by consensus rules. Whether it materially strengthens the mining security budget will depend on real transaction demand, fee generation and the final mainnet parameters.

Operational risks are still live

Consensus upgrades can split networks if miners, nodes, wallets or infrastructure providers run incompatible software. Zebra 7.0.0-rc.0 also changes its state database to format v29 and introduces breaking API changes for components that read Zebra state directly. Testnet deployment is therefore the correct place to detect compatibility, synchronization and block-template problems before mainnet.

Recent context reinforces the need for caution. The Foundation issued Zebra 6.4.2 on 25 September as an emergency fix for a remotely triggerable crash. That incident is separate from NU7, but it shows why release-candidate testing, multi-client review and operator readiness matter more than headline throughput claims.

NetNapz assessment after activation and the security release

NU7 has moved beyond a release-readiness story: the observed mainnet chain crossed the specified activation height, and Zebra 7.1.0 now addresses ten disclosed node-security issues. The operational question is whether infrastructure operators adopt supported builds and users can transact reliably under the new rules. Faster target blocks and published patches alone do not prove greater economic usage, sustained throughput, universal service readiness or stronger demand for ZEC.

The 30 October alpha remains a testing release, as its dated notes above explain. An activation outcome does not turn an alpha into a stable recommendation. Independent operator reports, wallet compatibility and post-upgrade measurements should determine follow-up coverage.

What to watch next

  • Post-upgrade chain continuity and measured block intervals over a stated observation window.
  • Wallet, mining-pool, exchange and indexer compatibility under the active consensus rules.
  • Operator reports of synchronization, transaction-format or database issues.
  • Any official stable-client follow-up, distinguished from alpha testing releases.

Primary sources: Zcash Foundation Zebra 7.1.0 security release, 16 November 2026; Zcash Foundation release, 2 October 2026; ZIP 259 draft deployment specification; Zcash NU7 upgrade status; Zebra 6.4.2 security release, 25 September 2026; Zcash Foundation engineering update, 21 October 2026.

Material update checked 18 November 2026: Zebra 7.1.0 was verified as a stable security release fixing ten advisories; operators were advised to upgrade, while ordinary ZEC holders need no action. Earlier material update checked 6 November 2026: the specified activation height was crossed on the observed mainnet chain; ZecBlock marked NU7 active. Earlier pre-activation planning language above is historical. Earlier material update checked 4 November 2026: Zebra 7.1.0-alpha.0 was verified as a testing release with mining-pool interfaces; stable 7.0.0 remains the production baseline. Earlier material update checked 22 October 2026: stable Zebra 7.0.0 was published with NU7 mainnet activation at block 3,543,405, replacing the prior expected-release wording. The original 5 October publication date is retained; the 21 October correction and attribution to Rogue Infrastructure Group remain documented above.

This article reports a dated protocol milestone and is not investment advice. No price forecast or execution level is provided.

Scroll to Top