Added support for protocol versioning and decline/ accept code implementation
Fixed race condition bug, and merged ping extension PR
Investigating the whoareyou challenge response issue and performance bottlenecks in Go implementation
2. Discussion topics
2.1 Protocol Versioning Implementation
Most of the client teams have started implementing the protocol versioning
Teams are encouraged to implement miniimal versioning to enable incremental updates and compatibility testing
2.2 Ephemeral Headers Spec Update
The problem
The initial assumption that all EL headers could be sourced from LightClientUpdates was invalidated as the CL derives tx/ withdrawal data via SSZ instead of RLP/ MPT
The spec is being updated to
Clarify limitation: EL headers can’t be fully sourced from the Beacon Network
Define handling
Headers should be organized chronologically in payloads
Clients should retain headers during reorgs until chain validity is re-verified
Avoid unnecessary network requests that could case DDOS issue
Allow headers to propagate naturally across the network
Edge cases: Notes added for scenarios like reorgs and data propagation
Next step
Team working on the implementation is encouraged to read the PR link for details
Sepolia testnet: The initial May 1st drop date is now Sepolia testnet drop date, with efforts underway to align an EL client version ready for Sepolia so CL clients can test against
Mainnet drop date: The mainnet drop date is postponed to sync with Pectra upgrade, due to CL’s dependency on pre-merge logs
2.5 State Network Progress
State network rollout has stalled due to
Gossip performance issue: Bottlenecks in propagating new state data across the network
Dependencies: Protocol versioning, accept codes must be finalized first to unblock state sync features
Action plan
Short-term goal: Focus on shipping a client version that can sync state even if it’s slighly behind the head of the chain
Priority:
History network will take precedence over the State network due to higher urgency
Ephemeral state work and performance optimizations may follow later, depending on team availability
Team bandwidth constraints
There will be reduced manpower on Trin side during summer due to vacation/ parental leave
Potentially exploring collaboration with Fluffy team on the State network development
2.6 Hive test status
Two key failures remain unsolved
JSON-RPC extension: Some clients still need to expose required extensions via JSON-RPC
Post-merge proof validation: Minor bug persist in validating post-merge proof formats
Next step
Teams are urged to prioritize these fixes within the next two weeks to get Hive tests fully green, as prolonged failures risk being overlooked