Versions Compared

Old Version 27

changes.mady.by.user Matt Nelson

Saved on

compared with

New Version Current

changes.mady.by.user Matthew Whitehead

Saved on

Key

  • 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.

Now (up to 23.1)

"Shanghai" Upgrade

First fork after Mainnet, whatever it is called. Bullets are notional until committed to on All-Core-Devs calls.

  • Withdrawals from the beacon chain 

Client enhancements

  • Shanghai devnets & Zhejiang testnet
  • Staking withdrawals in Besu
  • EOF (delayed, feature complete)
  • Execution performance
  • Bonsai Stability (bug fixes & auto-heal)

Later (up to 23.4 and beyond)

Cancun Upgrade

  • EIP-4488 - Sharding 
  • Ethereum Object Format support
    • Code Segments
    • Jump Tables
    • New Opcodes

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 

Optimistic Besu

  • The team will be exploring different options for supporting use of the Besu EVM for Optimistic Rollups

Proof of Stake Enhancements

...

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 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

Reduce unnecessary storage

  • Empty-block period

Bonsai + QBFT support

  • Reduce storage requirements
  • Improve performance

Performance

  • Explore QBFT performance bottlenecks and improvements

Next

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

Bonsai archive

  • Part of the journey towards Bonsai replacing Forest DB
  • Make Bonsai an option for retrieving state at arbitrary blocks in the chain

Modularity/Enterprise release

  • Release that removes unneccesary features and packages
    • POS
    • POW
    • Tessera? (possibly optional)
    • Public chain profiles
    • ...

Later

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