You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specs/phase0/p2p-interface.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -127,8 +127,8 @@ This section outlines the specification for the networking stack in Ethereum con
127
127
Even though libp2p is a multi-transport stack (designed to listen on multiple simultaneous transports and endpoints transparently),
128
128
we hereby define a profile for basic interoperability.
129
129
130
-
All implementations MUST support the TCP libp2p transport, and it MUST be enabled for both dialing and listening (i.e. outbound and inbound connections).
131
-
The libp2p TCP transport supports listening on IPv4 and IPv6 addresses (and on multiple simultaneously).
130
+
All implementations MUST support the TCP libp2p transport, MAY support the QUIC (UDP) libp2p transport, and MUST be enabled for both dialing and listening (i.e. outbound and inbound connections).
131
+
The libp2p TCP and QUIC (UDP) transports support listening on IPv4 and IPv6 addresses (and on multiple simultaneously).
132
132
133
133
Clients must support listening on at least one of IPv4 or IPv6.
134
134
Clients that do _not_ have support for listening on IPv4 SHOULD be cognizant of the potential disadvantages in terms of
@@ -963,9 +963,9 @@ The Ethereum Node Record (ENR) for an Ethereum consensus client MUST contain the
0 commit comments