The team will follow the testing complexity checklist for the Execution Layer (EL).
Invited everyone to chime in with EIPs they believe should be prioritized.
The testing team will prioritize assessing complexity and begin implementation for key proposals.
If there are Consensus Layer (CL) EIPs needing prioritization, those can also be assessed subsequently.
Raúl Kripalani (Chat):
Offered support from the networking team — happy to assist with reviews, testing, and implementation.
Mario:
Emphasized the goal is to get a sentiment check for Glamsterdam EIP priorities.
Based on impact and community feedback, the team will plan assessment and implementation work.
Ansgar:
Mentioned that initial decisions on prioritized EIPs and DFIs may come during this week’s ACDE call.
Wolovim:
Announced that the Forkcast rank page is back online for client team scoping: https://forkcast.org/rank
lightclient:
Requested more clarity on prioritization, noting there are nearly 10 gas fee EIPs.
Marius:
Suggested it’s best to quickly identify which EIPs to kick or deprioritize first.
Barnabas agreed with this approach.
Mario Vega:
Added that some proposals are under-specified, and it makes sense to exclude those first.
Barnabas:
Asked for a Nethermind-maintained list to help other teams coordinate priorities.
Marc confirmed this will be prepared.
lightclient:
Reiterated that repricing EIPs are a high priority.
Requested stronger testing team signaling to guide client focus.
Ansgar Dietrichs:
Noted that Maria shared a document outlining bundling options for repricing proposals.
The core EIPs in that document should be treated as highest priority within the repricing group.
Fredrik:
Mentioned the Mainnet Upgrade & Incident Response Plan, similar to the Pectra model: Fusaka Mainnet Plan
Encouraged client teams to start identifying coordinators and backup coordinators.
Summary
Barnabas:
Echoed the request for client teams to make PRs to the plan file with coordinator details.
Expressed hope that by Wednesday/Thursday, the plan and coordination list will be complete.
If there is any correction suggestion, please drop a comment here.
The team discussed various technical issues including problems with Prism attestation nodes and incorrect KZG proofs in the network, with fixes being developed for both. Client release plans for the upcoming hard fork were reviewed, with most teams targeting November 5th while some may need additional time, and the team confirmed the December 3rd mainnet fork date. The conversation ended with discussions about testing complexity assessment and incident response planning, including the introduction of a new checklist for EIPs and the identification of primary and backup coordinators.
Click to expand detailed summary
The team discussed recent physical activation activities, including BPO2 and Hudi, noting that Prism encountered issues with struggling attestation nodes. Manu explained that Prism was rejecting attestation from certain nodes, leading to disconnections and loss of peers, and mentioned a fix was being worked on. The team also mentioned that BP01 was expected to go live on Hudi later in the week.
Barnabas inquired about the status of claims release, with Manu confirming it would not be possible by the end of the day due to the need for bug fixes and soaking time. Enrico mentioned discovering incorrect KZG proofs in the network, primarily from Lodestar, and reported that a fix was being worked on, with the team planning to release it in the coming hours.
Barnabas and Enrico discussed an issue with blob sidecars containing incorrect KZG proofs, which were not detected earlier despite the invalid blocks. Enrico noted that changes in logging made the problem more evident and suggested implementing a metric to track rejections on subnets for better detection. Manu added that Lodestar was passing 0.6000 KZG cell proofs, and explained how bad proofs from the execution layer could lead to message rejections and disconnections in Prism, highlighting the need for trust in the execution layer.
The team discussed a bug related to zero proofs, where Manu reported seeing non-Lodestar clients, including Prism, occasionally producing invalid proofs. Enrico and Barnabas agreed this was not a critical issue as affected peers would be disconnected and sidecars not gossiped. Kamil provided an update on gas-submit testing, noting they had switched to 100 mega-gasz blocks for better stability and were working on EST compute scenarios and repricing branches, while facing some issues with Gnosis files.
The team discussed the status of client releases for the upcoming hard fork, with most teams aiming to release by November 5th, though some like Prysm and Lighthouse may need more time. They reviewed test results for BAL v1.3.0, which showed promising progress with most clients passing except Nethermind. The team agreed to stick to the original December 3rd mainnet fork date, with Barnabas requesting all major releases by Thursday’s AllCoreDevs meeting. Mario presented a new Testing Complexity Assessment Checklist for EIPs, which the team will use to prioritize testing efforts, particularly for repricing-related EIPs. Fredrik shared a mainnet upgrade and incident response plan, requesting client teams to identify primary and backup coordinators.
Next Steps:
Manu/Prism team: Fix the attestation bug and complete soaking before releasing
Lodestar team: Fix the KZG proof bug causing zero proofs to be sent over the network
Enrico/Nethermind: Release mainnet version in upcoming hours with KZG proof fix
Barnabas: Check with Lodestar team about zero proof issues on Fusaka 3 devnet
Enrico: Consider implementing metrics to track rejection rates on every subnet to catch similar issues
Kamil/Nethermind: Work on mainnet release and address sync regression
All client teams: Release mainnet clients with Fusaka support by November 5th deadline
All EL client teams: Confirm gas limit is set to 60 million by default in releases
Geth and Besu teams: Signal readiness in Blob Access List chat for Glamsterdam devnet
Stefan: Start Glamsterdam devnet once all client teams signal readiness
Rahul/Testing team: Release new test suite version 1.3.0+ including Coinbase changes
All client teams: Review and test against new consensus specs releases 1.6.0 and 1.6.0 beta 2 for ePBS
Testing team: Prioritize repricing EIPs for complexity assessment
Łukasz/Nethermind team: Share their EIP analysis and prioritization views in publishable form
All client teams: Assign primary and backup coordinators for mainnet upgrade and incident response team
Alex: Merge the mainnet upgrade and incident response team plan into upstream repo
All client teams: Make PRs to add their coordinators to the incident response plan
Parithosh: Reach out to community about gas limit updates once client releases are out