Doc: expanding the introduction section #566

[seetadev]

Hi @acul71

Thank you for taking the time to dive deep into the py-libp2p codebase and provide detailed feedback—really appreciate the initiative.

You're absolutely right that some of the features were either not previously implemented or not fully functional at the time of your research. Since then, there's been steady progress on multiple fronts, and we’ve started tracking these efforts more formally via GitHub issues. Let me give you a detailed breakdown and point you in the right direction:

✅ QUIC Transport

You're right that QUIC was in early development for a while. The good news is: QUIC support is now near completion.
The implementation can be found in the transports/quic module and is being tracked in this issue.
We're currently testing edge cases and integration scenarios, and it's looking solid so far.

🛠️ NAT Traversal

NAT traversal is currently in active development, and we're implementing features like AutoNAT and relay-based hole punching.
This is being tracked in this issue
and discussed extensively in recent dev syncs. Some parts are being developed under the libp2p/nat module.

🧪 WebSocket Transport

You're absolutely right—WebSocket transport is not yet implemented, but the good news is that the design and scoping discussions are already underway.

🌐 mDNS Peer Discovery

Again, totally fair call—mDNS hasn't landed yet.
That said, it's on the roadmap and has been actively discussed for upcoming sprints.

📦 Bootstrap Module

Currently, you're right that there’s only manual bootstrap support. A modular bootstrap system (as seen in go-libp2p and js-libp2p) is planned and will likely be scoped after mDNS is in place. We'll be opening a tracking issue for this soon.

In short:
You're spot-on with your observations, and I’m really glad you brought them up. We're making rapid progress in closing the feature parity gap and appreciate any documentation updates or collaboration you’d like to offer as these features roll out.

Let me know if you'd like links to any WIP branches or implementation notes—we’d love to keep you in the loop.

Thanks again! 🙌

Manu

[acul71]

Hi @Khwahish29 .
If you could correct the documentation (see #566 (comment) and #571 (comment)) we can close #559