Zebra 3.0.0 Launch: Our Most Function-Wealthy Launch Ever

We’re excited to announce the discharge of Zebra 3.0.0—probably the most feature-rich Zebra launch ever!  Along with supporting NU6.1, the newest community improve, we’ve additionally targeted on making Zebra simpler to run in manufacturing, sooner to sync, and accessible on extra platforms.

Zebra 3 at a Look

Right here’s what’s new on this launch:

• NU6.1 Community Improve – Prompts the newest Zcash protocol improve on Mainnet
• Well being Test Endpoints – Constructed-in HTTP endpoints for monitoring node well being and readiness in manufacturing deployments
• ARM64 Help – Native help for Apple Silicon Macs (M1/M2/M3), Raspberry Pi, and ARM cloud servers
• Dramatically Sooner Preliminary Sync – Full blockchain sync from genesis now takes 15-16 hours in CI and fewer than 9 hours on some machines, down from 24+ hours (representing a 35-65% discount in preliminary sync time)
• Enhanced Safety – Docker photographs now embody software program invoice of supplies (SBOM) and construct attestations
• Simpler Configuration – Configure Zebra utilizing surroundings variables with out enhancing config recordsdata
• Improved Community Infrastructure – Zcash Basis now runs highly-available Zebra nodes to raised help the ecosystem
• New RPC Strategies – Three new strategies for community data, mempool stats, and aspect chain queries plus a number of new fields on the outputs of present RPC strategies.
• Sooner Testing – Modernized take a look at infrastructure for faster growth cycles

New Versioning method – Main model numbers now point out breaking modifications, not simply community upgrades. This helps you perceive when updates want further consideration.

What This Means for You

In the event you run Zebra in manufacturing

Now you can arrange well being monitoring with load balancers and orchestration instruments like Kubernetes. ARM64 help opens up extra {hardware} choices together with cost-effective ARM cloud cases. The Zcash Basis can also be now working highly-available infrastructure which advantages all the ecosystem.

In the event you’re organising Zebra for the primary time

Zebra is now simpler to configure, permitting you to set surroundings variables as an alternative of enhancing config recordsdata. Preliminary sync is dramatically sooner (15-16 hours as an alternative of 24+ hours)—and when you’re on an Apple Silicon Mac, you’ll get native ARM64 efficiency with none further steps.

In the event you construct instruments that use Zebra

Three new RPC strategies present higher entry to community info, mempool knowledge, and aspect chain queries. We’ve additionally improved transaction validation efficiency and made many enhancements to present RPC strategies.

In the event you contribute to Zebra

Our modernized testing infrastructure means sooner CI runs and faster suggestions on pull requests. The codebase additionally advantages from quite a few code high quality enhancements and higher documentation.

The Particulars

Need to know extra? Right here’s a deeper take a look at what’s on this launch.

Community Improve & Protocol Adjustments

NU6.1 Community Improve

Zebra 3.0.0 prompts NU6.1 on Mainnet, which incorporates:

• Prolonged funding streams for community growth (1,260,000 further blocks)
• One-time lockbox disbursements
• The most recent community protocol model (170_140)

Operational Excellence

This launch contains a number of options particularly designed to make working Zebra in manufacturing simpler and extra dependable.

Well being Test Endpoints for Manufacturing Operations

One of many standout options is the addition of HTTP well being verify endpoints. These easy HTTP endpoints make it simple to combine Zebra with manufacturing monitoring and cargo balancing programs.

Two endpoints can be found:

• /wholesome – Returns 200 when Zebra is working and has energetic peer connections, 503 in any other case
• /prepared – Returns 200 when Zebra is totally synced and able to serve requests, 503 in any other case

The distinction issues for manufacturing deployments: use /wholesome for primary liveness checks (is the method working?) and /prepared to make sure you solely ship site visitors to completely synchronized nodes with energetic peer connections.

Allow the well being verify server by including a [health] part to your configuration:

[health]
listen_addr = "0.0.0.0:8080"
min_connected_peers = 1
ready_max_blocks_behind = 2

The endpoints are disabled by default and designed for inner infrastructure use (no authentication). They return easy plain-text responses like “okay” or transient explanations when checks fail.

