Skip to content

Tracking - Filecoin ProPGF Batch 3 grant #3602

Description

@tabcat

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/trackingA meta-issue for tracking work

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions