Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 be refined and 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 v1.5)

Performance Improvements

  • Work will be done to improve Besu’s performance across several areas: block propagation, block product and validation, transaction pool management, and JSON RPC query response time. 

Privacy Improvements 

  • APIs to support filtering of private contract events. Onchain privacy group improvements.

Beam Sync Early Access 

  • Work will be done on adding Beam Sync support in Besu. This will allow Besu to sync to the head of a network without downloading the entire network state and then download it on an as-needed basis as it processes incoming blocks. 

[Community Request] Mining Support 

  • Work has begun to add proper mining support in Besu. While it now supports Stratum, there are a handful of transaction pool improvements missing for Besu to be a proper mining client.

Next (v1.6)

Peering Improvements

  • Improving the stability, reliability and performance of the peer-to-peer layer.

Performance benchmarks

  • Performance testing and measurement of private transactions using privacy groups with a private transaction manager.

Support for EIP-1559

  • Change to the transaction fee structure charged on Ethereum Mainnet

Integrate Hive Testing

  • Integrate Hive testing results into the QA process. Hive is an Ethereum Foundation test harness that tests Devp2p, syncing, reference tests, and graphql in a black-box fashion.

Single Trie Data Storage Mode

  • Add a new database storage mode that instead of a multi-trie key-value store it is one trie, one set of indexed leaves, and a series of diffs that can be used to move the trie forwards or backwards.

Future (v1.7+)

In addition to making incremental improvements to the above features, there will be some bigger pieces of work. These are deliberately kept vague at this time, and will be elaborated upon when they move up to the now and next levels of work.

The enterprise roadmap is currently led by Matthew Whitehead from Kaleido. To discuss the enterprise roadmap items reach out to matthew.whitehead on the Hyperledger discord server.



Public Roadmap

Enterprise Roadmap

Now

Node Operator Experience

Related releases 24.1.x

- Bonsai-friendly Archive Mode

- Besu as the Linea client

- Sync improvements, speed & robustness

- Besu as a Snap Sync Server

- Verkle Trie ongoing development

- Cancun delivery, Prague scoping/prep


Related releases 24.4.x

- Public / Private network feature parity (sync!)

- Codebase cleanup for better multi-use-case 

- Packaged PoS images for Mainnet with neatly integrated CL client

- Revitalized plug-in strategy, technical documentation

Reduce unnecessary storage

  • Empty-block period

Bonsai + QBFT support

  • Reduce storage requirements
  • Improve performance

Performance

  • Explore QBFT performance bottlenecks and improvements

Next

Developer Experience

Related releases 24.7.x

- Besu as a customizable L2/L3 sequencer

- Besu on more Layer 2 networks 

- Prague: dev/test/ship

- Verkle Trie ongoing development

- Modularity of the protocol schedule

- Ongoing performance work

Bonsai archive

  • Part of the journey towards Bonsai replacing Forest DB
  • Make Bonsai an option for retrieving state at arbitrary blocks in the chain

Modularity/Enterprise release

  • Release that removes unneccesary features and packages
    • POS
    • POW
    • Tessera? (possibly optional)
    • Public chain profiles
    • ...

Later

Prague Fork, Client Evolution

Related releases 24.10.x

- Prague: dev/test/ship

- Verkle Tries: 

- Light client exploration

- Besu as a customizable L2/L3 sequencer

- Modularity everywhere

- Ongoing performance work

Ongoing Protocol Research

  • Besu as an Ethereum reference client in Java
  • Verkle Tries
  • History / State Expiry research 
  • Portal network PoC / EIP-4444

...

Ethereum 1.x

  • Stateless Clients 

...

Alternate Consensus Mechanisms

...

Privacy group consensus

...

Cross privacy group communication

...