ARM64 Help: Native Efficiency In every single place


Zebra now runs natively on ARM64 platforms, which implies:



Apple Silicon Macs (M1, M2, M3) – No extra emulation or Rosetta overhead
ARM cloud cases – AWS Graviton, Google Cloud Tau T2A, and different ARM servers
Single-board computer systems – Raspberry Pi and comparable gadgets



 

Docker robotically handles platform detection:


docker pull zfnd/zebra:newest
# Mechanically will get the suitable model on your platform


This transformation takes benefit of GitHub’s free ARM64 runners for open supply initiatives, so we are able to construct and take a look at ARM64 releases with out further infrastructure prices. The result's native efficiency on ARM platforms with none setup complexity.


Enhanced Docker Picture Safety


For organizations that must audit their software program provide chain, Zebra’s Docker photographs now embody provenance attestations and Software program Invoice of Supplies (SBOM).


What this implies:



Provenance attestations observe precisely how the picture was constructed, the place, and by whom
SBOM supplies a whole stock of all software program parts within the picture
Each allow safety scanning, vulnerability monitoring, and compliance reporting



These options combine with instruments like Docker Scout, Snyk, and different safety platforms that may robotically scan for identified vulnerabilities.


Improved Community Infrastructure


The Zcash Basis has upgraded its deployment infrastructure to run long-lived, highly-available Zebra nodes. These enhancements immediately profit the Zcash ecosystem:



DNS Seeder Help – Lengthy-lived nodes with static IP addresses present dependable peer discovery for the community
Multi-zone Excessive Availability – Working 2-3 cases throughout availability zones ensures constant uptime
Automated Well being Monitoring – Makes use of the brand new /wholesome endpoint with auto-healing to take care of service reliability
Persistent Storage – Disk reuse between deployments eliminates prolonged re-syncs, guaranteeing nodes keep present



These long-lived nodes with static IP addresses assist help the broader Zcash ecosystem by offering secure infrastructure for DNS seeders and bettering total community reliability. Whereas this work is particular to the Basis’s infrastructure, the underlying enhancements to Zebra’s deployment tooling can be found for anybody working manufacturing nodes.


Efficiency Enhancements


Dramatically Sooner Preliminary Sync: From 24+ Hours to Beneath 16 Hours


This launch delivers a major efficiency achievement: full blockchain synchronization from genesis now completes in 15-16 hours, down from 24+ hours in earlier variations. This represents a 35-40% discount in sync time.


The development comes primarily from PR #9973, which mounted a regression in how Zebra updates tackle balances within the database. The repair avoids costly RocksDB merge operations when the database format is already up-to-date, dramatically bettering write efficiency throughout preliminary sync.


That is mixed with batch validation enhancements for each Orchard and Sapling proofs, which cut back computational overhead throughout block validation.


Actual-world influence: Our steady integration assessments present constant sync instances of 15-16 hours for full Mainnet sync from genesis, in comparison with 20-28 hours earlier than these optimizations. In the event you’re working a brand new Zebra node or syncing from scratch, you’ll see this enchancment instantly.


Higher Efficiency Via Batch Validation


Transaction validation is now extra environment friendly due to:




Batch validation reduces computational overhead throughout block processing by validating teams of proofs collectively, which is extra environment friendly than particular person verification. The batch measurement for Orchard validation elevated from 2 to 64 actions per batch.


Developer Expertise


Simpler Configuration with Setting Variables


Zebra now makes use of a layered configuration system that makes it simpler to configure by way of surroundings variables:


export ZEBRA_NETWORK__NETWORK=Mainnet
export ZEBRA_STATE__CACHE_DIR=/var/cache/zebra
export ZEBRA_RPC__LISTEN_ADDR=0.0.0.0:8232
zebrad begin


The configuration hundreds in layers: built-in defaults, then non-compulsory TOML file, then surroundings variables. This implies you may:



Run Zebra with zero configuration recordsdata for easy setups
Use a base configuration file and override particular values by way of surroundings variables
Maintain secrets and techniques in surroundings variables as an alternative of config recordsdata



