This document represents the current working roadmap for Besu. It is a living document, which will evolve and change over time. In particular the features in later versions are likely to change.
We use the approach of #now, #next, #later used by foursquare, with a slightly different time horizon. Our #now scale is about 3 months, #next about 6 months, and #later is 12+ months.
Now (up to 21.7)
London Hard Fork
The 21.7.0 release of Besu includes full support for the London Hard Fork, which includes the following EIPs
EIP-1559: Fee market change for ETH 1.0 chain
EIP-3198: BASEFEE opcode
EIP-3529: Reduction in refunds
EIP-3541: Reject new contracts starting with the 0xEF byte
EIP-3554: Difficulty Bomb Delay to December 1st 2021
Bonsai Tries: A new database format which reduces storage requirements and improves performance for access to recent state.
QBFT is a Byzantine Fault Tolerant consensus algorithm, building on the capabilities of IBFT and IBFT 2.0. It aims to provide performance improvements in cases of excess round change, and provides interoperability with other EEA compliant clients, such as GoQuorum.
Additional Privacy Modes
GoQuorum-compatible privacy introduces a new restricted privacy mode using Tessera which operates on a single private state.
Next (up to 22.1)
The Merge replaces Ethereum’s Proof-of-Work consensus engine with the Proof-of-Stake Beacon Chain.
We are benchmarking various transaction types and APIs in order to identify bottlenecks and make improvements, in both mainnet and private network modes.
- The team will be exploring different options for supporting use of the Besu EVM for Optimistic Rollups
The team will be exploring different options for supporting MEV APIs
- Permissioning features will be extended to include more granular account permissioning for different transaction and interaction types.