SPONSORED PARTNERMEXCExplore global spot and futures marketsEXPLORE MEXC →
CHARTING PARTNERTradingViewAdvanced charts, indicators and market analysisOPEN CHARTS →
TRADING PARTNERGMX via NetNapz TradeTrade decentralised perpetual marketsSTART TRADING →ZCASH · PROTOCOL · 2 OCTOBER 2026
Zcash NU7 Reaches Public Testnet With 25-Second Blocks—but Mainnet Is Not Scheduled
NetNapz editorial illustration. Illustrative image; it does not depict a live network event.
Zcash Foundation released Zebra 7.0.0-rc.0 on 2 October, setting NU7 to activate on the public testnet around 6 October. The release candidate cuts target block spacing from 75 seconds to 25 seconds, introduces a fee-funded reserve and applies shielded-action limits. The important qualifier: no mainnet activation height has been set.
What is verified
The 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. Mainnet operators do not yet need to act because this is not a stable release and there is no mainnet activation height.
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 is still marked draft and lists unresolved items including mainnet activation height, protocol versions and reference test vectors. 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
Near-term view: cautiously constructive on protocol execution, neutral on ZEC price implications. Reaching public testnet with an explicit activation height is stronger evidence than a roadmap promise. Three-times-faster target blocks and bounded shielded capacity could improve payments and wallet usability if the testnet remains stable.
The bear case is that consensus, mining or wallet integrations expose defects, forcing delays or scope reductions. The bull case requires clean activation around block 4,465,026, broad operator compatibility, stable shielded synchronization and a subsequent mainnet proposal with complete test vectors and clear activation parameters.
Confirmation: sustained testnet finality, no material chain split, functioning wallet and indexer integrations, and a stable Zebra release followed by a dated mainnet plan. Invalidation: repeated activation failures, emergency rollbacks, unresolved database or mining-template problems, or a mainnet schedule announced before the draft specification’s open issues are closed.
For ZEC holders, protocol progress does not automatically create token demand. The value-accrual test is whether faster private payments lead to more genuine shielded usage and fees without weakening reliability or privacy. A short-lived price reaction would not answer that question.
What to watch next
- Public-testnet activation at height 4,465,026, expected around 6 October.
- Operator reports covering chain continuity, mining templates and database migration.
- Wallet, explorer and indexer compatibility with Zebra’s v29 state format and API changes.
- Finalization of ZIP 259, including mainnet height, protocol version and test vectors.
- A stable Zebra release and a separately announced mainnet activation plan.
Primary sources: Zcash Foundation release, 2 October 2026; ZIP 259 draft deployment specification; Zcash NU7 upgrade status; Zebra 6.4.2 security release, 25 September 2026.
This article reports a dated protocol milestone and is not investment advice. No price forecast or execution level is provided.