The sample for surroundings variables is ZEBRA_SECTION__KEY, matching the TOML construction. For instance, [network] part’s community = "Mainnet" turns into ZEBRA_NETWORK__NETWORK=Mainnet.


Necessary: This transformation contains breaking updates to surroundings variable names. See the Migration Notes part beneath.


New RPC Strategies


Three new RPC strategies enhance compatibility with present instruments:




RPC Enhancements


Many present RPC strategies obtained enhancements:




Sooner Growth with Improved Testing


This launch features a full modernization of the testing infrastructure utilizing cargo-nextest:



Sooner take a look at execution – Higher parallel take a look at working
Centralized take a look at configuration – 17 specialised take a look at profiles in .config/nextest.toml
Clearer take a look at outcomes – Higher progress reporting and timeout dealing with
Simplified CI workflows – Decreased complexity in GitHub Actions



For contributors, this implies faster suggestions on pull requests and fewer time ready for CI to finish.


New Versioning Technique


Beginning with Zebra 3.0.0, we’re altering how we model releases. Beforehand, main model bumps had been primarily tied to community upgrades. Going ahead, we’ll launch a brand new main model every time there are breaking modifications, which incorporates:



Adjustments to the Zebra API
Adjustments to operational necessities (like configuration format)
Different modifications that require motion from node operators or builders



This method provides us a clearer method to talk influence. Once you see a serious model bump, evaluation the discharge notes fastidiously and plan for potential updates to your deployment or integration. Minor model bumps will proceed to be backward suitable.


Migration Notes


In the event you’re upgrading from Zebra 2.x, please notice these breaking modifications.


Setting Variable Adjustments


The surroundings variable naming scheme modified. Key updates:






Previous Variable
New Variable




ZEBRA_CACHE_DIR
STATE_CACHE_DIR


ZEBRA_FORCE_USE_COLOR
FORCE_USE_COLOR


RUST_LOG or ZEBRA_RUST_LOG
ZEBRA_TRACING__FILTER






For configuration values, use the sample ZEBRA_SECTION__KEY:



ZEBRA_NETWORK__NETWORK=Mainnet
ZEBRA_RPC__LISTEN_ADDR=0.0.0.0:8232
ZEBRA_STATE__CACHE_DIR=/var/cache/zebra



Docker Entrypoint Adjustments


The Docker entrypoint not generates TOML configuration recordsdata robotically. As a substitute:



Configure utilizing surroundings variables (really helpful)
Mount a configuration file into the container
Use a mixture of each approaches



Acknowledgments


An enormous thanks to all of the contributors who made this launch attainable: @arya2, @oxarbitrage, @conradoplg, @gustavovalverde, @syszery, @upbqdn, @str4d, @nuttycom, @zancas, @natalieesk, @gap-editor, @elijahhampton, @dorianvp, @AloeareV, @sashass1315, @radik878, @GarmashAlex, @Galoretka and @Fibonacci747.


Particular recognition goes to Least Authority for the safety audit of  the NU6.1 implementation which supplied precious strategies for enhancements.


Thanks to everybody who filed points, examined launch candidates, and supplied suggestions all through this launch cycle.




The Greater Image


The Z3 Stack


Zebra 3.0.0 is designed to combine seamlessly with the opposite Z3 parts. We’ve been creating the Z3 stack, which is a whole deployment resolution for Zcash infrastructure. The stack contains:



Zebra – The consensus node (this launch)
Zaino – The indexer for tackle and transaction knowledge
Zallet – The CLI pockets service



These parts work collectively to offer a whole, production-ready Zcash infrastructure you could deploy with a single configuration.


Zebra 3.0.0 represents a major step ahead in making Zebra production-ready. The options on this launch—well being checks, ARM64 help, and improved configuration—present a robust basis for dependable node operations.


We’re persevering with to develop the Z3 stack to offer a whole, easy-to-deploy resolution for Zcash infrastructure. We’re additionally engaged on future community improve help, together with early implementations of proposals for NU7.


Get Concerned


Questions or suggestions? We’d love to listen to about your expertise with Zebra 3.0.0. Share your ideas on the Zcash Neighborhood Discussion board, join with us on Discord, or open a problem within the Zebra repository: