Meeting Summary:
The meeting focused on updates and discussions regarding the status of DevNet environments, particularly DevNet 5 and 6, and related technical challenges. Barnabas reported that DevNet 5 launched version 11.5 but struggled with bugs and unclear root causes for forking issues, with efforts focused on recovery rather than a quick relaunch. The team discussed whether to keep DevNet 5 alive for debugging or relaunch DevNet 6 simultaneously, ultimately deciding to delay both and aim for a relaunch on Wednesday after addressing client bugs and issues. The group reviewed EL and CL specification updates, with Mario noting progress on merging EIP-837 into the main development branch. A significant portion of the meeting addressed EIP-7997 regarding deterministic factory deployment options, with Toni presenting three options and the team generally supporting enshrining the Araknit contract in the Genesis file (option 2) as the preferred approach. The conversation ended with plans for breakout discussions on EL and CL topics, including SSE Engine API implementation and EIP-8037-related issues.
Click to expand detailed summary
The team discussed issues with Amsterdam DevNet 5, which launched version 11.5 but experienced stability problems and client bugs. Barnabas reported that the root cause of forking issues remains unclear, and the team is considering either recovering DevNet 5 or relaunching under DevNet 6. Terence explained that PRISM cannot sync from a finalized checkpoint, and Potuz noted that while colocation whitelisting might be contributing to downscoring, the underlying cause of sync failure is still unclear. The team debated whether to keep DevNet 5 running for 48 hours to allow debugging while simultaneously launching DevNet 6, with Enrico suggesting it might be better to wait a few days to implement fixes across clients before launching a new devnet.
The team decided to delay the relaunch of DevNet 6 by a few days to address client issues and review pending PRs. Barnabas suggested aiming for a relaunch on Wednesday. The group discussed a bug where payloads from Nimbus were not reaching Prism on time, with Enrique suggesting it might be related to empty payloads being rejected. Justin confirmed the decision to relaunch DevNet 6 on Wednesday, and the meeting moved on to discuss EL spec updates.
Mario reported progress on merging EIP-837 into the main development branch and discussed ongoing work on rebasing other branches. Jochem-brouwer inquired about missing EIP-8037 tests in the latest release, which Mario confirmed should be present. The team clarified that the new release would be for DevNet 7 rather than DevNet 6, as Barnabas explained they are relaunching with the same spec as DevNet 5. Etan led a discussion about EIP-7688 regarding stable containers, explaining it’s currently blocking higher gas limits due to deposit request caps, with full implementation only completed by Nimbus and Lodestar so far. The team debated the definition of “stable” for DevNets, with consensus emerging around needing at least a weekend to a week of continuous operation with finalization before adding new features.
The team discussed three options for deploying the deterministic factory, with option 2 (deploying Arachnid contract through Genesis file) being the preferred choice due to simplicity and avoiding gas limit issues caused by EIP-8037. Toni explained that the original Arachnid deployment method using Nick’s method is no longer viable due to increased state gas prices exceeding the fixed 100K gas limit. The group, including EIP author Frangio and Mario, supported option 2, with some suggesting to modify EIP-7997 to enshrine this approach rather than creating a new EIP.
The team decided to conduct breakouts to discuss EIP implementation and sync issues between EL and CL developers. Marius mentioned he is implementing the SSE Engine API in Geth and requested feedback on minor specification changes, noting that both Prysm and Nimbus would be involved in implementation. The group agreed to have Toni lead the EL portion of the breakout discussion on deployments, while Maria would lead discussions on EIP 8037 topics.
Next Steps:
- Barnabas: Relaunch Amsterdam DevNet 6 (now DevNet 7 due to renumbering) on Wednesday with the same spec as DevNet 5, ensuring all client teams have time to merge fixes.
- Barnabas: Keep DevNet 5 alive for an additional 48 hours to allow clients to debug and understand the root cause of the forking issues.
- Potuz: Investigate which peers Prism is downscoring and identify if it is a specific client causing inconsistent payload issues.
- terence: Fix the bug where Prism produces inconsistent payloads with respect to withdrawals when the view changes between empty and full in the middle of a slot, and ensure the fix is pulled into the DevNet branch.
- Barnabas: Enable the P2P colocation whitelist flag in Prism by default for the next DevNet to address peer downscoring due to same-colocation issues.
- Potuz: Investigate the bug where Prism is not receiving payloads produced by Nimbus on time (only requesting them via RPC later), and check if other clients observe similar issues.
- Enrico: Update Nimbus’s side implementation of EIP-7688 (stable containers) and fix identified issues on the EPBS side before the next DevNet.
- Mario: Verify that EIP-8037 tests are included in the latest Glamsterdam test release (EEST v7.2.0) and resolve any inconsistencies.
- Mario: Complete the merge of EIP-8037 into the main development branch and rebase EIP-7997, EIP-2780, and EIP-88 branches on top of the ADT7 branch.
- Toni: Follow up async with Mario and frangio to determine the best path forward for EIP-7997 (either modifying 7997 or drafting a new simple EIP) to enshrine the Arachnid contract into the Genesis file (Option 2).
- Marius: Post proposed minor spec changes as comments on the SSE Engine API EIP/PR for review by other teams.
- Marius: Coordinate with an intern at the Ethereum Foundation to implement the SSE Engine API in Nimbus (and potentially one other CL client).
- Nico: Share the EIP link for the new deposit contract proposal and follow up with EL teams on the required changes to the execution deposit contract.
- Client teams (Teku, Prism, Lighthouse): Continue work on EIP-7688 (stable containers) implementation so it can be included in a future DevNet (DevNet 8) once EPBS is stable.
Recording Access: