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 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 20.10 FKA 1.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.

Championing Fee Market Changes

  • Work to get EIP-1559 or an alternative deployed on the Ethereum Mainnet by providing a reference implementation in Besu and coordinating the broader community work around the initiative. 

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. (This is a large task, over multiple quarters.  Some will ship in 20.10, some will ship later.)

IBFT2.0 Improvements

  • Enhancing support for block rewards and transaction fees in gas-charged networks.

Next (21.2/21.3 FKA 1.7)

Berlin Network Upgrade

  • Support for the upcoming network upgrade on the Ethereum Mainnet. 

GoQuorum Interoperability

  • Interoperability with GoQuorum across various functionality such as privacy, IBFT consensus and plugin frameworks. (This is a large task, over multiple quarters.  Some will ship in 21.2, some will ship later.)

Single Trie Data Storage Mode

  • Continuation of the work from the 20.10 release. 

TBA

  • More items to be added to the roadmap in the coming months. If you have a suggestion, you can submit it using the Feature Proposal template. 

Future (21.5+)

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

...

Privacy group consensus

...

Cross privacy group communication

...

Onchain privacy

...