Releases: base/base
Release list
v1.1.1
What Changed
Important
Base Mainnet: Operators must upgrade to this release by June 25th at 18:00:00 UTC for the Beryl hardfork. See here for more information.
Base Sepolia: Recommended upgrade to improve Flashblocks stability
base-reth-node
- Beryl Support for Mainnet
- Fix Flashblock processing where transactions relying on the BLOCKHASH could have different execution outcomes during Flashblocks and canonical processing.
base-consensus
- Beryl Support for Mainnet
v1.1.0
What Changed
Important
Base Sepolia: Operators must upgrade to this release by June 18 at 18:00:00 UTC for the Beryl hardfork. See here for more information.
Base Mainnet: Operators running V1.0.0 or V1.0.1 must upgrade to this release to fix a potential node halt.
base-reth-node
- Beryl Support
- Upgrade Reth to V2.3.0
- Improve Peering Reliability
- JS Tracer Performance Improvement
base-consensus
- Beryl Support
v1.0.1
What's Changed
Performs a small fix to the optimism_syncStatus endpoint to fix current_l1 to track the safe l1 head less --l1-verifier-confs. Previously, current_l1 was equivalent to head_l1 despite L1 verifier confs being configured which was unintended behavior.
Note
This is not a required upgrade.
It is only recommended if you configure --l1-verifier-confs on your node to provide accurate head info when querying optimism_syncStatus against base-consensus.
Full Changelog: v1.0.0...v1.0.1
v1.0.0
What's Changed
Note
This release contains improvements to ERC-7562 tracing performance. For RPC providers or operators relying on account abstraction workflows, this is a recommended release.
base-node-reth
- Upgrades to Reth v2.2.0. This is purely a SDK version bump. Storage V2 upgrade will come in a later release once snapshots for those are ready.
Full Changelog: v0.9.1...v1.0.0
v0.9.1
What's Changed
Important
Required release for node operators running pruned nodes with base-consensus, optional release for archive nodes.
base-consensus
- Fixed crash for pruned nodes syncing
v0.9.0
What Changed
Important
Node operators must upgrade Base Mainet nodes to use base-node-reth and base-consensus by 28th May. See here for more information. This is a recommended release for Base Sepolia nodes.
base-node-reth
- Azul Readiness - Added support for Azul execution-layer changes, including Osaka support.
eth_getProof&debug_executionWitnessRPC performance improvements.
base-consensus
- Azul Readiness - Added support for Azul consensus-layer changes.
All Components
- Fixes & performance improvements.
v0.8.0
What Changed
Important
Recommended upgrade for Base Sepolia and Mainnet node operators to ensure optimal performance and peering reliability.
base-node-reth
- Enhanced Peer Discovery Improved execution-layer peering to facilitate faster initial sync and better stability.
- Flashblocks - Added receipt fields to the
eth_subscribe(newFlashblockTransactions)subscription. - Proof Performance - Significant sync performance optimizations when processing recent blocks.
- General - Various under-the-hood performance improvements and bug fixes.
base-consensus
- Peering Reliability - Refinements to peer discovery logic for more resilient connections.
- Engine API - Added support for WebSocket schemes for Engine RPC connections.
- RPC Throughput - Introduced parallelized RPC query processing with a new configurable concurrency limit.
- General - Stability fixes and performance tuning.
Proofs
- Optimizations - Targeted performance improvements and bug fixes for the proof generation and verification pipeline.
v0.7.6
What's Changed
Note
This release contains a fix to eth_estimateGas for Base Sepolia nodes that have activated Base Azul, as well as a bug fix for websocket engine connections. If you are not impacted by either of these issues, this is an optional update.
- chore(release): set version to 0.7.6 by @github-actions[bot] in #2299
- fix(consensus): Refresh JWT On Every WS Reconnect by @refcell in #2301
- [v0.7.6] fix: implicit gas handling in azul by @danyalprout in #2303
Full Changelog: v0.7.5...v0.7.6
v0.7.5
What's Changed
Note
This release only contains a fix to base-consensus configurable L1 confirmation depth. If you're not setting the BASE_NODE_VERIFIER_L1_CONFS environment variable or specifying the --l1.verifier-confs cli flag, you do not need to upgrade to this release.
- chore(release): set version to 0.7.5 by @github-actions[bot] in #2260
- [backport] fix(consensus): Enforce Verifier L1 Confs In Derivation by @refcell in #2264
Full Changelog: v0.7.4...v0.7.5
v0.7.4
What's Changed
Note
This release contains fixes for base-consensus rpc endpoints to mitigate slow response times on high ingress.
Along with a number of fixes to base-consensus, this release adds a configurable L1 confirmation depth for the verifier derivation pipeline via --l1.verifier-confs cli flag or a BASE_NODE_VERIFIER_L1_CONFS environment variable.
Changelog
- chore(release): set version to 0.7.4 by @github-actions[bot] in #2199
- [backport] fix(consensus): Decouple L1 Query Processing by @refcell in #2203
- [backport] perf(engine-rpc): parallelize RPC query processing (#2189) by @0x00101010 in #2210
- [backport] feat(rpc): add concurrency limit to RPC server (#2190) by @0x00101010 in #2211
- [backport] feat(consensus): Add Verifier L1 Confs by @refcell in #2230
- fix: 0.7.4 build by @refcell in #2233
Full Changelog: v0.7.3...v0.7.4