Zcash activated its Heartwood network upgrade at block 903,000 on July 16, 2020, introducing consensus changes that allowed miners to direct newly created funds to shielded Sapling addresses and laid groundwork for more efficient light-client verification.

The official Zcash upgrade record timestamps the activation block at 10:56 UTC. Heartwood was the network’s fourth major upgrade and was endorsed by both Electric Coin Company and the Zcash Foundation. Its activation mattered because the changes reached two structural parts of the protocol: how mining rewards could enter the transaction system and what historical information Zcash block headers committed to.

Heartwood was a planned, backward-incompatible protocol upgrade, not evidence of an adversarial chain split. Operators needed compatible software to continue following the upgraded consensus rules. Electric Coin Company had released zcashd 3.0.0 in May 2020 with support for activation at the predetermined height.

Mining rewards gained a shielded route

ZIP 213 changed the rules for coinbase transactions—the special transactions through which miners collect the block subsidy and transaction fees. Before Heartwood, those transactions could not contain Sapling shielded outputs. After activation, they could.

That made it possible for a miner or mining pool to send coinbase funds directly to a Sapling address instead of first receiving a transparent output and later moving it into the shielded pool. Removing that separate transaction reduced one publicly visible link in the movement of mining rewards.

The upgrade did not require miners to use shielded outputs. Transparent coinbase outputs remained permitted so pools could migrate gradually. Heartwood therefore created an option rather than establishing that mining rewards immediately became predominantly shielded.

The privacy claim also needs a technical qualification. ZIP 213 required shielded coinbase outputs to be recoverable with a fixed, all-zero outgoing viewing key. Consequently, the recipient addresses and values of those initial coinbase outputs remained publicly recoverable. What became private was the subsequent spend relationship: observers could no longer follow the reward through a mandatory transparent-to-shielded transaction in the same way.

Heartwood did not alter the existing Founders’ Reward addresses. Nor did it prove that exchanges, wallets or mining pools had completed operational support on July 16.

Block headers began carrying chain-history commitments

Heartwood’s second component, ZIP 221, changed the meaning of a field in each Zcash block header. After the activation block, the field committed to the root of a Merkle Mountain Range containing information about earlier blocks in the current consensus epoch.

Those commitments were designed to support FlyClient, a probabilistic verification protocol. The specification described a reduction in the number of block headers required for verification from linear growth with chain length to logarithmic growth, subject to the protocol’s security assumptions. Potential beneficiaries included resource-constrained wallets and cross-chain systems that could not economically process the entire Zcash history.

Activation did not itself deliver a complete consumer-facing FlyClient wallet. The consensus change supplied commitments that implementations could use; application availability, integration quality and adoption remained separate engineering questions.

Why Heartwood mattered

Heartwood joined privacy and accessibility at the consensus layer. Shielded coinbase reduced the need for miners to create a visible intermediate transaction, while the history-tree commitments aimed to make meaningful verification possible with less data.

Neither feature guaranteed immediate use. Their significance on July 16 was that the upgraded network began enforcing the rules necessary for miners, wallet developers and cross-chain builders to adopt them. That is a narrower but more verifiable conclusion than claiming that Heartwood instantly made all mining private or produced fully trustless lightweight wallets.

Primary sourceZcash — Heartwood network upgrade record

The complete source packet and revision history are retained with the newsroom record.

Automated desk disclosure

Automated systems may have assisted with source organization and drafting. Coinburn is accountable for the published text and maintains a revision record.

Financial-risk note

This article provides news and analysis, not investment, legal or tax advice. Digital assets are volatile and may result in total loss.