go-libp2p
go-libp2p copied to clipboard
libp2p
libp2p implementation in Go
QUIC is susceptible to Request Forgery Attacks: https://www.rfc-editor.org/rfc/rfc9000.html#name-request-forgery-with-versio In short, the client controls both the source and the destination connection ID (both up to 255 bytes in length), which the...
Looping over the connections on a fixed interval would make the data returned to Prometheus independent of its scrape interval and the amount of Prometheus instances. E.g. if you have...
I created this PR because I had to adapt the mDNS service to be used on specific interfaces. This can be useful for others as well. The usage of a...
The beginning of self dialing work, eventually closing #328. This work starts with the transports. I developed a ring buffer based `MemoryTransport`, but then, in documenting it, realized I really...
The idea is the following: 1. We construct an `AutoRelay` with a `peerChan
We haven't seen any panics in identify, but I'm going through and adding panic handlers to libp2p handlers because the benefits often outweigh the risk: - Risk: We might continue...
Fixes #1247. As suggested by @Stebalien in https://github.com/libp2p/go-libp2p/pull/1257#issuecomment-990616783. We probably need to work on naming here. Should we rename the `basic` package to `full`?
1. Only the use the cache if we actually have cached addresses. 2. Only cache relay addresses.