Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


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.

Public Roadmap

Enterprise Roadmap


Node Operator Experience

Related releases 24.1.x

- 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 

- Packaged PoS images for Mainnet with neatly integrated CL client

- Revitalized plug-in strategy, technical documentation

Parity with public features

  • QBFT/IBFT2 + Shanghai
  • QBFT & Bonsai DB

Enterprise TX pool

  • --tx-pool=sequenced

Version upgrade/downgrade protection

  • Detect downgrade and prevent without an override


Developer Experience

Related 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

Reduce unnecessary storage

  • Empty-block period

Application limits

  • Configurable max gas per transaction

TX pool control

  • Periodic re-distribution of transactions over a certain age?
  • Administrative actions on TX pool (remove TX)


Prague Fork, Client Evolution

Related 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

  • Besu as an Ethereum reference client in Java
  • Verkle Tries
  • History / State Expiry research 
  • Portal network PoC / EIP-4444

Enterprise oriented releases

  • Profiles for default values etc.