A public statement will be issued explaining the upcoming change.
MEV-Boost (Get Payload API)
Teams were using version 2 prior to Fusaka activation.
Question raised:
➝ Is there consistent behavior across all clients using v2?
- Prysm believes they’re aligned post-fork but will confirm.
- nflaig: Switching occurs at fork boundary.
- Bharath to give additional clarification in the Discord thread
Pari: Expects steady MEV blocks to resume.
Holesky End-of-Life
Announcement: Holesky will reach End Of Life at the end of this month.
Fusaka devnet status updates
Devnet 3 has been running non-finality tests for the past 2–3 days; it is successfully recovered.
Some nodes experienced disk exhaustion again.
Planning another network split test using the Sunnyside Labs tool.
The team discussed updates on the Holsky fork and BP01 launch, addressing various technical issues including node reorganization rates and a Nethermind bug, while noting that most clients will switch to V2 at the fork boundary despite MEV relays’ support discontinuation. They reviewed progress on non-finality testing and upcoming maintenance for both Holsky and Fusaka testnets, including discussions on gas limits, scaling, and block-level access list specifications. The team concluded with plans for a breakout call to address trusted payments and agreed to improve application-focused testing and weekly Hive RPC reporting.
Click to expand detailed summary
The team discussed updates on the Holsky fork and the upcoming BP01 launch, noting a higher reorg rate on Lighthouse nodes that will be addressed in the next release. They also addressed a Nethermind bug and discussed changes to the blob sidecar endpoint, with Pawan raising questions about the KZG proof field. The team confirmed that most clients switch to the V2 version at the fork boundary, and Parithosh mentioned that MEV relays have stopped supporting Holsky, though this should not affect Sepolia and Goerli. Finally, they noted that Holsky is officially EOL at the end of the month, and there was a brief mention of nonfinality testing and disk space issues on some nodes.
The team discussed updates on Holsky and Fusaka testnets, including a successful non-finality testing period and upcoming maintenance. They addressed issues with gas limits, scaling, and MEV workflows, with Besu reporting progress on a 60 million gas implementation. The group reviewed block-level access list specifications and testing progress, noting that Reth and Geth are passing most current tests. They also discussed ePBS implementation and planned a breakout call for Friday to address trusted payments. Finally, they agreed to update the weekly Hive RPC pass/fail rate reporting and to coordinate on improving application-focused testing.
Next Steps:
Lighthouse team to release a fix for the higher reorg rate issue in the next release.
Client teams to check with the attesting team to add support for the new GetBlobs endpoint.
Client teams to put out a statement about the API change for GetBlobs endpoint.
Pawan to find and share the thread about GetPayloadv2 endpoint usage.
Besu team to freeze implementation of 60 million gas limit by tomorrow and start fuzzing and testing.
Carlos and team to work with EAST on orchestrating the framework for stateful tests this week.
Client teams to push block-level access list code to a branch called “BAL DevNet0” on their main repositories.
Client teams to attend the ePBS breakout call on Friday to discuss trusted payments and other details.
Client teams to create a branch called “ePBS devnet0” on their main repositories for automation.
Bharath to create a list on Discord showing how each client is implementing GetPayloadv2 for consistency.