The post Ethereum’s peer-to-peer backbone faces open-source funding gap appeared on BitcoinEthereumNews.com. Shipyard, a key maintainer of libp2p — the peer-to-peer networking stack underpinning Ethereum and dozens of other networks — will cease support for its Go and JavaScript implementations by Sept. 30, citing resource constraints.  In a blog post, the team confirmed it is “working to transition stewardship to the community.” Libp2p is the backbone of Ethereum’s peer-to-peer networking layer, providing the protocol suite that consensus clients use to discover peers, exchange messages, and propagate blocks and attestations across the network. Ethereum clients rely on libp2p’s Gossipsub pub/sub protocol to rapidly broadcast new blocks and validator votes, a process that must complete within strict slot deadlines to keep the chain running smoothly. The status quo is “against good engineering practice,” according to MIT professor and Optimum co-founder Muriel Médard, who has developed a drop-in, API-compatible replacement for Gossipsub, called OptimumP2P (mumP2P). “The thing is, if you hardwire something that does not need to be hardwired, you create fragility and dependence,” Médard told Blockworks. Tea Protocol presents one possible answer to funding conundrums such as this, within the open-source software community. Tea is a blockchain-based system that maps open-source dependencies, ranks projects by criticality, and routes token rewards and security bounties to maintainers to ensure long-term, sustainable support, per Tea co-founder Max Howell, creator of Homebrew. While the ecosystems that rely on libp2p are mobilizing around a transition for the software, in the short term there’s a risk of a slowdown in triaging bugs or security issues, amid the loss of Shipyard’s institutional knowledge. “The incentives aren’t really there for open source maintainers to care enough about security,” Howell told Blockworks, noting that, today, open-source software is more than “a public good,” and rather “fundamental infrastructure.” Timothy Lewis, Tea’s co-founder, said libp2p “sits in what we consider the protocol ranking graph —… The post Ethereum’s peer-to-peer backbone faces open-source funding gap appeared on BitcoinEthereumNews.com. Shipyard, a key maintainer of libp2p — the peer-to-peer networking stack underpinning Ethereum and dozens of other networks — will cease support for its Go and JavaScript implementations by Sept. 30, citing resource constraints.  In a blog post, the team confirmed it is “working to transition stewardship to the community.” Libp2p is the backbone of Ethereum’s peer-to-peer networking layer, providing the protocol suite that consensus clients use to discover peers, exchange messages, and propagate blocks and attestations across the network. Ethereum clients rely on libp2p’s Gossipsub pub/sub protocol to rapidly broadcast new blocks and validator votes, a process that must complete within strict slot deadlines to keep the chain running smoothly. The status quo is “against good engineering practice,” according to MIT professor and Optimum co-founder Muriel Médard, who has developed a drop-in, API-compatible replacement for Gossipsub, called OptimumP2P (mumP2P). “The thing is, if you hardwire something that does not need to be hardwired, you create fragility and dependence,” Médard told Blockworks. Tea Protocol presents one possible answer to funding conundrums such as this, within the open-source software community. Tea is a blockchain-based system that maps open-source dependencies, ranks projects by criticality, and routes token rewards and security bounties to maintainers to ensure long-term, sustainable support, per Tea co-founder Max Howell, creator of Homebrew. While the ecosystems that rely on libp2p are mobilizing around a transition for the software, in the short term there’s a risk of a slowdown in triaging bugs or security issues, amid the loss of Shipyard’s institutional knowledge. “The incentives aren’t really there for open source maintainers to care enough about security,” Howell told Blockworks, noting that, today, open-source software is more than “a public good,” and rather “fundamental infrastructure.” Timothy Lewis, Tea’s co-founder, said libp2p “sits in what we consider the protocol ranking graph —…

Ethereum’s peer-to-peer backbone faces open-source funding gap

2025/09/20 01:18

Shipyard, a key maintainer of libp2p — the peer-to-peer networking stack underpinning Ethereum and dozens of other networks — will cease support for its Go and JavaScript implementations by Sept. 30, citing resource constraints. 

In a blog post, the team confirmed it is “working to transition stewardship to the community.”

Libp2p is the backbone of Ethereum’s peer-to-peer networking layer, providing the protocol suite that consensus clients use to discover peers, exchange messages, and propagate blocks and attestations across the network. Ethereum clients rely on libp2p’s Gossipsub pub/sub protocol to rapidly broadcast new blocks and validator votes, a process that must complete within strict slot deadlines to keep the chain running smoothly.

The status quo is “against good engineering practice,” according to MIT professor and Optimum co-founder Muriel Médard, who has developed a drop-in, API-compatible replacement for Gossipsub, called OptimumP2P (mumP2P).

“The thing is, if you hardwire something that does not need to be hardwired, you create fragility and dependence,” Médard told Blockworks.

Tea Protocol presents one possible answer to funding conundrums such as this, within the open-source software community. Tea is a blockchain-based system that maps open-source dependencies, ranks projects by criticality, and routes token rewards and security bounties to maintainers to ensure long-term, sustainable support, per Tea co-founder Max Howell, creator of Homebrew.

While the ecosystems that rely on libp2p are mobilizing around a transition for the software, in the short term there’s a risk of a slowdown in triaging bugs or security issues, amid the loss of Shipyard’s institutional knowledge.

“The incentives aren’t really there for open source maintainers to care enough about security,” Howell told Blockworks, noting that, today, open-source software is more than “a public good,” and rather “fundamental infrastructure.”

