/
Besu Roadmap & Planning

Besu Roadmap & Planning

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 dmonths, #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 discord server.

 

 

Public Roadmap

Enterprise Roadmap

 

Public Roadmap

Enterprise Roadmap

Now

(3 months)

Related releases 26.1.x - 26.3.x

Glamsterdam Fork

Ongoing performance work 

  • Gas limit - next target is 70Mgas/block

    • Optimizing relevant worst cases identified by benchmarking

  • Block processing

    • Tuweni - incorporate new version into Besu

    • eth/70 which delivers a way to batch block receipts

  • For details, refer to Performance improvements project

Syncing time/memory improvements

Client Evolution

  • Hegota planning/dev

  • discv5 early access

  • History Expiry - 4444 ERA files available

  • Encrypted Mempools

  • Plug-in improvements

  • Removal of enterprise features per sunset plan

  • Codebase cleanup for better multi-use-case

Move QBFT snap sync out of experimental ✅

  • Has been out since 24.7.1

  • Option removed in 25.7.0 (now enabled by default

Bonsai archive ✅

  • Provides equivalent function to FULL sync FOREST DB

  • Available as experimental option in 25.7.0

Faster QBFT recovery ✅

  • Reduces time to recover from losing quorum

  • Available as experimental qbft-enable-early-round-change option since 25.2.0

  • Still fully QBFT compliant

IBFT & QBFT mining beneficiary forks ✅

  • Improves support for paid-gas permissioned chains

  • Available in 25.4.0

IBFT -> QBFT migration ✅

  • Allows migration to industry standard PoA QBFT consensus

  • Available in 25.3.0

Removal of Tessera and native private transaction support ✅

  • Paves the way for more rapid Besu development via a much reduced codebase and fits in with industry direction to app-level privacy solutions

  • Removed in 25.6.0

Bonsai archive with state proofs (WIP - due Q4 2025)

  • Build on PR 7475 to provide proofs for historic state

  • Provides full replacement for FOREST DB

Next

(6 months)

Related releases 26.4.x - 26.12.x

4444s and Statelessness

  • EIP-4444 history expiry

  • Binary Trie ongoing development

Client Evolution

  • Glamsterdam dev/test/ship

  • Hegota dev/test/ship

  • Removal of enterprise features per sunset plan

  • Plug-in improvements

  • Besu on more Layer 2 networks

  • Besu as a customizable L2/L3 sequencer

  • Ongoing performance work

  • Encrypted Mempools

  • Snarkification, RiscV

  • Statelessness - Binary Tree

Modularity work (WIP)

  • Move consensus logic out of core Besu monorepo

  • Allow faster iteration on both core Besu and enterprise Besu features

Move empty block periods out of experimental (WIP)

  • Has been in out since 24.7.1

BFT peering via non-validators

  • Allow edge-of-network nodes that aren’t BFT validators

Enterprise options for history expiry

  • L1 will start dropping block bodies and receipts from 2Q2025

  • Enterprises will need to understand the options Besu provides and the architectures that are available to them

    • Might involve e.g. option to automatically remove blocks and receipts for chainHead-N blocks for non archive, non-full nodes

Later

(12 months)

Related releases 27.m.x

Client Evolution

  • Modularity of the protocol schedule

  • Modularity everywhere

Ongoing Protocol Research

  • Encrypted Mempools

  • Snarkification, RiscV

  • Statelessness - Binary Tree 

Ensure Verkle + Archive has a solution