...
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
...
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.
...
Privacy group consensus
...
Cross privacy group communication
...
Onchain privacy
...
21.7)
London Hard Fork
The 21.7.0 release of Besu includes full support for the London Hard Fork, which includes the following EIPs
EIP-1559: Fee market change for ETH 1.0 chain
EIP-3198: BASEFEE opcode
EIP-3529: Reduction in refunds
EIP-3541: Reject new contracts starting with the 0xEF byte
EIP-3554: Difficulty Bomb Delay to December 1st 2021
Bonsai Tries
Bonsai Tries: A new database format which reduces storage requirements and improves performance for access to recent state.
QBFT
QBFT is a Byzantine Fault Tolerant consensus algorithm, building on the capabilities of IBFT and IBFT 2.0. It aims to provide performance improvements in cases of excess round change, and provides interoperability with other EEA compliant clients, such as GoQuorum.
Additional Privacy Modes
GoQuorum-compatible privacy introduces a new restricted privacy mode using Tessera which operates on a single private state.
Next (up to 22.1)
The Merge
The Merge replaces Ethereum’s Proof-of-Work consensus engine with the Proof-of-Stake Beacon Chain.
Performance enhancements
We are benchmarking various transaction types and APIs in order to identify bottlenecks and make improvements, in both mainnet and private network modes.
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.