Update on go-libp2p maintenance

[aschmahmann]

Per the announcement on the Shipyard blog, (https://ipshipyard.com/blog/2025-libp2p-maintenance-update/), Shipyard will be transitioning stewardship of go-libp2p to community maintainers.

Shipyard will continue active maintenance of go-libp2p until September 30, 2025, while working with credible community members or organizations with a proven track record to ensure a smooth handoff. We are committed to helping place these critical implementations in capable hands.

We’ve been proud to steward go-libp2p under Shipyard, and we’re grateful for the many contributors who’ve helped make go-libp2p what it is today. If you’d like to be involved in the transition please comment here or reach out to us directly.

[MarcoPolo]

Thanks Adin and Sukun and others at the Shipyard team. It's disheartening to see this.

As a general note, I'll continue maintaining go-libp2p and related go-libp2p libraries. I have some big changes in mind for go-libp2p that I've been working on recently.

[aschmahmann]

Thanks Marco, and it’s great that you’re going to be continuing maintenance work on the project!

Is the Ethereum Foundation ok with you increasing your time spent on maintenance beyond the 20% or so that I understand has been the case so far?

Do you know if the Ethereum Foundation would like to take over responsibility for the CI and interop tests? Currently Shipyard is still footing the bill so as to minimize ecosystem disruption, but ultimately this should transition to the community stakeholders funding the ongoing work.

[MarcoPolo]

Is the Ethereum Foundation ok with you increasing your time spent on maintenance beyond the 20% or so that I understand has been the case so far?

I'll discuss with folks and report back. I think in the short/medium term the answer is likely yes, as it aligns with work the EF wants to do.

Do you know if the Ethereum Foundation would like to take over responsibility for the CI and interop tests?

I think we can. Can you send me a list privately of what Shipyard is covering currently and the rough costs?

[anomit]

Thank you all for your contributions so far at Shipyard.

@MarcoPolo do we have another discussion thread or forum about the big changes you mentioned where downstream projects can participate or contribute in? We have been heavily invested in developing on the Gossipsub protocol for a decentralized sequencer network, and would like to stay close to the source of upcoming developments.