The Ethereum Foundation’s EF Protocol Support team officially announced its dissolution on X on July 10; the official statement was brief and did not reveal specific reasons for the breakup. The team is the coordination hub of the Ethereum ecosystem, mainly responsible for organizing and coordinating meetings among core developers, tracking network upgrades, providing support for the advancement of EIPs, and maintaining the day-to-day execution of the protocol.
EF Protocol Support Dissolution Announcement: Official Did Not Disclose Specific Reasons
Based on the announcement posted on X by the Ethereum Foundation’s protocol support team on July 10, the team has officially been dissolved. The official wording was brief and provided no details regarding the reasons for dissolution, any handover arrangements for subsequent responsibilities, or which organization would continue to推进 relevant work.
The responsibilities of the Ethereum protocol support team include the following four core functions:
Core Developer Meeting Coordination: Organizing cross-team synchronization meetings among Ethereum development teams ahead of network upgrades
Network Upgrade Tracking: Monitoring the status and progress of upgrades across testnets and the mainnet
EIP Advancement Support: Assisting with the drafting, review, and merging process of EIP proposals
Daily Protocol Execution and Maintenance: Ensuring the stable day-to-day operation of Ethereum’s core protocols
AI Agent Red-Team Testing Finds a libp2p gossipsub Panic Vulnerability, Now Fixed and Disclosed
According to a blog post by the Ethereum Foundation’s protocol security team, on the same day the protocol support team announced its dissolution, the security team published a result: by deploying AI agents to conduct red-team testing on software that Ethereum depends on, it successfully identified a panic vulnerability in the consensus client libp2p gossipsub, numbered CVE-2026-34219. The vulnerability has been fixed and responsible disclosure has been completed.
This incident reflects that resources within the Ethereum Foundation are being reorganized: while the protocol support team was dissolved, the security team was actively introducing AI tools to improve detection efficiency, indicating a trend in Ethereum development shifting from people-intensive coordination to tool-driven verification.
Frequently Asked Questions
Why did the Ethereum Foundation dissolve the protocol support team?
According to the Ethereum Foundation’s official announcement on July 10, the statement was brief and did not provide specific reasons for the dissolution; analysis suggests that as Ethereum entered a relatively mature stage (the Merge has been completed, and the Dencun upgrade is already live), the demand for labor-intensive cross-team coordination may have decreased.
After EF Protocol Support was dissolved, who is responsible for EIP advancement and developer meeting coordination?
Based on the current announcements, the official has not disclosed any handover arrangements for those responsibilities. This is the most关注 question in the industry right now—how to ensure the coordination mechanism does not fall into a vacuum due to the team’s dissolution, and further clarification from the Ethereum Foundation is still needed.
What is the CVE-2026-34219 vulnerability discovered on the same day?
According to the Ethereum Foundation’s protocol security team blog post, CVE-2026-34219 is a panic vulnerability in Ethereum’s consensus client libp2p gossipsub. It was discovered through AI agent red-team testing, has been fixed, and responsible disclosure has been completed.
