From 03e2661982ff2858d7cc9ea2d326a0a43338bb9d Mon Sep 17 00:00:00 2001 From: acul71 Date: Wed, 9 Apr 2025 04:57:33 +0200 Subject: [PATCH] modified multiplexer getting_started doc section --- docs/getting_started.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/getting_started.rst b/docs/getting_started.rst index 9b9e00a1..67321024 100644 --- a/docs/getting_started.rst +++ b/docs/getting_started.rst @@ -57,7 +57,9 @@ For development or testing purposes only, you can use the insecure transport: Multiplexing ^^^^^^^^^^^^ -While multiplexers are not strictly required, they are highly recommended as they improve the effectiveness and efficiency of connections. Adding a multiplexer to your configuration will allow libp2p to run several of its internal protocols, like Identify, as well as allow your application to easily run any number of protocols over a single connection. +Multiplexers are a required component of libp2p connections. They enable multiple logical streams to be carried over a single connection, which is essential for efficient peer-to-peer communication. The multiplexer layer is a mandatory part of the connection upgrade process, alongside the transport and security layers. + +Adding a multiplexer to your configuration allows libp2p to run several of its internal protocols, like Identify, as well as enables your application to run any number of protocols over a single connection. For Python, we can use mplex as our multiplexer: