# Zcash Foundation puts Zebra 7.2.0 beta into miner testing

Published 2026-11-19 · Crypto.world Team · Crypto.world

> The Zcash Foundation released Zebra 7.2.0-beta.1 for miners, mining pools and node operators to test alongside Zebra 7.1.0. The beta adds optional block pruning and changes to mining templates, block propagation and initial synchronization; production nodes should remain on 7.1.0.

The [Zcash](https://forum.zcashcommunity.com/t/zebra-7-2-0-beta-1-release/59466) Foundation has released Zebra 7.2.0-beta.1 for miners, mining pools and the operators who run their nodes, asking them to test it alongside 7.1.0 while production nodes stay on 7.1.0. The November 19 release combines mining changes previously tested in Zebra Ándale with work on verification, initial synchronization and block propagation.

## Earlier templates and faster relay

Zebra now serves a block template as soon as it is built and checks it in the background. After a new block passes proof-of-work and header checks, the node can provide coinbase-only work before transaction checks finish; that work expires after one second. The internal miner starts on new work immediately rather than sleeping for up to 20 seconds.

When a miner submits a block built from a template Zebra has already checked, the node announces it to peers while validation continues. The release also says Zebra skips rechecking the same transactions and checks the block’s chain position during validation, allowing `submitblock` to return sooner. Among beta nodes, received blocks are announced on commit rather than after a delay of up to seven seconds, while mempool transactions are announced every two seconds instead of every seven.

Compact block relay is on by default. It lets supporting peers rebuild blocks from their mempools instead of downloading whole blocks, and relay them once proof of work and transaction commitments check out. If a peer announces a transaction but cannot send it, Zebra requests it from other peers after 200 milliseconds rather than waiting up to 73 seconds.

## Pruning and sync options

Operators can enable block pruning with `state.prune_blocks_older_than`. A pruned node retains at least 10,000 recent blocks and the data Zebra needs to validate, mine and submit blocks. The Foundation reports that one Mainnet measurement used about 15 GB for a pruned database, compared with about 282 GB for an archive; the release notes say to leave extra room for initial sync and compaction.

Pruning is off by default and does not work with a `zcashd` sidecar. Pruned data uses a separate `state-pruned/v29` directory, and moving an existing archive there requires a manual step with the node stopped. Pruned nodes advertise `NODE_NETWORK_LIMITED`. The release notes say `zcashd` does not download blocks from them and Zebra 7.1.0 only downloads the blocks they announce, so operators should keep some Zebra peers connected so the blocks they find spread quickly.

The beta also offers opt-in fast tree sync. When enabled, initial sync uses note commitment tree roots supplied by peers and checks them against Zebra’s checkpoints instead of computing every tree locally. The release describes this as a one-way change: Zebra 7.1.0 and tools that read the database directly cannot use the resulting database. At fast-synced heights, `z_gettreestate` and the `lightwalletd` tree-state methods return an unavailable error.

## Testing, fees and availability

The Foundation asks mining operators to run the beta beside a 7.1.0 node, direct a test miner or a small share of pool work to it, and report results. Its testing instructions recommend getting work through `getblocktemplate` long polling and comparing how soon new work arrives after each block, as well as whether solved blocks are accepted and relayed. The post points testers to `rpc.getblocktemplate.first_template.duration_seconds` and `rpc.submitblock.outcomes.total` for node-side measurements.

On Mainnet, the beta requires the original ZIP 317 fees until the chain reaches height 3,590,000, which the release expected around 15:30 UTC on November 19, 2026. Before that height, transactions paying the reduced fee of 1,000 zatoshis per logical action are not relayed or mined. From that height onward, and already on public Testnet, the beta accepts the same fees as Zebra 7.1.0.

The beta is available from GitHub and Docker Hub as `zfnd/zebra:7.2.0-beta.1`, also tagged `edge`; `zfnd/zebra:latest` remains on 7.1.0. On first start, it upgrades a 7.0.0, 7.1.0 or Zebra Ándale state database from format 29.0.0 to 29.2.0 in place, which the Foundation says takes about a minute on Mainnet without a resync. The beta starts warning around December 3, 2026, and stops itself around December 10, the same end-of-support schedule as 7.1.0.

## Sources

1. Original source [Zcash Foundation, Zcash Community Forum](https://forum.zcashcommunity.com/t/zebra-7-2-0-beta-1-release/59466) forum.zcashcommunity.com

## Related stories

- [Zcash Foundation Details Zebra Work After NU7 Activation](https://crypto.world/news/zcash-foundation-zebra-work-after-nu7-activation)
- [Zcash forum post calls for miner input in NU7.1 poll assessment](https://crypto.world/news/zcash-miner-signaling-nu7-1-poll)
- [Zebra 7.1.0 fixes ten Zcash node security advisories](https://crypto.world/news/zebra-7-1-0-fixes-ten-zcash-node-security-advisories)
- [TRON Marks GreatVoyage v4.8.2.4 a Mandatory Node Upgrade](https://crypto.world/news/tron-greatvoyage-v4-8-2-4-mandatory-upgrade)
- [Researchers Model How Capital Costs Delay Bitcoin Mining Gaps](https://crypto.world/news/researchers-model-capital-costs-bitcoin-mining-gaps)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/zcash-foundation-zebra-7-2-0-beta-1-miner-testing
