ZEC View
English简体中文

Zcash protocol upgrades

Zcash NU7 Upgrade Tracker

Document status below reflects the official sources at the stated check time, not a live feed. Proposed is a document status, not confirmation of mainnet activation. Repository inclusion, advisory voting and actual chain activation are separate facts.

NU7 mainnet: active (source-reported)

Source nodes report the NU7 mainnet branch active at and above block 3,543,405. ZIP 259 remains Proposed as a document; document status is separate from observed network activation. This site did not independently validate a full node.

Current next halving height
Block 6,132,390
Estimated halving time (UTC)

Estimate uses the dated block observation and the 25-second target spacing, not a guaranteed calendar date. Before activation, remaining time is split into 75-second and 25-second segments. Faster blocks rescale the height, not the intended halving cadence.

Observed mainnet height: 3,546,316 · Block timestamp (UTC):

Network observed (UTC): · Evidence checked (UTC):

Consensus branch ID: 77190ad9 · Observed block hash: 0000000000f2c8ab4d14a1b4a4fcdf6522a247659b9a2ddc6cf9068eb7450f03

Mainnet node dashboard evidence · Corroborating network observation · ZIP 259 · ZIP 218 · ZIP 237

Historical reference — pre-NU7 75-second schedule

The previous reference model placed the third halving at block 4,406,400. That is not the current next-halving height after NU7. With activation A = 3,543,405, ZIP 218 gives H3 = 13,219,200 − 2A = 6,132,390 and later intervals of 5,040,000 blocks.

Scheduled subsidy changes from 1.56250000 ZEC to 0.52083333 ZEC at activation, then to 0.26041666 ZEC at the third halving. NSM reissuance starts at block 8,939,664; it is separate from a halving and does not raise the supply cap. Additional NSM subsidy needs value-balance state and is not included in this scheduled-issuance calculator.

Evidence snapshot SHA-256: f5dc436649f99b26073aa93185da23bd3a74e96bbe02dfcdd3629c6734f2b665

Source-backed ZIP documents

3 source documents

ZIP 259: Deployment of the NU7 Network Upgrade

Document: Proposed · Mainnet activation: active according to the dated node evidence above

Created: 2026-09-15. License stated in document: MIT.

Document checked (UTC): · Source document, not proof of chain activation.

Official document · Read immutable checked source

Version and SHA-256

Commit: 4699a8d518c4c409db3f486c7917e649369c41c9
SHA-256: 75061c436cd9cd65f03842af75377f87608f4157b43b72c475e5276b7cdeebdd

ZIP 218: 25-second Block Target Spacing

Document: Proposed · Mainnet activation: active according to the dated node evidence above

Created: 2026-03-13. License stated in document: MIT.

Document checked (UTC): · Source document, not proof of chain activation.

Official document · Read immutable checked source

Version and SHA-256

Commit: 4699a8d518c4c409db3f486c7917e649369c41c9
SHA-256: 14369354b0ddd16bb1a1a8a309291244cca8dfd8b4b2b7435ef7d94f58f00780

ZIP 237: Network Sustainability Mechanism: Halving-Preserving Issuance

Document: Proposed · Mainnet activation: active according to the dated node evidence above

Created: 2026-08-19. License stated in document: BSD-2-Clause.

Document checked (UTC): · Source document, not proof of chain activation.

Official document · Read immutable checked source

Version and SHA-256

Commit: 4699a8d518c4c409db3f486c7917e649369c41c9
SHA-256: 5b62469f703bd29bf271f8c3d692b77bd9376b4136d7b398e5f369d6a9d3a1e6

Separate advisory poll records

February 2026 ZCAP sentiment results

reported results · Published: 2026-02-20

Source-published advisory, non-binding February results. Not the August/September poll and not mainnet activation.

Participation: 99 / 173 ZCAP members. Source-reported response rate: 57%.

February reported support percentage: support / (support + oppose) × 100; abstentions excluded. Counts are ZCAP ballots, not ZEC-weighted coinholder votes. Source rounding: one decimal place. This differs from September option percentages, which include abstentions.

QuestionSupportOpposeAbstainTotal ballotsSupport %
1. Zcash Shielded Assets (ZSAs)692919970.4%
2. Network Sustainability Mechanism (NSM) + Issuance Smoothing791559984%
3. Burning 60% of Transaction Fees via NSM712089978%
4. Memo Bundles732249976.8%
5. Explicit Fees791649983.2%
6. Disallowing v4 Transactions (Sprout Deprecation)732159977.7%
7. Project Tachyon (New Shielded Pool for Scalability)831429985.6%
8. STARK Proof Verification via TZEs (Layer-2 Support)5038119956.8%
9. Comparable-Based Dynamic Fee Mechanism672399974.4%
10. Consensus Accounts6719139977.9%
11. Orchard Quantum Recoverability86949990.5%

Read primary Foundation source · Checked: 2026-10-01T18:02:51.083797+00:00

Source methodology: Source-published advisory poll; deterministic HTML table/heading extraction; no independent ballot recount. Activation: unverified.

Article snapshot SHA-256

20231829f41a15f0c5a23fcde32b184317380818dbce9ca98a7565626177b1f4

August 2026 ZCAP scope announcement

announcement only · Published: 2026-08-27

Announcement and questions retrieved; advisory poll. Later outcome not established by this announcement. September forum direct retrieval returned HTTP 403.

This announcement does not contain results. See the separately sourced September scope results below; no February totals are reused here.

  1. NSM Issuance Smoothing
  2. NSM Reissuance Start Date
  3. Sprout Deprecation
  4. Faster Block Times
  5. NU7 Scope and Readiness

Announced closing time: 2026-09-14T19:00:00Z. This historical time is not an invitation to vote or an assertion that voting is still open.

Read primary Foundation source · Checked: 2026-10-01T18:02:51.081729+00:00

Source methodology: Source-published advisory poll; deterministic HTML table/heading extraction; no independent ballot recount. Activation: unverified.

Article snapshot SHA-256

8209b0b2279e5efe708d968de0cb0a1e10767399dc728e3557c043e8c39a9608

September 2026 ZCAP NU7 scope results

reported option results · Published: 2026-09-14

September 2026 ZCAP advisory, non-binding poll. All published options are preserved. Smooth issuance led with 57 votes (42.2%), a plurality, not a majority. These results do not establish final ZIP approval, a confirmed activation date or a mainnet upgrade.

Participation: 135 / 198 ZCAP members. Source-reported response rate: 68%.

September percentage basis: option votes / actual question total × 100; abstentions included. Counts are ZCAP ballots, not ZEC-weighted coinholder votes. Published percentages are rounded to one decimal place and may not sum to exactly 100%.

Question wording below is quoted from the historical poll, including its proposal assumptions; it is not a current approval or activation statement by ZEC View.

1. The component of the Network Sustainability Mechanism that removes ZEC from circulation is already approved. How that ZEC is recycled into future block rewards remains unresolved. In no case will the total supply of ZEC be affected. Refs: ZIP 233, ZIP 234. Which approach do you support?

Total votes for this question: 135

OptionVotesPublished %
Smooth issuance curve. Replace halvings with a gradual issuance curve. ZEC removed from circulation by the NSM is recycled into future block rewards along the same curve.5742.2%
Preserve halvings. Keep the existing halving schedule for new ZEC. ZEC removed from circulation by the NSM is eventually recycled into future block rewards.5440.0%
Abstain1511.1%
Do not include issuance smoothing in NU7. How ZEC removed from circulation by the NSM is recycled into future block rewards is left to future governance.96.7%

2. NSM has prior coinholder approval. This question concerns the start of reissuance of funds removed from circulation (which includes at least 60% of total fees). When should NSM reissuance of funds removed from circulation begin?

Total votes for this question: 135

OptionVotesPublished %
As soon as possible. If the outcome of Q1 is smoothed issuance, this will be February 2027; otherwise it may be sooner.6749.6%
February 2031, regardless of the outcome of Q1.3123.0%
February 2027, regardless of the outcome of Q1.1914.1%
Abstain1813.3%

3. The Sprout pool was deprecated in 2018. Deposits are disabled, it holds less than 23,000 ZEC, and it accounts for under 0.1% of transaction volume. Disabling v4 transactions is now broadly accepted; only timing is open. The disposition of the affected funds is out of scope for this poll and is not specified here. When should v4 transactions be disabled?

Total votes for this question: 134

OptionVotesPublished %
Immediately at NU7 activation.6548.5%
One year after this poll concludes.3828.4%
Do not set a date to disable v4 transactions.2317.2%
Abstain86.0%

