Zebra v1.0.0-alpha.3

Zebra's latest alpha brings multiple reliability and stability improvements for node startup, long-running syncs, and testing.

Some notable changes include:

Added

• Add beta rust to CI (#1725)
• Add Usability Testing Plan GitHub issue template (#1519)
• Add Release Checklist GitHub pull request template (#1717)

Changed

• Compute the network message body length to reduce heap allocations (#1773)
• Re-enable the macOS conflict acceptance tests (#1778)
• Re-enable coverage CI (#1758, #1787)
• Disable fail-fast in the CI test job (#1776)
• Rename responsible_disclosure.md to SECURITY.md (#1747)

Removed

• Disable unreliable testnet large sync test (#1789)

Fixed

Hangs and Panics

• Refactor connection.rs to make fail_with panics impossible (#1721)
• Stop ignoring failed peer addresses (#1709)
• Retry initial peer DNS resolution on failure (#1762)
• Update tower-batch semaphore implementation (#1764)
• Use ready! in ChainVerifier::poll_ready (#1735)
• Use CallAllUnordered in peer_set::add_initial_peers (#1734)

Testing

• Bump CI build and test timeouts to 60 minutes (#1757)
• Run CI workflow on push to main & manual request (#1748)
• Set ZEBRA_SKIP_NETWORK_TESTS using Windows syntax (#1782)
• Fix Windows build failures due to disk space (#1726)
• Fix acceptance test timeouts, cleanup, and diagnostics (#1736, #1766, #1770, #1777)

Logging and Metrics

• Update PeerSet metrics after every change (#1727)
• Log initial peer connection failures (#1763)

Zebra v1.0.0-alpha.2

Zebra's latest alpha brings multiple reliability and stability improvements for node startup, node shutdown, and long-running syncs.

Some notable changes include:

Added

• Asynchronous Groth16 verification (#830)
• Security disclosure principles (#1650)

Changed

• Document that connect_isolated only works on mainnet (#1693)
• Document the impact of the redjubjub channel bound (#1682)
• Log when the syncer awaits peer readiness (#1714)

Fixed

• Fix shutdown panics (#1637)
• Add hints to port conflict and lock file panics (#1535)
• Perform DNS seeder lookups concurrently, and add timeouts (#1662)
• Avoid buffer slot leaks in the Inbound service (#1620)
• Avoid a buffer slot leak by removing CallAllUnordered (#1705)
• Avoid future buffer slot leaks in ChainVerifier (#1700)
• Limit inbound download and verify queue (#1622)
• Increase a tower-batch queue bound (#1691)
• Fix a f64::NAN metrics sentinel (#1642)
• Actually use VerifyCheckpointError::CommitFinalized (#1706)

Zebra v1.0.0-alpha.1

Zebra's second alpha brings multiple reliability and stability improvements for long-running syncs.

We've resolved known panics during syncing, and reduced the number of sync hangs.

Some notable changes include:

Added

• Add peer set tracing (#1468)
• Add Sentry support behind a feature flag (#1461)
• Log configured network in every log message (#1568)

Changed

• Export new precompute api in zebra-script (#1493)
• Rewrite peer block request hander to match the zcashd implementation (#1518)

Fixed

• Avoid panics when there are multiple failures on the same connection (#1600)
• Add sync and inbound timeouts to prevent hangs (#1586)
• Fix Zebra versions so all crates are on the 1.0.0-alpha series (#1488)
• Make 'cargo run' use 'zebrad' rather than failing (#1569)
• Panic if the lookahead limit is misconfigured (#1589)
• Recommend using --locked with 'cargo install' (#1490)
• Simplify C++ compiler dependency in the README (#1498)
• Stop failing acceptance tests if their directories already exist (#1588)
• Stop panicking when ClientRequests return an error (#1531)
• Upgrade to tokio 0.3.6 to avoid a time wheel panic (#1583, #1511)

Currently, Zebra does not validate all the Zcash consensus rules.

Zebra v1.0.0-alpha.0

Zebra first alpha release 🎉

The goals of this release are to:

• participate in the Zcash network,
• replicate the Zcash chain state,
• implement the Zcash proof of work consensus rules, and
• sync on Mainnet under excellent network conditions.

Currently, Zebra does not validate all the Zcash consensus rules.
It may be unreliable on Testnet, and under less-than-perfect
network conditions.