Tracking Issue: 🧩 Filecoin × py-libp2p — Proposed Set of R&D initiatives

[seetadev]

1️⃣ Filecoin Network Parity & Interop

Issue: Improve py-libp2p compatibility with Filecoin network behaviors

• Audit py-libp2p defaults against Filecoin node networking expectations
• Compare connection lifecycle, stream limits, and peer scoring assumptions
• Identify gaps vs go-libp2p usage in Filecoin
  Outcome: Clear parity notes + suggested config changes or docs

---

Issue: Validate py-libp2p interoperability with Filecoin nodes (Lotus / Forest)

• Establish test cases where py-libp2p peers connect to real Filecoin nodes
• Document supported protocols and failure modes
• Capture handshake, muxer, and security compatibility
  Outcome: Interop matrix + reproducible test steps

---

2️⃣ Protocol Support & Gaps

Issue: Evaluate Filecoin-specific libp2p protocols support in py-libp2p

• Review protocols used by Filecoin (e.g., identify, ping, gossipsub variants)
• Identify missing or partially supported protocol IDs
• Propose roadmap items or stubs
  Outcome: Tracked protocol gaps with prioritization

---

Issue: Add example demonstrating Filecoin-compatible gossipsub usage

• Create a py-libp2p example aligned with Filecoin pubsub parameters
• Document mesh parameters and message validation expectations
  Outcome: Reference example for Filecoin-style pubsub

---

3️⃣ Security & Transport (Filecoin Context)

Issue: Review TLS / Noise usage in py-libp2p for Filecoin deployments

• Compare security transports used in Filecoin networks
• Validate cert handling, peer ID derivation, and failure behavior
  Outcome: Security notes + recommended defaults

---

Issue: Connection hardening for long-lived Filecoin peers

• Analyze reconnect behavior, idle stream handling, and backoff strategies
• Propose improvements for long-running Filecoin services
  Outcome: More robust connection lifecycle for production use

---

4️⃣ Performance & Scaling

Issue: Benchmark py-libp2p performance under Filecoin-like workloads

• Simulate higher peer counts and message throughput
• Measure stream creation, latency, and memory usage
  Outcome: Performance report + optimization candidates

---

Issue: Improve peerstore scalability for Filecoin-scale peer sets

• Review peerstore cleanup, TTLs, and memory growth
• Suggest tuning or structural improvements
  Outcome: Safer defaults and documented limits

---

5️⃣ Developer Experience & Tooling

Issue: Add Filecoin-focused py-libp2p examples
Examples could include:

• Connecting to a Filecoin node
• Ping / identify against Filecoin peers
• Pubsub participation (read-only observer mode)
  Outcome: Lower barrier for Filecoin devs using Python

---

Issue: Document how py-libp2p fits into Filecoin architecture

• Where py-libp2p can be used today
• Where go-libp2p is still required
• Suggested use cases (tooling, analytics, testnets, research)
  Outcome: Clear positioning for Python developers

---

6️⃣ Testing & CI

Issue: Add Filecoin-oriented integration tests for py-libp2p

• Mock or live network tests
• Focus on protocol negotiation and stream stability
  Outcome: Early detection of Filecoin regressions

[GautamBytes]

Hey @seetadev sir , pr for module 5 is raised here . Now i will be taking on module 2 from here!