IPFS Team Weekly Planning 2025-06-02

[lidel]

IPFS Priorities

• Roadmap
  • 2025 Year view
  • Q2 Board view (finish these before picking up anything new)

This week

• Improve the providing subsystem in Kubo — IPFS/2025 #6 & Most Kubo users can reliably advertise their data into the Amino DHT — IPFS/2025 #7

  • (Aim at Kubo RC1 before EOM) feat: Reprovide Sweep libp2p/go-libp2p-kad-dht#1082 (@guillaumemichel)
  • (Aim at Kubo RC1 before EOM) Reduce the amount of spamming (aka network noise) of non-LAN nodes in kubo’s downloading system — IPFS/2025 #10 (@gammazero)
    • Test on staging with Stracha/Pinata/Filebase added to ignored providers

• Native HTTP across the IPFS Stack, to enable Filecoin direct retrieval — IPFS/2025 #9

  • Add support for testing HTTP retrieval ipfs/ipfs-check#73
    • Add HTTP Retrieval check ipfs/ipfs-check#87 (@2color, @hsanjuan)

• Node telemetry — IPFS/2025 #17

  • ❓ TBD agree on means and list of metrics to track by end of Q2 (@hsanjuan @aschmahmann)

• Feasibility study on shifting gateway traffic to inbrowser.link — IPFS/2025 #5

  • Work on report, move numbers to "Current State of IPFS Gateways" section of the draft, create visual aids (@lidel)
  • Review/ship fix: trustless gateway returned blocks can be limited ipfs/helia#791 (@SgtPooki , @achingbrain)
  • update tests to gateway-conformance v0.8 ipfs/helia-verified-fetch#246 (@SgtPooki)

• Overhaul the IPFS docs section on Troubleshooting — IPFS/2025 #13

  • PR WIP (@2color)

• (best-effort) Ongoing maintenance of key libraries and services — IPFS/2025 #1 & Protocol stewardship and improvements — IPFS/2025 #16

  • Clarify our position on IPIP-504: provider query parameter as hint for HTTP Gateways ipfs/specs#504, feat: support provider query parameter ipfs/helia-verified-fetch#242 & chore: add tag code multiformats/multicodec#380 (?)
  • IPNS republishing in Helia (@2color)
  • Hashberg presentation outline @lidel , @hsanjuan )