...
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
Cancun Fork & Rollups Experience
Related releases 23.7.x
- Cancun: EIP-4844 dev/test/ship
- Besu as an L2 client
- 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
...
- Modular consensus mechanisms via plug-ins*
- Tooling & features for infrastructure providers- KikoriFleet: new feature, trie-log shipping for Bonsai
- Light client infrastructure for near-head scale
- Exploring Sync: new sync 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
...
Next
User & Developer Experience
...
- Revitalized plug-in strategy, technical documentation
Later
Prague Fork, Client Evolution
...