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.
Public Roadmap | Enterprise Roadmap | |
---|---|---|
Now | Multi-Chain Besu, Flexible InfrastructureRelated releases 23.10.x - Modular consensus mechanisms via plug-ins* - Fleet: new feature, trie-log shipping for Bonsai - Light client infrastructure for near-head scale - Sync: new formats for validators, snap server - Bonsai-friendly Archive* * May be delayed Modularization of BesuThe goal is to shorten release cycle of Besu, increased adoption of Besu leveraged by composability
| Parity with public features
Enterprise TX pool
Version upgrade/downgrade protection
|
Next | User & Developer ExperienceRelated releases 24.1.x - Codebase tailored for multi-use case support (Mainnet, private nets, L1/L2s) - Packaged PoS images for Mainnet with neatly integrated CL client - Revitalized plug-in strategy, technical documentation | Reduce unnecessary storage
Application limits
TX pool control
|
Later | Prague Fork, Client EvolutionRelated releases 24.4.x - Prague: EOF dev/test/ship - Verkle Tries: prototype - Bonsai adaptation for Verkle, full light client exploration - Besu as a customizable L2/L3 sequencer Ongoing Protocol Research
| Enterprise oriented releases
|