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.

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.

Now (up to v1.4)

Multi Tenancy

• Multi-tenancy allows multiple participants to use the same Besu and Orion node. Each participant is called a Tenant, and the Operator is the owner of the Besu and Orion node.

Private State Migration

• Hyperledger Besu v1.4 implements a new data structure for private state storage that is not backwards compatible. A migration will be performed when starting v1.4 for the first time to reprocess existing private transactions and re-create the private state data in the v1.4 format. If you have existing private transactions, see migration details.

End-to-End TLS Support

• Besu now supports TLS connections with both Orion, its private transaction manager, and EthSigner, its transaction signer. 

New Tracing API

• New tracing APIs are being added to Besu to support Parity-style traces. As of 1.4, trace_replayBlockTransactions, was added, with support for the trace, vmTrace and stateDiff options. trace_block and trace_transaction will be added next. 

Plugins API

• Besu now has an exposed Plugins API which allows anybody to build Java plugins to extend Hyperledger Besu.
  

Better NAT Support 

• Besu now automatically detects Docker NAT settings from inside a container. Similar functionality for Kubernetes clusters will be added next. 

Tuweni Bytes Library Support 

• Besu has moved from an internal Bytes library to the Apache Tuweni Bytes library. This includes using the library in the Plugins API interfaces.

Next (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 

...

Future (v1.6+)

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.

...

Ethereum 1.x

• Stateless Clients 

...

Alternate Consensus Mechanisms

...

Privacy group consensus

...

Cross privacy group communication

...