# Geth Glamsterdam Headliner Assessment This is our tier list of EIPs for the Glamsterdam headliner selection. We believe BALs (EIP-7928) are the only viable option for headliner, reasons given below. ### Block-level Access Lists (EIP-7928) This proposal enables parallel tx execution and also has the potential to remove a failure condition in snap sync. Specifically, if implemented in a certain way, BALs can be used to heal the state during sync. This would be a big improvement for the sync user experience and also make the sync time more deterministic. ### Delayed Execution (EIP-7886) This proposal mostly has benefits for the consensus layer. It gives the CL more time to do things within the slot interval. We would like to note that a CL headliner selection of ePBS might make this proposal redundant. On the execution side, we believe the introduction of Delayed Execution may pose unknown risks related to incentives and attacks. The latest version of the EIP, where tx fees are pre-paid by the sender, also seems to have bad effects on user experience. ### Pureth (EIP-7919) This is more of a meta-proposal. Pureth contains some good changes: - New log index (EIP-7745). We are pursuing this as a non-headliner, so we want this in Glamsterdam. - ETH transfer logs (EIP-7708). This is an often-requested feature, and could also be realized in combination with EIP-7745. - Improved receipts format (EIP-6466). An update to receipts merkelization and encoding is overdue, and we feel this EIP sets a good direction. Overall, we don't agree with the bundling of all the changes into a headliner. The individual EIPs in the proposal should be assessed independently. ### EOF / EVM64 We don't want to pursue these proposals for Glamsterdam.
Last changed by  
 
Felix Lange
187

Read more

Ideas for rollup-geth integration into upstream

Date: 2025-04-07 In this document, I'd like to lay out some of the ideas for L2 forks of go-ethereum to work with the upstream code. At a high level, what we want to achieve is that L2 projects can use go-ethereum as upstream and have kind of a good time. Conflicts from upstream changes, especially larger ones, should be minimized. Common features across L2s, and even L2 common core features, should be implemented directly in the upstream where possible. L2 project authors should be able to collaborate via the upstream. What to do about rollup-geth, the repository The existing rollup-geth project at https://github.com/NethermindEth/rollup-geth has some features merged and others implemented as PRs. We won't just merge their project directly into upstream. We will need to collaborate with the rollup-geth development team in order to schedule submission and review of each change into upstream on an individual basis, and this process should also take into account the perspective of the intended consumers of rollup-geth, the L2 downstream projects. As such, we will have calls with these actors over a longer period of time in order to figure out the sequence of changes.

4/8/2025
State of the RPC Standardization Process (01/2025)

This document is a bit of a brain dump of the RPC Standardization problem space. Mostly just posting this for discussion purposes, and also as an intro for people who aren't familiar with the space. There are some solution pointers at the end. If you are familiar with Ethereum's RPC, you may want to skip to that. The Spec The canonical Ethereum JSON-RPC specification is at https://github.com/ethereum/execution-apis The spec uses the OpenRPC format. After a lot of work over the last year or so, it's pretty comprehensive and covers most methods that can be relied on by users.

1/13/2025
Untitled

Geth Position on EIP-4488 This document summarizes our (the geth team's) position on EIP-4488. We are against the inclusion of this EIP in a fork before the merge. EIP-4488 is a tweak to the economic balance of Ethereum. It does not enable anything that's currently impossible, the change just makes it more economically feasible. Such a change should not be hastily implemented ahead of an already scheduled major fork. Technical Concerns Decreasing the costs of data-heavy transactions will make typical Ethereum transactions

12/10/2021
Read more from Felix Lange
Published on HackMD