NU7 Coinholder Vote Results

Private coinholder vote on NU7 scope — issuance smoothing, Sprout deprecation, 25-second blocks, and upgrade schedule. Organized by Valar Group and Project Tachyon.

Results published

Published results

Published by the voting-chain API. ZecBlock has not independently verified this tally.

Verify this tally independently

ZEC per question: ~2.40M
Ironwood at snapshot: 3.73M ZEC
Share of snapshot pool supply: 64.3–64.4%

Snapshot comparison & verification

Compared with 3,731,959.40650354 ZEC in Ironwood at snapshot block 3,459,350 (Aug 24, 2026, 19:18:03 UTC). This is not an exact eligible-voter turnout rate.

Snapshot block hash

000000000079f151b017b515d0084713d19bd596a76ecfd75f82fd32bf43d968

Snapshot RPC command

getblock "000000000079f151b017b515d0084713d19bd596a76ecfd75f82fd32bf43d968" 1

Run on a Zcash mainnet node. In valuePools, Ironwood has chainValueZat = 373195940650354; divide by 100,000,000 for ZEC. The tally uses a separate voting-chain node.

1,000,000 ZEC participation threshold: met.

Vote weights include abstentions. Question totals do not count unique voters.

Q1 — NSM Issuance Smoothing

2,403,537 ZEC participating

Top choice

B.Preserve halvings.

Keep the existing halving schedule for new ZEC. ZEC removed from circulation by the NSM is eventually recycled into future block rewards.

98.85%

2,375,932.375 ZEC

A.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.

0.93%

22,384.875 ZEC

C.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.

0.17%

4,147.625 ZEC

D.Abstain.

0.04%

1,072.125 ZEC

Question context

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. Which approach do you support?

Q2 — NSM Reissuance Start Date

2,401,152 ZEC participating

Top choice

C.February 2031, regardless of the outcome of Q1.

96.61%

2,319,643.75 ZEC

A.As soon as possible.

If the outcome of Q1 is smoothed issuance, this will be February 2027; otherwise it may be sooner.

2.93%

70,239.625 ZEC

B.February 2027, regardless of the outcome of Q1.

0.26%

6,283 ZEC

D.Abstain.

0.21%

4,985.625 ZEC

Question context

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?

Q3 — Sprout Deprecation

2,399,146.25 ZEC participating

Top choice

A.Immediately at NU7 activation.

97.28%

2,333,854.625 ZEC

B.One year after this poll concludes.

0.57%

13,787 ZEC

C.Do not set a date to disable v4 transactions.

2.08%

49,820.875 ZEC

D.Abstain.

0.07%

1,683.75 ZEC

Question context

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?

Q4 — Faster Block Times

2,399,463.25 ZEC participating

Top choice

A.Yes.

99.93%

2,397,669.375 ZEC

B.No.

0.01%

141.625 ZEC

C.Abstain.

0.07%

1,652.25 ZEC

Question context

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

Q5 — NU7 Scope and Readiness

2,399,474.375 ZEC participating

Top choice

A.Ship NU7 as soon as possible, removing any feature that is not implemented by the September 30th deadline.

99.30%

2,382,601.5 ZEC

B.Delay NU7 until every applicable feature approved in this poll is deemed complete.

0.53%

12,707.5 ZEC

C.I do not support this NU7 plan.

0.00%

4 ZEC

D.Abstain.

0.17%

4,161.375 ZEC

Question context

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?

Verify the tally

Node setup guide ↗

Run on your own synced zvote-1 node. No wallet, keys or funds needed.

Voting round · NU7 Scope

16eef7ebc77e0e04fb1c7329abfcc390f4a0c002964671ebb360914a3e5a3f11

Verify tally command

svoted query vote verify-tally 16eef7ebc77e0e04fb1c7329abfcc390f4a0c002964671ebb360914a3e5a3f11 \
  --node tcp://localhost:26657 --output json

Question labels & totals (JSON) ↗Raw finalized tally (JSON) ↗Verifier source ↗

What should the output show?

Confirm the report names the round above and includes:

SESSION_STATUS_FINALIZED
verified: true
All 19 question/option checks, with claimed_total values matching the raw tally.

A failed or missing check needs investigation. The command verifies totals against encrypted accumulators and validator partial decryptions; it does not reveal individual ballots or constitute a full protocol audit.

Data sources & methodology

Each raw tally unit is 12,500,000 zatoshi (0.125 ZEC), per the voting software’s conversion. Missing option index 0 fields use protobuf’s zero default.

Percentages use each question’s vote weight, including abstentions, not its number of voters. Totals cannot be added to count unique participating ZEC or voters. The 1,000,000 ZEC threshold applies to at least one question, including abstentions.

ZecBlock checks for a complete, matching summary and tally. API responses alone are not independent verification.

This page refreshes automatically while visible. Source responses are cached for up to five minutes and may remain older during upstream failures.

Snapshot

Aug 24, 2026· 19:18 UTC

Ironwood funds must be spendable

Voting opens

Aug 25, 2026

~20 days to cast votes

Voting closes

Sep 14, 2026· 19:00 UTC

Voting has ended

Voting chain details

Connecting to zvote-1…

RESOURCES_&_AUDIT

Forum announcement Run a validator Verify a tally Vote SDK (source)PIR server setup Voting circuits Client library ZIP 218 (25s blocks)ZIP 233 (NSM burn)ZIP 234 (issuance smoothing)

What ZecBlock shows

This page displays public vote parameters, published aggregate results, and live chain state from the Valar zvote-1 REST API. ZecBlock has not independently verified the tally. Follow the verification instructions above to check it against your own full node. Individual ballots remain private.