...
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 | Enterprise Roadmap | |
---|---|---|
Now |
Node Operator ExperienceRelated releases |
24. |
1.x - |
- Fleet: new feature, trie-log shipping for Bonsai
- Light client infrastructure for near-head scale
- Sync: new formats for validators, snap server
- Bonsai-friendly Archive*
* May be delayed
Modularization of Besu
The goal is to shorten release cycle of Besu, increased adoption of Besu leveraged by composability
- Besu modules for Rollups & L2s
- Modularize existing multi-use-case for better long term support of public and private networks
- (Later) Support for more chains and environments via Besu modules
Parity with public features
- QBFT/IBFT2 + Shanghai
Enterprise TX pool
- --tx-pool=sequenced
Version upgrade/downgrade protection
- Detect downgrade and prevent without an override
Next
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 |
User & Developer Experience
Related releases 24.1.x
- Codebase tailored for multi-use case support (Mainnet, private nets, L1/L2s)- Packaged PoS images for Mainnet with neatly integrated CL client - Revitalized plug-in strategy, technical |
documentation | Reduce unnecessary storage
|
Application limits
- Configurable max gas per transaction
TX pool control
Bonsai + QBFT support
Performance
| ||
Next | Developer ExperienceRelated 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
Modularity/Enterprise release
|
Later | Prague Fork, Client EvolutionRelated 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
|
Enterprise oriented releases
Profiles for default values etc.
|