b31d0882-5

ConfirmedInfrastructure600 words3 min decode

Zcash Foundation opens Zebra 7.2.0 beta with block pruning

Zcash Foundation’s Zebra 7.2.0-beta.1 test cut database use to about 15 GB from 282 GB in one mainnet run, while production nodes remain on 7.1.0 for now.

Zcash Foundation Opens Zebra 7.2.0 Beta With Optional Block Pruning
WitnessZcash Foundation Opens Zebra 7.2.0 Beta With Optional Block PruningBluesnap / pixabay

Outputs

  1. Zcash Foundation opened testing of Zebra 7.2.0-beta.1, with pruning disabled by default.

  2. One mainnet test reduced database use to about 15 GB from roughly 282 GB.

  3. Enabled pruning retains at least 10,000 recent blocks plus data needed for validation and mining.

  4. The beta targets faster validation, initial synchronization, block propagation and mining-template generation.

  5. Production nodes should remain on Zebra 7.1.0 while the beta runs alongside existing nodes.

The Zcash Foundation said it opened testing of Zebra 7.2.0-beta.1 after one mainnet test cut database use to about 15 GB from roughly 282 GB. The reduction came from optional block pruning in the node software update.

What does the beta change?

The beta’s stated scope combines storage reduction with changes to transaction processing and node synchronization:

  • Optional block pruning, which remains disabled by default and must be enabled by an operator.
  • Retention of at least 10,000 recent blocks, along with the data needed for validation and mining.
  • Faster transaction validation, initial synchronization and block propagation as development targets.
  • A shorter wait to generate a mining block template after a new block is produced.

The default-off setting lets operators evaluate pruning without making it part of a standard node configuration. It also makes the storage result conditional on an explicit activation choice rather than a behavior every beta tester receives by default.

When enabled, the mode keeps at least 10,000 recent blocks and the data required for validation and mining. In operational terms, it seeks to reduce stored historical data without stripping the node of information needed for its core functions.

For operators, the reported outcome could mean a materially smaller disk footprint, though one mainnet test does not establish what every configuration will deliver. The 15 GB figure remains a single-test result, not a promised footprint for every deployment.

What is the beta trying to speed up?

The Foundation listed faster transaction validation, faster initial synchronization and faster block propagation among the release targets. Those areas affect routine node operation: validation work, the process of bringing a node current, and the movement of newly produced blocks.

For miners and mining pools, the beta also seeks to shorten the wait to generate a mining block template after a new block is produced. The Foundation said testing is aimed at miners, mining pools and node operators, making the release a performance test across both node and mining infrastructure.

These remain stated targets, not measured guarantees for each tester. The announcement provides no separate timing numbers for validation, synchronization, propagation or template generation, so the operational value of the performance work will depend on what the beta phase produces.

Should production operators deploy it?

The Foundation recommends running Zebra 7.2.0-beta.1 alongside existing nodes while keeping production deployments on Zebra 7.1.0. Its guidance to production operators is explicit: “stay on Zebra 7.1.0.”

That keeps the release in a parallel-test role and limits the amount of production activity placed on beta software. It also gives miners, pools and node operators a way to test pruning and the performance changes without replacing the version they already run.

The Foundation said feedback from testing “will inform development of a stable Zebra 7.2.0 release.” In practical terms, the stable release remains the intended destination for these changes, while 7.1.0 remains the production version recommended during the test.

What is the release context?

The announcement also placed the beta in the context of Zebra’s recent release history. The Foundation’s earlier Zebra 7.0.0 release covered security fixes ahead of the NU7 upgrade, while 7.2.0-beta.1 focuses on optional pruning and performance targets.

The next structural milestone is a stable Zebra 7.2.0 release shaped by feedback from this beta phase. No target date accompanies that milestone, and the Foundation’s standing guidance keeps production nodes on 7.1.0 while 7.2.0-beta.1 remains a parallel test.

via tokenpost.com (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,653 articles