go-libp2p
go-libp2p copied to clipboard
libp2p
libp2p implementation in Go
I can consistently repro the errors mentioned at https://github.com/libp2p/go-libp2p/blob/b23d8b580bf819b207aa136e6484183233d52a36/p2p/transport/tcp/tcp.go#L43-L47 with kubo. Note that for this issue, I am running this code directly from a `make build` version of kubo on...
We should rethink how we treat QUIC connections. Our current connection model assumes a clear separation between the two states "Connected" and "Disconnected". QUIC has two interesting properties that dilute...
At the moment, we're enabling keep-alives on both the server and the client. In general, it should only be necessary for one of the nodes to send keep-alives. The server...
We need to make sure we can decode and then re-encode public keys back into the same datastructure. That means preserving unknown fields (which I believe we don't currently do).
We have some code to support a valid TLS cert in the webtransport listener, but we disabled it in https://github.com/libp2p/go-libp2p/pull/1927. There's some subtlety around making it secure. In the mean...
For example, TCP+noise+yamux: 
During our [`punchr`](https://github.com/libp2p/punchr) measurement campaign, we observed that the listening addresses returned by `host.Addrs()` didn't match the ones that were used during a hole punch. After a `punchr` client has...
Fixes #2913 The issue is presented in https://github.com/libp2p/go-libp2p/issues/2913#issuecomment-2305818394. The fix here introduces "associations" to refcountedTransports. a libp2p transport can associate itself with the transport used for listening, and then prefer...
## What's in this PR This change attempts to fix #2913. In essence, it enables the `dctur` protocol, when a peer has a public IP (if it's bound to an...
Hello While looking through your docs I found and fixed several spelling issues. Br, Elias.
