...
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
...
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 - |
...
Bonsai-friendly Archive Mode - Besu as |
...
- Template for other L2 plug-ins, client code
- Linea integration template
- Bonsai: Archive-friendly & storage reductions
- Sync improvements
- Database & IO improvements
Next
Multi-Chain Besu, Flexible Infrastructure
Related releases 23.10.x
- Modular consensus mechanisms via plug-ins
- Tooling & features for infrastructure providers
- Kikori: new feature, trie-log shipping for Bonsai
- Light client infrastructure for near-head scale
- Exploring new sync formats for validators
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
Later
...
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 - Packaged PoS images for Mainnet with neatly integrated CL client - Revitalized plug-in strategy, technical documentation | Reduce unnecessary storage
Bonsai + QBFT support
Performance
|
Next | Developer ExperienceRelated releases 24. |
...
7.x |
...
- Codebase tailored for multi-use case support (Mainnet, private nets, L1/L2s)
- Packaged PoS images for Mainnet with neatly integrated CL client
- 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
|