libp2p / libp2p/js-libp2p

Tracking - Filecoin ProPGF Batch 3 grant

Open
#3,602 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/tracking
Dominant language
TypeScript
Stars
2.6k
Forks
546
Avg merge
8h 18m
Merged PRs (30d)
16

Description

The Filecoin ProPGF Batch 3 grant for js-libp2p has been finalized and work is starting. This issue tracks the funded milestones.

Project: https://app.filpgf.io/project/js-libp2p

What the grant covers

Filecoin ProPGF funds public-goods infrastructure that the Filecoin and IPFS ecosystems depend on. js-libp2p was accepted into Batch 3 under Core Infrastructure: $15,000 over a three month term running to mid-November 2026.

It funds two maintenance migrations (yamux and noise, moving from ChainSafe into this org), finalizing and shipping WebRTC-Direct v2, and day-to-day maintenance across the monorepo: triage, bug fixes, security patches, dependency updates, reviews, and releases, including validating js-libp2p against Node 26 once it reaches Active LTS.

js-libp2p has been maintained part-time and unpaid since the handover in February 2026. This is the first funding behind that work.

On sustainability

The program is renewable. The term can be extended a month at a time, and projects can apply again in later batches, so this could become sustained funding rather than a one-off.

That is not the goal, though. The goal is a project that sustains itself: people building on js-libp2p giving back to it, financially or through code, reviews, and triage. Grants buy time to get there. If you depend on js-libp2p, either kind of contribution is what makes the difference.

Milestones

Each milestone is tracked in its own issue, listed as a sub-issue. Work references those issues, so the evidence for each one collects in a single place.

  • yamux maintenance migration, due September 14, 2026. Maintenance of the Yamux stream multiplexer moves from ChainSafe into this monorepo.
  • noise maintenance migration, due September 29, 2026. Maintenance of the Noise handshake moves from ChainSafe into this monorepo.
  • WebRTC-Direct v2, due November 14, 2026. Finalize the spec and ship the implementation, with interoperability validated against go-libp2p.

Ongoing maintenance runs in parallel throughout the term. It is not tracked separately, it is the normal flow of the repo.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Filecoin ProPGF project page and the milestone sub-issues referenced here: yamux maintenance migration, noise maintenance migration, and WebRTC-Direct v2. The issue provides no implementation files or tests; completion means the migrations and WebRTC-Direct v2 are delivered by their stated deadlines, with interoperability validated against go-libp2p.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.