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 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
Extended Permissioning
- Permissioning features will be extended to include more granular account permissioning for different transaction and interaction types.