The Zenhub has up-to-date Epics that Besu development is targeting over various releases. See the roadmap tab on the Public Zenhub here: https://app.zenhub.com/workspaces/hyperledger-besu-61fc06f457da1c0017f6347d/roadmap
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 23.1)
"Shanghai" Upgrade
- Withdrawals from the beacon chain
- New Push0 op-code and gas costing changes
Client enhancements
- Shanghai devnets & Zhejiang testnets
- Execution performance improvements
- Bonsai Stability Refactor (new format, bug fixes, & auto-heal)
- RPC enhancements and improvements (streaming, accuracy/bug fixes, memory usage)
Later (up to 23.4 and beyond)
Cancun Upgrade
- EIP-4844 - Sharding and data availability sampling first steps
- Ethereum Object Format support
- Code Segments
- Jump Tables
- New Opcodes
- New op-codes and gas optimizations
Modularization of Besu
The goal is to shorten release cycle of Besu, increased adoption of Besu leveraged by composability
- Besu modules for Rollups & L2s
- Modularize existing multi-use-case for better long term support of public and private networks
- (Later) Support for more chains and environments via Besu modules
Optimistic Besu
- The team will be exploring different options for supporting use of the Besu EVM for Optimistic Rollups
Proof of Stake Enhancements
- Packaged Proof of Stake Images for Mainnet with cleaner code and integrated Consensus layer capabilities
Ongoing Protocol Research
- Besu as an Ethereum reference client in Java
- Verkle Tries
- History / State Expiry research