v0.15.2

What's Changed

Note

Fixes a small bug in base-consensus where the L2_ENGINE_RPC_URL didn't support websocket urls. Now, both ws:// and wss:// prefixed urls are supported by base-consensus.

Update Base to 0.7.3 in #1021.

Full Changelog: v0.15.1...v0.15.2

v0.15.1

Breaking Changes (same as v0.15.0)

Important

Node operators must upgrade Base Sepolia nodes to use base-node-reth and base-consensus by 20th April. See here for more information.

The default consensus layer client is now base-consensus. Geth and Nethermind will no longer be supported starting with Base v1.

Action required:

• Configure new BASE_NODE environment variables (see example env files)
• To temporarily opt out, set USE_BASE_CONSENSUS=false

Changes

• Switch all entrypoints to use base-consensus authentication (#1001)
• Add legacy OP node flag (#1002)

Full Changelog: v0.15.0...v0.15.1

v0.15.0

What Changed

Important

Node operators must upgrade Base Sepolia nodes to use base-node-reth and base-consensus by 20th April. See here for more information.

Client Updates

• Base v0.5.1 to v0.7.0: diff
• Nethermind 1.36.0 to 1.36.2: diff
• op-geth v1.101609.1 to v1.101702.0: diff
• op-node v1.16.7 to v1.16.11: diff

v0.14.9

Warning

This is a recommended release for Base Geth Nodes

• Node Client Updates
  op-geth - v1.101609.1: diff
  optimism - op-node/v1.16.7: diff

Full Changelog: v0.14.8...v0.14.9

v0.14.8

❗ Critical bug fix for Base Reth Node Operators

This release contains base reth v0.5.1 which fixes race condition between canonical & flashblock propagation, missing RPC fields and ws subscription.

What's Changed

• chore: remove unused op-reth repo by @meyer9 in #981
• feat: support proofs ExEx by @meyer9 in #980
• chore: updated base-reth to 0.5.1 by @github-actions[bot] in #969

Full Changelog: v0.14.7...v0.14.8

v0.14.7

Note

Fixes a regression in eth_subscribe for Flashblock data. This is a recommended release for node operators running 0.4.0 and an optional release for those running 0.3.1.

• Node Client Updates
  • Base v0.4.0 to v0.4.1

Full Changelog: v0.14.6...v0.14.7

v0.14.6

Note

Recommended but optional upgrade for Base Node Reth

• Node Client Updates
  • Base v0.3.1 to v0.4.0

v0.14.5

Warning

Contains breaking changes to the Flashblock Websocket APIs introduced in the Base client in v0.14.4

• Node Client Updates
  • Base v0.3.0 to v0.3.1
  • Nethermind v 1.35.3 to 1.36.0
  • Geth v1.101603.5 to v1.101608.0
  • OP Node v1.16.2 to v1.16.6
  • OP Reth v1.9.3 to v1.10.2

Full Changelog: v0.14.4...v0.14.5

v0.14.4

Warning

For node operators that run Base Reth Nodes with Flashblocks enabled this is a mandatory change and must be deployed by 6th February for both Base Sepolia and Base Mainnet.

New RPCs

Note

These features are only supported in Base Reth

• base_transactionStatus - lookup whether a transaction is present in the mempool
• eth_subscribe - updated to support Flashblocks
  * pendingLogs: stream of logs from transactions in Flashblocks
  * newFlashblockTransactions: stream of transaction hashes that are included in the block
  * newFlashblocks: stream the pending block as new Flashblocks arrive

Other Changes

• Base Reth
  • Flashblock bug fixes and performance improvements
• Nethermind, Geth
  • No changes

Full Changelog: v0.14.3...v0.14.4

v0.14.3

❗ Mandatory update for Base Mainnet nodes to support the Jovian upgrade on December 2nd.

Operators of Base Mainnet nodes must upgrade to this release before December 2nd at UTC 16:00:01 UTC (unix timestamp 1764691201).

⚠️ Breaking Changes (same as v0.14.1)

Similar to v0.14.1 which was a mandatory upgrade for Base Sepolia node operators, this release also contains the following change and will be applied to mainnet node operators now as well.

op-reth Binary Removed, Consolidated into base-reth-node

The separate op-reth binary has been removed and is no longer available.

All functionality previously provided by op-reth has been consolidated into the existing base-reth-node binary.

• Impact: If your deployment or scripts explicitly called the op-reth binary, you must update them to call base-reth-node instead.
• Parameters & Operation: The base-reth-node binary is designed to be identical in its command-line parameters and operational behavior to the removed op-reth. No parameter changes should be necessary other than the binary name itself.
• Reasoning: This consolidation allows us to more easily introduce and manage Base-specific features within a single, unified client binary.

What's Changed

• chore: updated node-reth, reth by @github-actions[bot] in #661

Full Changelog: v0.14.2...v0.14.3