You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 35 Next »

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 Infrastructure

Related 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 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 

Parity with public features

  • QBFT/IBFT2 + Shanghai
  • QBFT & Bonsai DB

Enterprise TX pool

  • --tx-pool=sequenced

Version upgrade/downgrade protection

  • Detect downgrade and prevent without an override


Next

User & Developer Experience

Related 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

  • Empty-block period

Application limits

  • Configurable max gas per transaction

TX pool control

  • Periodic re-distribution of transactions over a certain age?
  • Administrative actions on TX pool (remove TX)

Later

Prague Fork, Client Evolution

Related 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

  • Besu as an Ethereum reference client in Java
  • Verkle Tries
  • History / State Expiry research 

Enterprise oriented releases

  • Profiles for default values etc.
  • No labels