Releases: AztecProtocol/aztec-packages
v4.2.1
Release 4.2.1 is a MANDATORY single-fix patch on top of 4.2.0.
The on-chain check for "has this payload already been proposed?" was timing out at the RPC layer so signaling was suppressed across the validator set. This hotfix release restores governance signaling.
Bug Fixes
-
Sequencers could not signal governance payloads on long-lived rollups (#23001): The "has this payload already been proposed?" check used
eth_getLogsover the rollup's full L1 deployment range. Once that range exceeded typical RPC provider block-range caps the call timed out, the publisher treated the timeout as "already proposed," and sequencers silently stopped signaling.The publisher now re-checks each slot rather than caching a permanent verdict, and the RPC-failure mode is switched from fail-closed to fail-open — a flaky L1 endpoint should not silence governance participation, and a duplicate signal is harmless.
v4.3.0-nightly.20260506
v4.3.0-nightly.20260506
v4.3.0-nightly.20260505
v4.3.0-nightly.20260505
v4.3.0-nightly.20260504
v4.3.0-nightly.20260504
v4.3.0-nightly.20260503
v4.3.0-nightly.20260503
v4.3.0-nightly.20260501
v4.3.0-nightly.20260501
v4.3.0-nightly.20260430
v4.3.0-nightly.20260430
v4.3.0-nightly.20260429
v4.3.0-nightly.20260429
v4.3.0-nightly.20260428
v4.3.0-nightly.20260428
v4.3.0-nightly.20260427
v4.3.0-nightly.20260427