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.

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

Now (up to 22.1)

Merge

  • Testnet participation
    • Hyperledger Besu joined devnet3 mid-december and is now on the long lived kintsugi testnet (read more on how to join Kintsugi with Besu-Teku)

EIPS

  • EIP-4488 (delayed post-merge)
  • add other relevant EIPs

Bonsai tries

  • Bonsai Tries: a new database format which reduces storage requirements and improves performance for access to recent state.

Snapsync

  • Snapsync rebuild the worldstate trie by requesting only the leafs to the peers. The intermediate nodes in the trie will be created locally. By reducing the number of network requests, the synchronization time is significantly accelerated

Client enhancements

  • Performance work - investigation of issues around sync, peering and tracing
  • Vert.X upgrade
  • Tracing APIs implementation

MEV Besu

  • The team will be exploring different options for supporting MEV APIs

Add/Update non-mainnet related roadmap items for Hyperledger Besu

Next (up to 22.7)

Merge 

  • The Merge replaces Ethereum’s Proof-of-Work consensus engine with the Proof-of-Stake Beacon Chain.

Optimistic Besu

  • The team will be exploring different options for supporting use of the Besu EVM for Optimistic Rollups

MEV Besu

  • The team will be exploring different options for supporting MEV APIs

Add/Update non-mainnet related roadmap items for Hyperledger Besu

  • moving onchain-privacy-groups to production status (removing "early access" label)

Later (up to 23.1 and beyond)

Sharding

State Expiry

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

...