Timothy Lewis, Tea’s co-founder, said libp2p “sits in what we consider the protocol ranking graph — the layer of active protocols and standards that underpin ecosystems like Ethereum.”

Tea tracks the relative importance of code through a system called tea rank, based on package manager data, and is now “leaning into graphing those protocols” as well, Lewis added.

Alternatives brewing

Optimum’s alternative, mumP2P, provides a libp2p-like pub-sub interface while using Random Linear Network Coding (RLNC) to remove Gossipsub’s redundancy and latency.

Médard said Gossipsub “slows down under stress,” and that propagation bottlenecks are now a key limiter for Ethereum scaling. By contrast, mumP2P is able to send “equations” rather than repeated messages, resulting in much lower latency — though it’s still in testing.

For now, libp2p’s future hinges on a new wave of community maintainers, including those from within crypto. Whether protocols like Tea can deliver durable funding for unglamorous maintenance work remains to be seen.  

“Our mainnet is just around the corner,” Lewis said. “This is how we ensure the protocols at the heart of Web3 aren’t left behind, but are sustainably supported for the long term.”


Get the news in your inbox. Explore Blockworks newsletters:

Source: https://blockworks.co/news/ethereums-peer-to-peer-backbone

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.

You May Also Like

Google's AP2 protocol has been released. Does encrypted AI still have a chance?

Google's AP2 protocol has been released. Does encrypted AI still have a chance?

Following the MCP and A2A protocols, the AI Agent market has seen another blockbuster arrival: the Agent Payments Protocol (AP2), developed by Google. This will clearly further enhance AI Agents' autonomous multi-tasking capabilities, but the unfortunate reality is that it has little to do with web3AI. Let's take a closer look: What problem does AP2 solve? Simply put, the MCP protocol is like a universal hook, enabling AI agents to connect to various external tools and data sources; A2A is a team collaboration communication protocol that allows multiple AI agents to cooperate with each other to complete complex tasks; AP2 completes the last piece of the puzzle - payment capability. In other words, MCP opens up connectivity, A2A promotes collaboration efficiency, and AP2 achieves value exchange. The arrival of AP2 truly injects "soul" into the autonomous collaboration and task execution of Multi-Agents. Imagine AI Agents connecting Qunar, Meituan, and Didi to complete the booking of flights, hotels, and car rentals, but then getting stuck at the point of "self-payment." What's the point of all that multitasking? So, remember this: AP2 is an extension of MCP+A2A, solving the last mile problem of AI Agent automated execution. What are the technical highlights of AP2? The core innovation of AP2 is the Mandates mechanism, which is divided into real-time authorization mode and delegated authorization mode. Real-time authorization is easy to understand. The AI Agent finds the product and shows it to you. The operation can only be performed after the user signs. Delegated authorization requires the user to set rules in advance, such as only buying the iPhone 17 when the price drops to 5,000. The AI Agent monitors the trigger conditions and executes automatically. The implementation logic is cryptographically signed using Verifiable Credentials (VCs). Users can set complex commission conditions, including price ranges, time limits, and payment method priorities, forming a tamper-proof digital contract. Once signed, the AI Agent executes according to the conditions, with VCs ensuring auditability and security at every step. Of particular note is the "A2A x402" extension, a technical component developed by Google specifically for crypto payments, developed in collaboration with Coinbase and the Ethereum Foundation. This extension enables AI Agents to seamlessly process stablecoins, ETH, and other blockchain assets, supporting native payment scenarios within the Web3 ecosystem. What kind of imagination space can AP2 bring? After analyzing the technical principles, do you think that's it? Yes, in fact, the AP2 is boring when it is disassembled alone. Its real charm lies in connecting and opening up the "MCP+A2A+AP2" technology stack, completely opening up the complete link of AI Agent's autonomous analysis+execution+payment. From now on, AI Agents can open up many application scenarios. For example, AI Agents for stock investment and financial management can help us monitor the market 24/7 and conduct independent transactions. Enterprise procurement AI Agents can automatically replenish and renew without human intervention. AP2's complementary payment capabilities will further expand the penetration of the Agent-to-Agent economy into more scenarios. Google obviously understands that after the technical framework is established, the ecological implementation must be relied upon, so it has brought in more than 60 partners to develop it, almost covering the entire payment and business ecosystem. Interestingly, it also involves major Crypto players such as Ethereum, Coinbase, MetaMask, and Sui. Combined with the current trend of currency and stock integration, the imagination space has been doubled. Is web3 AI really dead? Not entirely. Google's AP2 looks complete, but it only achieves technical compatibility with Crypto payments. It can only be regarded as an extension of the traditional authorization framework and belongs to the category of automated execution. There is a "paradigm" difference between it and the autonomous asset management pursued by pure Crypto native solutions. The Crypto-native solutions under exploration are taking the "decentralized custody + on-chain verification" route, including AI Agent autonomous asset management, AI Agent autonomous transactions (DeFAI), AI Agent digital identity and on-chain reputation system (ERC-8004...), AI Agent on-chain governance DAO framework, AI Agent NPC and digital avatars, and many other interesting and fun directions. Ultimately, once users get used to AI Agent payments in traditional fields, their acceptance of AI Agents autonomously owning digital assets will also increase. And for those scenarios that AP2 cannot reach, such as anonymous transactions, censorship-resistant payments, and decentralized asset management, there will always be a time for crypto-native solutions to show their strength? The two are more likely to be complementary rather than competitive, but to be honest, the key technological advancements behind AI Agents currently all come from web2AI, and web3AI still needs to keep up the good work!
Share
PANews2025/09/18 07:00