• ZIP 218 specifies a change in block target spacing from 75 seconds to 25 seconds in NU7.
• CoinDesk reports NU7 is live on mainnet; ZIP 259 sets activation by block height (mainnet 3,543,405), which this desk has not checked against the chain.
• By arithmetic, the expected wait for any fixed number of confirmations falls to one third.
• NU7 is a consensus-parameter upgrade; neither ZIP addresses exchange, processor or regulatory treatment of privacy coins.
• For merchants, the practical step is to re-set confirmation policy deliberately rather than assume the old count still gives the same assurance.

Zcash's NU7 network upgrade changes how fast the network settles, not how it handles privacy or compliance. CoinDesk reports that NU7 has gone live on mainnet. The governing specification, ZIP 218, moves block target spacing from 75 seconds to 25 seconds. For anyone treating Zcash as payment plumbing, the question is whether confirmation speed was the real obstacle to adoption.

What the specification changes

ZIP 218, titled 25-second Block Target Spacing, specifies a change in block target spacing from 75 seconds to 25 seconds in NU7. The proposal also lengthens the difficulty averaging window from 17 to 102 blocks, triples default transaction expiry from 40 to 120 blocks, and raises the maximum reorganisation length to at least 600 blocks. ZIP 259, which deploys NU7, sets activation by block height, not calendar date: 3,543,405 on mainnet and 4,465,026 on testnet. Both documents list Proposed status.

What is confirmed about mainnet

CoinDesk's report of 6 November 2026 says NU7 has gone live on mainnet. Because ZIP 259 defines activation by block height, not by date, this desk has not independently compared the current chain height with 3,543,405. The live status therefore rests on CoinDesk's reporting and should be read as reported rather than verified on-chain. Operators who depend on it can compare a block explorer's current height with the ZIP 259 value.

Why faster blocks matter for payments

With expected spacing cut to one third, the average wait for any fixed number of confirmations falls by the same proportion. As an illustration, a merchant requiring six confirmations would wait roughly 450 seconds at the old target and 150 seconds at the new one. That is a checkout-friction gain. It does not change the merchant's risk policy, since the right confirmation count still depends on the value at stake and on how the chain behaves under the new interval.

What speed does not change

NU7 is a package of consensus-parameter changes. Neither ZIP 218 nor ZIP 259 addresses how exchanges, payment processors or regulators treat privacy-focused assets, and those treatments are what constrain merchant adoption. ZIP 259 also bundles monetary-design items, including ZIP 235, which removes 60 percent of transaction fees from circulation, and ZIP 237, the Network Sustainability Mechanism. Those alter issuance and fee flows, not merchant discount economics, and the documents reviewed here describe no pricing effect.

What to watch next

The measurable follow-ups are on-chain and operational. Watch whether realised block intervals settle near 25 seconds, whether shorter intervals raise the rate of orphaned blocks or strain node synchronisation, and whether wallets and payment processors revise their confirmation policies. Because the ZIPs specify a longer minimum reorganisation limit, reorg depth in blocks is also worth tracking. Adoption data from processors would show whether speed changed behaviour.