4. Should we reduce the block target spacing from 75s to 25s, and introduce per-pool action limits, per [ZIP-218]?

Total votes for this question: 135

OptionVotesPublished %
Yes9570.4%
Abstain2115.6%
No1914.1%

5. NU7 will be consistent with the results of this poll, assuming each applicable feature is implemented by September 30th. How should features that are not ready by the deadline be handled?

Total votes for this question: 135

OptionVotesPublished %
Ship NU7 as soon as possible, removing any feature that is not implemented by the September 30th deadline.8663.7%
Delay NU7 until every applicable feature approved in this poll is deemed complete.3425.2%
Abstain107.4%
I do not support this NU7 plan.53.7%

View original result image · View published polling results

Results are rendered from verified local structured data, not a live image fetch. If source-image re-verification fails, the verified results are retained and the failed check is recorded in the update history.

Verification and update history
  • historical retrieval failure · Earlier image retrieval returned HTTP 403; superseded by the visually verified local snapshot.
  • 2026-10-05T00:56:23Z · visually verified

Result image SHA-256: 8ae7435cfeeccbd0eb85a1e4e3b79404bd07591e2948865b93814e3257a39720

Read primary Foundation source · Checked: 2026-10-05T00:56:23Z

Source methodology: Manual transcription visually checked against the downloaded Foundation result image; original counts and published percentages preserved; no independent ballot recount. Activation: unverified.

Article snapshot SHA-256

e15c3b65afba4195aa3c1c4a9837933659a7d7695a44b3efbc8c7103ec588a2e

Historical document comparison

This saved ZIP 259 comparison is historical, not the latest document or a live change feed. Its Draft text and unresolved heights describe only the saved versions; use the checked document records above for the latest verified status.

ZIP 259 version difference

line-multiset difference; locations in each original; not semantic consensus analysis. 14 added lines and 8 removed lines. Not a review of consensus semantics.

Historical snapshots retrieved (UTC): →

Before version → After version

Before hash: 8c06371e8753cd2c97cd277699924067f7e30eac985041ecd2bbb617ec43425b
After hash: 5e6f2b934137be8d7fc989812f9d1e66d29fbf4e35f7b621372f7d18b170e5b0

Added

+ L114: : Testnet: 4465026

+ L121: : Testnet: 7305222

+ L124: Each NSM_REISSUANCE_HEIGHT is $\mathsf{DEPLOYMENT\_BLOCK\_HEIGHT}$ for the

+ L125: corresponding network, as calculated in ZIP 237 [^zip-0237]. The Testnet

+ L126: ACTIVATION_HEIGHT (NU7) $A = 4{,}465{,}026$ lies between the second and third

+ L127: pre-NU7 Testnet halvings (2,796,000 and 4,476,000). The ZIP 218 third halving

+ L128: is therefore at $H_3 = 13{,}428{,}000 - 2A = 4{,}497{,}948$, and the Testnet

+ L129: reissuance height is $H_3 + 2{,}807{,}274 = 16{,}235{,}274 - 2A = 7{,}305{,}222$.

+ L132: : Testnet: 170180

+ L133: : Mainnet: 170190

+ L184: * Assign the Mainnet NU7 activation height.

+ L185: * Publish the Mainnet NSM reissuance height calculated from the assigned

+ L186: Mainnet NU7 activation height.

+ L230:

Removed

− L114: : Testnet: TBD (To be set on OCT 5)

− L121: : Testnet: $\mathsf{DEPLOYMENT\_BLOCK\_HEIGHT}$ for Testnet, as calculated in ZIP 237 [^zip-0237]

− L125: : Testnet: TBD

− L126: : Mainnet: TBD

− L177: * Assign the NU7 activation heights.

− L178: * Publish the Mainnet and Testnet NSM reissuance heights calculated from the

− L179: assigned NU7 activation heights.

− L180: * Assign the minimum network protocol versions.

Method and limitations

Three documents are retrieved at immutable repository commits and SHA-256 checked. Diff compares line multiplicity, so moves/reordering may not appear as semantic changes. No automatic YMYL publication, no vote collection, and no independently running node. The September 14, 2026 Foundation article and result image are preserved locally; all published ZCAP option results were visually verified. Direct forum availability does not determine whether these verified results can be displayed. All document content remains available without JavaScript; interactive filtering needs JavaScript.

Compare the reference issuance schedule · Source ledger · Methods