Zebra 4.3.0 Released, Includes Critical Security Fixes.
ZcashTracker
Key Takeaways
- Zebra 4.3.0 has been released, including critical security fixes, and immediate upgrades are strongly recommended for all node operators.
- The release addresses a V5 transaction proof verification bypass that could have led to a chain split and a transaction deserialization panic capable of crashing Zebra nodes.
- An initial implementation of the Network Sustainability Mechanism (ZIP-235) is included, though currently disabled by default and intended for testing.
- Performance profiling tools and documentation have been improved for developers.
- Additional bug fixes resolve issues with Regtest block propagation, pre-Canopy block subsidy calculations, and a Testnet performance regression.
New Protocol Integration and Developer Tools
Get the Z-Brief
Zcash signal & market insights, without the noise.
🔒Zero spam. Zero sharing. Unsubscribe anytime.
This release integrates an initial implementation of ZIP-235, the Network Sustainability Mechanism. This feature is crucial for the long-term economic health of the Zcash network. Currently, ZIP-235 support is disabled by default, gated behind a feature flag, and intended for testing and development rather than production environments (issue #10357).
Developer tooling has also seen improvements, with a dedicated profiling Cargo profile and expanded documentation now available. This update aims to streamline the workflow for developers diagnosing performance bottlenecks and optimizing Zebra's behavior (issue #10411).
Resolved Issues and Test Coverage
Several other bugs have been resolved to enhance network operation and development workflows:- Block propagation on the Regtest network, previously hindered, has been restored for local development and testing (issue #10403).
- The `getblocksubsidy` RPC now accurately calculates miner rewards for blocks predating the Canopy network upgrade, correctly subtracting the Founders’ Reward (issue #10338).
- A performance regression on Testnet, which caused Zebra to consume an entire CPU thread due to repeated checkpoint parsing, has been fixed by caching parsed checkpoints (issue #10409).
