Add WebSocket transport support #781

GautamBytes · 2025-07-20T09:42:36Z

Closes #585

This pull request introduces WebSocket transport support to py-libp2p, enabling interoperability with other major libp2p implementations like js-libp2p and go-libp2p that rely on /ws multiaddrs.

The implementation adds a new libp2p.transport.websocket module containing the necessary components to dial and listen on WebSocket connections, integrating seamlessly with the existing TransportUpgrader and Swarm.

Key Features

WebsocketTransport and WebsocketListener: Implements the core ITransport and IListener interfaces for handling the WebSocket connection lifecycle.
/ws Multiaddr Handling: Correctly parses /ip4/.../tcp/.../ws multiaddrs for both dialing and listening. The listener also advertises the correct public /ws address.
trio-websocket Integration: Uses trio-websocket for native, non-blocking I/O within the py-libp2p trio runtime.
Interop Testing: Includes a new integration test (test_js_ws_ping.py) that successfully establishes a connection and runs the /ipfs/ping/1.0.0 protocol with a live js-libp2p node, confirming bi-directional communication.
Upgrader Compatibility: The new transport works with the existing TransportUpgrader, allowing security protocols (e.g., noise) and stream multiplexers (e.g., mplex) to be layered on top.

Scope

This PR implements the plaintext WebSocket (/ws) transport.
Support for secure WebSockets (/wss) is deferred for future work as discussed in the issue. The transport will raise a NotImplementedError if a /wss address is provided.

Signed-off-by: GautamBytes <[email protected]>

GautamBytes · 2025-07-20T09:43:41Z

cc @seetadev

seetadev · 2025-07-20T11:14:43Z

@GautamBytes : Thanks Gautam for submitting the PR. Appreciate your initiative and efforts. Please resolve the CI/CD issues.

CCing @sumanjeet0012, @guha-rahul and @lla-dane for their feedback and pointers too. This module will be needed by a number of projects. Lets productionize it well.

Signed-off-by: GautamBytes <[email protected]>

guha-rahul · 2025-07-20T19:54:11Z

libp2p/transport/websocket/transport.py

+            raise ValueError(f"No host protocol found in {maddr}")
+
+        port = int(maddr.value_for_protocol("tcp"))
+        uri = f"ws://{host}:{port}"


are we leaving support for ipv6 for later on?

Thanks for the catch!
I'll update the dial method to properly enclose IPv6 hosts in brackets.

…libp2p into add-ws-transport

GautamBytes · 2025-07-23T16:24:17Z

@seetadev , @guha-rahul , i am trying to fix this failing workflows but facing difficulty . Its because of my test_js_ws_ping.py file not passing , error logs shows -

(venv) gautam@Gautam:/mnt/e/PY-LIBP2P/py-libp2p$ pytest -s tests/interop/test_js_ws_ping.py
======================================================================= test session starts =======================================================================
platform linux -- Python 3.12.3, pytest-8.4.1, pluggy-1.6.0 -- /mnt/e/PY-LIBP2P/py-libp2p/venv/bin/python3
cachedir: .pytest_cache
rootdir: /mnt/e/PY-LIBP2P/py-libp2p
configfile: pyproject.toml
plugins: anyio-1.4.0, Faker-37.4.0, trio-0.8.0, xdist-3.7.0
collected 1 item                                                                                                                                                  

tests/interop/test_js_ws_ping.py::test_ping_with_js_node FAILED

============================================================================ FAILURES =============================================================================
_____________________________________________________________________ test_ping_with_js_node ______________________________________________________________________
  + Exception Group Traceback (most recent call last):
  |   File "/mnt/e/PY-LIBP2P/py-libp2p/venv/lib/python3.12/site-packages/trio/_core/_run.py", line 1070, in __aexit__
  |     raise combined_error_from_nursery
  | BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception)
  +-+---------------- 1 ----------------
    | libp2p.exceptions.MultiError: Error 1: fail to open connection to peer 12D3KooWS771iWN9eXL7hSrpyS9WQos5wRXJjeiXz2HMDD3rfs4g
    | 
    | The above exception was the direct cause of the following exception:
    | 
    | Traceback (most recent call last):
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/tests/interop/test_js_ws_ping.py", line 99, in test_ping_with_js_node
    |     await host.connect(peer_info)
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/libp2p/host/basic_host.py", line 267, in connect
    |     await self._network.dial_peer(peer_info.peer_id)
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/libp2p/network/swarm.py", line 161, in dial_peer
    |     raise SwarmException(
    | libp2p.network.exceptions.SwarmException: unable to connect to 12D3KooWS771iWN9eXL7hSrpyS9WQos5wRXJjeiXz2HMDD3rfs4g, no addresses established a successful connection (with exceptions)
    | 
    | During handling of the above exception, another exception occurred:
    | 
    | Traceback (most recent call last):
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/venv/lib/python3.12/site-packages/pytest_trio/plugin.py", line 195, in _fixture_manager
    |     yield nursery_fixture
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/venv/lib/python3.12/site-packages/pytest_trio/plugin.py", line 250, in run
    |     await self._func(**resolved_kwargs)
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/tests/interop/test_js_ws_ping.py", line 102, in test_ping_with_js_node
    |     pytest.fail(
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/venv/lib/python3.12/site-packages/_pytest/outcomes.py", line 177, in fail
    |     raise Failed(msg=reason, pytrace=pytrace)
    | Failed: Connection failed with SwarmException.
    | THE REAL ERROR IS: MultiError([SwarmException('fail to open connection to peer 12D3KooWS771iWN9eXL7hSrpyS9WQos5wRXJjeiXz2HMDD3rfs4g')])
    | 
    +------------------------------------
======================================================================== warnings summary =========================================================================
<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: Type google._upb._message.MessageMapContainer uses PyType_Spec with a metaclass that has custom tp_new. This is deprecated and will no longer be allowed in Python 3.14.

<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: Type google._upb._message.ScalarMapContainer uses PyType_Spec with a metaclass that has custom tp_new. This is deprecated and will no longer be allowed in Python 3.14.

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
====================================================================== slowest 50 durations =======================================================================
9.74s call     tests/interop/test_js_ws_ping.py::test_ping_with_js_node
4.15s setup    tests/interop/test_js_ws_ping.py::test_ping_with_js_node

(1 durations < 0.005s hidden.  Use -vv to show these durations.)
===================================================================== short test summary info =====================================================================
FAILED tests/interop/test_js_ws_ping.py::test_ping_with_js_node - Connection failed with SwarmException.

would really appreciate if someone can tell how to fix this!

seetadev · 2025-07-24T04:36:52Z

@seetadev , @guha-rahul , i am trying to fix this failing workflows but facing difficulty . Its because of my test_js_ws_ping.py file not passing , error logs shows -

(venv) gautam@Gautam:/mnt/e/PY-LIBP2P/py-libp2p$ pytest -s tests/interop/test_js_ws_ping.py
======================================================================= test session starts =======================================================================
platform linux -- Python 3.12.3, pytest-8.4.1, pluggy-1.6.0 -- /mnt/e/PY-LIBP2P/py-libp2p/venv/bin/python3
cachedir: .pytest_cache
rootdir: /mnt/e/PY-LIBP2P/py-libp2p
configfile: pyproject.toml
plugins: anyio-1.4.0, Faker-37.4.0, trio-0.8.0, xdist-3.7.0
collected 1 item                                                                                                                                                  

tests/interop/test_js_ws_ping.py::test_ping_with_js_node FAILED

============================================================================ FAILURES =============================================================================
_____________________________________________________________________ test_ping_with_js_node ______________________________________________________________________
  + Exception Group Traceback (most recent call last):
  |   File "/mnt/e/PY-LIBP2P/py-libp2p/venv/lib/python3.12/site-packages/trio/_core/_run.py", line 1070, in __aexit__
  |     raise combined_error_from_nursery
  | BaseExceptionGroup: Exceptions from Trio nursery (1 sub-exception)
  +-+---------------- 1 ----------------
    | libp2p.exceptions.MultiError: Error 1: fail to open connection to peer 12D3KooWS771iWN9eXL7hSrpyS9WQos5wRXJjeiXz2HMDD3rfs4g
    | 
    | The above exception was the direct cause of the following exception:
    | 
    | Traceback (most recent call last):
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/tests/interop/test_js_ws_ping.py", line 99, in test_ping_with_js_node
    |     await host.connect(peer_info)
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/libp2p/host/basic_host.py", line 267, in connect
    |     await self._network.dial_peer(peer_info.peer_id)
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/libp2p/network/swarm.py", line 161, in dial_peer
    |     raise SwarmException(
    | libp2p.network.exceptions.SwarmException: unable to connect to 12D3KooWS771iWN9eXL7hSrpyS9WQos5wRXJjeiXz2HMDD3rfs4g, no addresses established a successful connection (with exceptions)
    | 
    | During handling of the above exception, another exception occurred:
    | 
    | Traceback (most recent call last):
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/venv/lib/python3.12/site-packages/pytest_trio/plugin.py", line 195, in _fixture_manager
    |     yield nursery_fixture
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/venv/lib/python3.12/site-packages/pytest_trio/plugin.py", line 250, in run
    |     await self._func(**resolved_kwargs)
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/tests/interop/test_js_ws_ping.py", line 102, in test_ping_with_js_node
    |     pytest.fail(
    |   File "/mnt/e/PY-LIBP2P/py-libp2p/venv/lib/python3.12/site-packages/_pytest/outcomes.py", line 177, in fail
    |     raise Failed(msg=reason, pytrace=pytrace)
    | Failed: Connection failed with SwarmException.
    | THE REAL ERROR IS: MultiError([SwarmException('fail to open connection to peer 12D3KooWS771iWN9eXL7hSrpyS9WQos5wRXJjeiXz2HMDD3rfs4g')])
    | 
    +------------------------------------
======================================================================== warnings summary =========================================================================
<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: Type google._upb._message.MessageMapContainer uses PyType_Spec with a metaclass that has custom tp_new. This is deprecated and will no longer be allowed in Python 3.14.

<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: Type google._upb._message.ScalarMapContainer uses PyType_Spec with a metaclass that has custom tp_new. This is deprecated and will no longer be allowed in Python 3.14.

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
====================================================================== slowest 50 durations =======================================================================
9.74s call     tests/interop/test_js_ws_ping.py::test_ping_with_js_node
4.15s setup    tests/interop/test_js_ws_ping.py::test_ping_with_js_node

(1 durations < 0.005s hidden.  Use -vv to show these durations.)
===================================================================== short test summary info =====================================================================
FAILED tests/interop/test_js_ws_ping.py::test_ping_with_js_node - Connection failed with SwarmException.

would really appreciate if someone can tell how to fix this!

@GautamBytes : Thank you so much for taking the initiative to work on fixing the failing workflows. Your effort on test_js_ws_ping.py is really appreciated. The SwarmException error you’re seeing usually means that the WebSocket connection between the Python host and the JS peer isn’t being established — this could be due to a mismatch in multiaddr protocols, peer discovery issues, or the JS node not being ready when the test starts.

@acul71, @guha-rahul , @varun-r-mallya — can you jump in to help debug this WebSocket issue with ? Maybe we can review the interop/test_js_ws_ping.py setup together and check:

If the JS node is properly launched and listening on the expected /ws multiaddr.

Whether dial_peer is using the correct transport and address.

If any recent changes in the libp2p handshake or transport modules might have caused regressions.

@GautamBytes, you might also try:

Running the JS ping test manually with verbose logs (DEBUG=libp2p* pytest -s tests/interop/test_js_ws_ping.py) to see detailed handshake failures.

Verifying that the JS node and Python host share the same set of supported protocols and transports.

Testing if basic_host.connect(peer_info) works when you manually start a JS libp2p node with WebSocket enabled.

Let’s collaborate and get this test passing soon.

acul71 · 2025-08-07T14:09:56Z

@GautamBytes @seetadev
I'm working on WebSocket transport.
I've added some additional tests, I've seen that I can do an echo test with PLAINTEXT_PROTOCOL_ID
But it fails with Noise

Work in progress.......

…Add transport_registry.py for centralized transport management - Integrate WebSocket transport with new registry - Add comprehensive test suite for transport registry - Include WebSocket examples and demos - Update transport initialization and swarm integration

acul71 · 2025-08-09T23:57:01Z

@GautamBytes can you give me access to push to your fork ?

seetadev · 2025-08-10T05:55:30Z

@GautamBytes : Hi Gautam. @acul71 is our amazing Py-libp2p developer, key maintainer to py-multiaddr, py-cid and core py-libp2p modules. Kindly give him push access so that he can collaborate with you on taking web socket to a production stage. Appreciate your efforts and initiative.

seetadev · 2025-08-10T05:57:16Z

@GautamBytes @seetadev I'm working on WebSocket transport. I've added some additional tests, I've seen that I can do an echo test with PLAINTEXT_PROTOCOL_ID But it fails with Noise

Work in progress.......

@acul71 : Great, thanks Luca. Appreciate your initiative and support.

I have asked Gautam to share access with you soon. He might be unavailable because of his engineering exams this week. Will be available soon in a day or two.

GautamBytes · 2025-08-10T06:34:37Z

@acul71 , i have invited u as collaborator , can u check the mail and confirm once?

seetadev · 2025-08-10T11:25:33Z

@acul71 : Can you confirm with @GautamBytes ? He did share an invite today.

- Fix INotifee interface compliance in WebSocket demo - Fix handler function signatures to be async (THandler compatibility) - Fix is_closed method usage with proper type checking - Fix pytest.raises multiple exception type issue - Fix line length violations (E501) across multiple files - Add debugging logging to Noise security module for troubleshooting - Update WebSocket transport examples and tests - Improve transport registry error handling

…ansport

acul71 · 2025-09-09T23:03:24Z

@yashksaini-coder
Next steps would be to see how python Websocket implementation works with other libp2p implementations like javascript, go, etc...
This are called interop-tests and right now the python-javascript Wesocket interop is failing.
First the python wss client is embedded in the test https://github.com/GautamBytes/py-libp2p/blob/add-ws-transport/tests/interop/test_js_ws_ping.py
We should make a python websocket client that is a standalone python file, so that will be easier to test manually the interop.
Also we should research in go implementation if there are websockets examples and make a go server (like javascript client https://github.com/GautamBytes/py-libp2p/blob/add-ws-transport/tests/interop/js_libp2p/js_node/src/ws_ping_node.mjs )

This scripts needs to be reviewed to see if they are well done (In the end make them work)

Would you like to start investigating ?

yashksaini-coder · 2025-09-09T23:07:14Z

@yashksaini-coder Next steps would be to see how python Websocket implementation works with other libp2p implementations like javascript, go, etc... This are called interop-tests and right now the python-javascript Wesocket interop is failing. First the python wss client is embedded in the test https://github.com/GautamBytes/py-libp2p/blob/add-ws-transport/tests/interop/test_js_ws_ping.py We should make a python websocket client that is a standalone python file, so that will be easier to test manually the interop. Also we should research in go implementation if there are websockets examples and make a go server (like javascript client https://github.com/GautamBytes/py-libp2p/blob/add-ws-transport/tests/interop/js_libp2p/js_node/src/ws_ping_node.mjs )

This scripts needs to be reviewed to see if they are well done (In the end make them work)

Would you like to start investigating ?

yes I was able to find out that during the interop js ping test, the security handshake fails, that could be a starting point, I will get js-libp2p module and start working on this.

…plement proper error handling and cleanup in P2PWebSocketConnection. Update tests for improved connection handling.

…or improved readability. Clean up whitespace and enhance logging for connection management.

seetadev · 2025-09-15T15:53:38Z

@yashksaini-coder and @acul71 : This PR is indeed coming along well. Appreciate your efforts.

Wish if you could add a test suite and a newsfragment file.

@acul71, @sumanjeet0012 and @lla-dane : Wish to have a collaborative review on this PR. We can take up js-libp2p interop in a separate PR if it is fully ready functionality wise. We are aiming for a new py-libp2p release and would like to get web socket transport protocol support in that release.

seetadev · 2025-09-15T19:22:44Z

@yashksaini-coder and @acul71 : Wish to also share that a number of CI/CD test cases are failing as well. Wish if you could resolve them.

yashksaini-coder · 2025-09-16T04:03:34Z

@yashksaini-coder and @acul71 : Wish to also share that a number of CI/CD test cases are failing as well. Wish if you could resolve them.

Got it sir,

- Combined yashksaini-coder's flow control improvements with luca's WSS features - Preserved comprehensive WSS support, TLS configuration, and handshake timeout - Added production-ready buffer management and connection limits - Maintained backward compatibility with existing WebSocket functionality - Integrated both approaches for optimal WebSocket transport implementation

…ation - Added back debug_websocket_url.py for WebSocket URL testing - Added back test_websocket_client.py for standalone WebSocket testing - These tools complement the integrated WebSocket transport implementation

- Add TLS configuration support to new_host and new_swarm functions - Fix WebSocket transport tests (test_wss_host_pair_data_exchange, test_wss_listen_without_tls_config) - Integrate TLS configuration with transport registry for proper WebSocket WSS support - Move debug files to downloads directory for future reference - All 47 WebSocket tests now passing including WSS functionality - Maintain backward compatibility with existing code - Resolve all type checking and linting issues

acul71 · 2025-09-17T07:13:53Z

@yashksaini-coder and @acul71 : Wish to also share that a number of CI/CD test cases are failing as well. Wish if you could resolve them.

Hi @seetadev
Issues should be resolved now. Please run CI/CD to confirm.
The wss interop test is for now skipped can be addressed in other PR.

acul71 · 2025-09-17T07:15:38Z

Summary

This last commits adds comprehensive WebSocket transport support to py-libp2p, including both WebSocket (WS) and WebSocket Secure (WSS) protocols with proper TLS configuration handling.

Features Added

✅ WebSocket Transport Implementation: Full WS/WSS transport support
✅ TLS Configuration: Proper TLS client/server configuration for WSS
✅ Transport Registry Integration: Seamless integration with existing transport system
✅ Comprehensive Test Suite: 47 WebSocket tests including WSS functionality
✅ Backward Compatibility: No breaking changes to existing APIs

Key Changes

libp2p/__init__.py: Added TLS configuration parameters to new_host and new_swarm
libp2p/transport/websocket/: Complete WebSocket transport implementation
tests/core/transport/test_websocket.py: Comprehensive test suite with WSS support
Transport Registry: Proper TLS configuration passing to WebSocket transports

Test Results

✅ 843 tests passed, 2 skipped
✅ All 47 WebSocket tests passing
✅ WSS functionality fully working
✅ No regressions in existing functionality

Technical Details

Uses trio-websocket for WebSocket implementation
Supports both WS (/ws) and WSS (/wss) multiaddr protocols
Proper TLS certificate handling for WSS connections
Flow control and buffer management for production use
Full integration with libp2p's transport registry system

Files Changed

libp2p/__init__.py - TLS configuration support
libp2p/transport/websocket/ - WebSocket transport implementation
tests/core/transport/test_websocket.py - Comprehensive test suite
tests/interop/test_js_ws_ping.py - Interop test updates

Breaking Changes

None - fully backward compatible

Documentation

WebSocket transport follows libp2p transport interface
TLS configuration is optional and backward compatible
Comprehensive test coverage for all functionality

acul71 · 2025-09-17T07:22:54Z

Thanks to @yashksaini-coder

yashksaini-coder's Contributions

Summary

Enhanced WebSocket transport with production-grade features for py-libp2p.

Key Features Added

Flow Control: Configurable buffer management (4MB default) with thread-safe writes
Connection Limits: Production-ready connection counting and rate limiting (1000 max connections)
Error Handling: Idempotent connection closing with proper resource cleanup
Code Quality: Enhanced logging, improved constructors, and better error handling

Files Modified

libp2p/transport/websocket/connection.py - Core connection management
libp2p/transport/websocket/transport.py - Transport implementation
tests/interop/test_js_ws_ping.py - Updated interop tests

Current Limitations

Interop tests are skipped due to JavaScript dependency issues
WSS tests require cryptography package and may skip if not available
Limited real-world testing - no comprehensive identify protocol testing on WSS
Examples exist but full integration testing with libp2p protocols is incomplete

Impact

Added production-ready infrastructure (flow control, error handling, connection limits) to WebSocket transport, but full integration with libp2p protocols and real-world usage scenarios need further validation.

yashksaini-coder · 2025-09-17T07:28:03Z

@acul71 thank you for the kind words, hope my contribution helped resolve this issue 👍🏼

acul71 · 2025-09-17T17:46:42Z

@seetadev
Can you run the CI/CD ?
If it passes I think we can merge this PR, so that transport_registry (swarm param selector by multiaddr) can be used by other transports that are coming along.
The Websocket is still high-experimental.
I've opened a discussion here:
#937
and in this new issue the task needed to achieve a full Websocket impl
#938

seetadev · 2025-09-21T18:33:32Z

@acul71 : Hi Luca. I did run CI/CD pipeline. Sorry, my message was not posted earlier.

There are 2 CI/CD issues remaining. Wish if we could arrive at a good conclusion on them.

@acul71 and @yashksaini-coder : Thanks a lot for pushing this forward 🙌 Appreciate your initiative and great efforts.

It’s great to see transport_registry shaping up in a way that can be reused by upcoming transports — that’s a really valuable step for the ecosystem.

Appreciate you also flagging the WebSocket work. Even though it’s still marked as high-experimental, having the discussion (#937) and a dedicated issue (#938) already scoped out makes it much easier for contributors to jump in and build towards a complete implementation.

Appreciate the thoroughness here — this PR will definitely help us move faster on transport expansion.

- Change global registry from immediate to lazy initialization - Fix doctest failure caused by debug logging during MultiError import - Update all functions to use get_transport_registry() instead of direct access - Resolves CI/CD doctest failure in libp2p.rst

acul71 · 2025-09-21T23:33:57Z

There are 2 CI/CD issues remaining. Wish if we could arrive at a good conclusion on them

@seetadev
Should be good now, can you re-run the CI/CD

yashksaini-coder · 2025-09-22T15:39:34Z

I just ran entire test commands all passed successfully, the CI/CD run can give more insights on current status

@acul71 @seetadev

seetadev · 2025-09-22T15:53:17Z

@acul71 , @yashksaini-coder : Did run the CI/Cd test pipeline. Will share results soon.

Hopefully, all test issues should get resolved. Appreciate your efforts and initiative.

seetadev · 2025-09-22T16:36:31Z

@acul71 , @yashksaini-coder : Indeed, all the test cases are passing. This PR is ready for final review + merge.

Please now start working on the missing features at #938. This is in reference to our last maintainer's call. Thank you for your continued support and wonderful progress.

@acul71: Would recommend you to collaborate with Paul on the upcoming py-libp2p release along with working on the above issue with @yashksaini-coder. Appreciate your efforts.

GautamBytes added 2 commits July 20, 2025 09:23

added WebSocket transport support

1874183

Signed-off-by: GautamBytes <[email protected]>

small tweak

227a5c6

Signed-off-by: GautamBytes <[email protected]>

Merge branch 'main' into add-ws-transport

fa0b64d

Prevent crash in JS interop test

4fb7132

Signed-off-by: GautamBytes <[email protected]>

guha-rahul reviewed Jul 20, 2025

View reviewed changes

seetadev and others added 5 commits July 21, 2025 06:44

Merge branch 'main' into add-ws-transport

b6c3637

Merge branch 'main' into add-ws-transport

7469238

Merge branch 'main' into add-ws-transport

8a21435

Fix IPv6 host bracketing in WebSocket transport

1997777

Merge branch 'add-ws-transport' of https://github.com/GautamBytes/py-…

53a16d0

…libp2p into add-ws-transport

GautamBytes requested a review from guha-rahul July 23, 2025 08:27

seetadev added 3 commits July 26, 2025 01:56

Merge branch 'main' into add-ws-transport

65faa21

Merge branch 'main' into add-ws-transport

7a1aa54

Merge branch 'main' into add-ws-transport

651bf0f

acul71 added 2 commits August 9, 2025 20:18

Merge upstream/main into add-ws-transport

a6f8569

Merge branch 'main' into add-ws-transport

19c1f5e

Merge branch 'main' into add-ws-transport

167dfdc

acul71 added 2 commits August 11, 2025 01:25

Merge remote-tracking branch 'origin/add-ws-transport' into add-ws-tr…

a5b0db1

…ansport

Copilot AI mentioned this pull request Sep 11, 2025

Implement WebSocket Transport with IPv6 Support and Security Integration GautamBytes/py-libp2p#1

Closed

yashksaini-coder force-pushed the add-ws-transport branch from d0c0508 to 771b837 Compare September 11, 2025 20:15

yashksaini-coder and others added 3 commits September 12, 2025 03:04

Update the flow control, buffer management, and connection limits. Im…

0271a36

…plement proper error handling and cleanup in P2PWebSocketConnection. Update tests for improved connection handling.

Refactor P2PWebSocketConnection and WebsocketTransport constructors f…

4fdfdae

…or improved readability. Clean up whitespace and enhance logging for connection management.

Merge branch 'main' into add-ws-transport

95e7e7b

Merge branch 'main' into add-ws-transport

284eee7

acul71 added 3 commits September 17, 2025 01:00

seetadev and others added 2 commits September 17, 2025 15:27

Merge branch 'main' into add-ws-transport

5f0c510

doc: websocket newsframgment

1a4fe91

seetadev and others added 2 commits September 22, 2025 02:36

Merge branch 'main' into add-ws-transport

87429eb

seetadev merged commit d519f75 into libp2p:main Sep 22, 2025
28 checks passed

yashksaini-coder deleted the add-ws-transport branch September 23, 2025 18:25

Add WebSocket transport support #781

Add WebSocket transport support #781

Uh oh!

Conversation

GautamBytes commented Jul 20, 2025

Key Features

Scope

Uh oh!

GautamBytes commented Jul 20, 2025

Uh oh!

seetadev commented Jul 20, 2025

Uh oh!

guha-rahul Jul 20, 2025

Choose a reason for hiding this comment

Uh oh!

GautamBytes Jul 21, 2025

Choose a reason for hiding this comment

Uh oh!

GautamBytes commented Jul 23, 2025

Uh oh!

seetadev commented Jul 24, 2025

Uh oh!

acul71 commented Aug 7, 2025

Uh oh!

acul71 commented Aug 9, 2025

Uh oh!

seetadev commented Aug 10, 2025

Uh oh!

seetadev commented Aug 10, 2025

Uh oh!

GautamBytes commented Aug 10, 2025

Uh oh!

seetadev commented Aug 10, 2025

Uh oh!

acul71 commented Sep 9, 2025

Uh oh!

yashksaini-coder commented Sep 9, 2025

Uh oh!

seetadev commented Sep 15, 2025

Uh oh!

seetadev commented Sep 15, 2025

Uh oh!

yashksaini-coder commented Sep 16, 2025

Uh oh!

acul71 commented Sep 17, 2025

Uh oh!

acul71 commented Sep 17, 2025

Summary

Features Added

Key Changes

Test Results

Technical Details

Files Changed

Breaking Changes

Documentation

Uh oh!

acul71 commented Sep 17, 2025

yashksaini-coder's Contributions

Summary

Key Features Added

Files Modified

Current Limitations

Impact

Uh oh!

yashksaini-coder commented Sep 17, 2025

Uh oh!

acul71 commented Sep 17, 2025

Uh oh!

seetadev commented Sep 21, 2025

Uh oh!

acul71 commented Sep 21, 2025

Uh oh!

yashksaini-coder commented Sep 22, 2025

Uh oh!

seetadev commented Sep 22, 2025

Uh oh!

seetadev commented Sep 22, 2025

Uh oh!

Uh oh!

Uh oh!