12217

Zebra submits a block-submission fix proposal｜NU7 still awaits height trigger｜ZEC: wait for confirmation, don’t chase

My view is that checking node status should take priority before upgrading. On November 4, the Zebra repository maintained by the Zcash Foundation opened Issue #12216 and proposed PR #12217: when no peers are available, repeatedly submitting blocks via submitblock can cause a backlog of pending broadcast notifications, potentially leading subsequent submissions to be rejected. Developers said they reproduced the issue after about 10,016 submissions in a peerless environment replaying mainnet data. The proposed changes adjust how notifications are received and how older pending items are replaced, to ensure newer blocks are propagated first when connectivity is restored. The PR is currently a Draft and remains Open; it should not be described as a merged fix, widespread mainnet block stoppage, or an exploit used to steal ZEC. The issue description is limited to specific node and submission conditions, and is not the same as a network-wide consensus failure.

The practical significance of this development is that, with NU7 approaching, miners and node operators need both the correct protocol version and stable peer connections and block propagation. Official ZIP 259 specifies that the NU7 mainnet activation condition is block height 3543405, not a particular round-number time on the calendar. When I checked, Blockchair showed a height of 3542541, still 864 blocks short, while the ZecBlock network page still showed NU6.3. These two on-chain observations corroborate the upgrade specification, so activation should not be announced prematurely. If the new PR is accepted later, it will improve submission reliability in certain offline replay or peerless-node scenarios, but it will not change the 25-second target block time, the token supply cap, or provide a reason to expect prices to rise.

The market is indeed somewhat stronger than at the open: Kraken ZEC/USD was around $1,321.21, versus an opening price of $1,295.73, with an intraday low and high of $1,283.68 and $1,333.77, respectively, and a rolling 24-hour upper bound of $1,350. This is a price reaction and should not be attributed to a PR that has not yet been merged. Farside data shows ZCSH saw net outflows of $3.6 million on both November 2 and 3, followed by a $3.4 million net inflow on the 4th, leaving a net outflow of $3.8 million over the three days. A single day of positive flows is not enough to prove sustained institutional buying. Near-term support is at $1,283.68 and the rolling low of $1,266.43; resistance is at $1,333.77 and $1,350. If a node fork occurs once the activation height is reached, deposits and withdrawals are disrupted for an extended period, or the price falls below $1,266.43 and fails to recover, I would withdraw my cautiously positive view.

If I were trading this myself, I would stay out for now and only consider a small, unleveraged spot long. I would wait until the NU7 height is actually reached, the project and commonly used trading platforms confirm normal operation, and the hourly chart closes above $1,350 and holds on a retest. Then I would place a trial trade with no more than 1% of total capital; the first target is $1,380, where I would reduce the position by half, and the second target is $1,420, with a trailing stop on the remainder. I would exit if the price falls back below $1,283.68 after entry. If it cannot hold above $1,350 within two days, or if an upgrade issue is officially disclosed, I would close the position proactively. If the conditions are not met, I stay out; no trade is made up.

Sources: Zebra Issue #12216与PR #12217, ZIP 259, Blockchair, ZecBlock, Farside, Kraken. #ZEC

This is solely my personal market observation and does not constitute investment advice.