Written by Matt Nelson with support & input from Maintainers at Consensys and Hedera.
Besu reaching Quorum...
Cancun is just hitting public testnets and Core Devs are setting their sights on Prague, the next EL update to Ethereum. Scoping is underway from the Besu Maintainers and we wanted to share some thoughts. Besu's team is a little different than many client teams in that we are part of the Hyperledger Foundation. We have a set of maintainers that represent themselves and the project, not necessarily their employers. To that end, we wanted to share our team's take on the Prague fork and what we would like to see.
How the sausage is made:
When the decentralized Besu team discusses scope for forks, we like to take a champion-based approach. Maintainers that want to propose or progress scope/EIPs must be the evangelizer, both to the other team members and to the Core Dev community. Below, the champions will break down what they want to see in the next fork and why. Let's get the items we have a complete consensus on out of the way first.
Verkle or Velocity...?
The Besu team is in favor of shipping a Prague fork that excludes Verkle in its current form. This is not to delay Verkle, but to give it more time to bake and for the Besu client to participate in the Kaustinian testnet. We know delaying the transition will cause headaches but view current UX improvements and a more stable transition as paramount. We do want to keep up velocity of shipping improvements on Mainnet and see delaying the next fork to a soft 2025 as unacceptable.
We are the Champions (or, Scope)
In keeping up with velocity, our maintainers propose the following scope...
EOF (Danno)
pros, cons, next steps
EOF (Danno)
pros, cons, next steps
EOF (Danno)
pros, cons, next steps
EOF (Danno)
pros, cons, next steps
EOF (Danno)
pros, cons, next steps
EOF (Danno)
pros, cons, next steps