## Erigon Team’s perspective on Glamsterdam Headliners

This article illuminates Erigon team’s view on what should be a part of Glamsterdam and beyond. But before actually “choosing” the headliner proposal(s), we identify the general directions that we deem Ethereum take and also the ones that is currently trending. 

## The Goals

Broadly speaking, it has been highlighted multiple times that Scalability, Decentralization, Privacy and User experience are our main pillars, among others. In that respect, we identify the following ongoing work:

1. Performance enhancements in client implementation, and a roadmap for much higher throughput 
2. Improving L2 data availability with Blobs
3. Integration with ZK tech and ZKVM implementations
4. Better UX with features like Account Abstraction, FOCIL,  Code-size improvements
5. Alternative cryptographic primitives and implementations for better performance and post-quantum enablement

For the client teams with limited bandwidth, shipping everything in a fork is often resource intensive and bug-prone. So, in recent forks we have been choosing our focus and building decentralized social consensus on what goes in the next one.

## Current Headliners 

Our preferences for the current list of proposals as follows

| EIP | Preference | Notes |
| --- | --- | --- |
| EIP-7732: ePBS | NO | - Currently doesn’t fit with the overall goals<br>- We need more deliberations about what to do with MEV |
| EIP-7805: FOCIL | YES | - Aligned with Ethereum’s values |
| EIP-7782: Reduce Block Latency | YES | - Improves UX <br> - Interferes with scaling goals in terms of Block size<br>- Global mempool latency is a concerm: most relays/builders concentrated in EU |
| EIP-7928 – Block-level Access Lists (BALs)<br> | YES | - Improves scalability<br>- Simple to implement with future expansion in mind |
| EOF Bundle| Weak Yes | - Paves the path for better integration with ZKVMs<br>- Is susceptible to social consensus fallout |
| EVM64 | NO | - Improvments may not be that much<br>- Too early to reach a social consensus |

<br>

## Continuing Work

We look forward to solving more bottlenecks to performance and enable ZK, statelessness and account abstraction. In that regard, we hope to see more EIPs for Glamsterdam and beyond that are more aligned to the core goals and take them head-on. The domain of ZK is still progressing and a push from client teams is necessary to direct it properly.

Further, slot re-structuring without enshrined payload separation may be a better way forward