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.5)
Merge Readiness
- Merge testing continues with Fuzz Testing and Shadow Forking of Goerli
- Hive2 testing system released, Besu being updated to participate
Peering Improvements
- Improve peer discovery speed
- Investigate peer reputation scoring system
- Fix defects on peering
Node Operation Improvements
- Investigate faster scaling to high volume read RPC traffic
Next (up to 22.8)
Modularization of Besu
- Assess various approaches to modularization and investigate each option
- The desired outcome of this work is faster release cycle of Besu, increased adoption of Besu leveraged by composability
EIP Implementation
- EIP-4488 (delayed post-merge)
Client enhancements
- Transaction synchronization optimizations, reduces CPU and Memory use for long-lived transaction pools.
- ETH/66 protocol improvements reducing network traffic.
MEV Besu
The team will be exploring different options for supporting MEV APIs
"Shanghai" Upgrade
First fork after Mainnet, whatever it is called. Bullets are notional until committed to on All-Core-Devs calls.
- Ethereum Object Format support
- Code Segments
- Jump Tables
- New Opcodes
Later (up to 23.2 and beyond)
Optimistic Besu
- The team will be exploring different options for supporting use of the Besu EVM for Optimistic Rollups
EVM Performance
- Continuing work to upgrade the overall performance of the EVM library