The Ethereum Foundation Protocol Support team officially disbanded on July 10 on X; the official announcement was brief and did not disclose specific reasons for the dissolution. The team served as a central coordination hub within the Ethereum ecosystem, mainly responsible for organizing and coordinating core developer meetings, tracking network upgrades, supporting EIP advancement, and maintaining daily protocol operations.
EF Protocol Support Disbandment Announcement: No Specific Reasons Disclosed
According to the announcement posted by the Ethereum Foundation Protocol Support team on July 10 on X, the team has officially disbanded; the official statement was concise and did not provide any details regarding the reasons for disbandment, subsequent handover of responsibilities, or which organization will continue related work.
The responsibilities of the Ethereum Protocol Support team included four core functions:
Core Developer Meeting Coordination: Organizing cross-team synchronization meetings before network upgrades.
Network Upgrade Tracking: Monitoring the progress of testnet and mainnet upgrades.
EIP Advancement Support: Assisting in drafting, reviewing, and merging EIP proposals.
Daily Protocol Maintenance: Ensuring the stable daily operation of the Ethereum core protocol.
AI Agent Red Team Testing Discovers libp2p gossipsub Panic Vulnerability, Now Fixed and Disclosed
According to a blog post by the Ethereum Foundation Security team, on the same day the Protocol Support team announced disbandment, the security team released a finding: by deploying AI agents for red team testing on Ethereum-dependent software, they successfully identified a panic vulnerability in the consensus client libp2p gossipsub, numbered CVE-2026-34219; the vulnerability has been fixed and responsibly disclosed.
This event reflects ongoing internal restructuring within the Ethereum Foundation: as the Protocol Support team disbanded, the security team is actively integrating AI tools to enhance detection efficiency, indicating a shift in Ethereum development from manpower-intensive coordination to tool-driven verification.
Frequently Asked Questions
Why did the Ethereum Foundation disband the Protocol Support team?
According to the official announcement on July 10, the wording was brief and did not specify reasons for disbandment; analysis suggests that as Ethereum enters a relatively mature phase (with the Merge completed and Dencun upgrade launched), the need for manpower-intensive cross-team coordination may have decreased.
Who will handle EIP progression and developer meeting coordination after EF Protocol Support disbands?
The current announcement does not specify who will take over these functions; this remains a key concern in the community—how to ensure coordination mechanisms do not fall into a vacuum following the team's dissolution, which awaits further clarification from the Ethereum Foundation.
What is the CVE-2026-34219 vulnerability discovered on the same day?
According to a blog post by the Ethereum Foundation Security team, CVE-2026-34219 is a panic vulnerability in the Ethereum consensus client libp2p gossipsub, discovered through AI agent red team testing, which has been fixed and responsibly disclosed.
