libp2p implementation in Go
Go to file
Marco Munizaga 3eb35223a7
Pass endpoint information to resource manager's OpenConnection (#1633)
* Move mux testsuite to here

* Update OpenConnection call sites to pass in endpoint information

* Go mod update

* Use proper versions for deps
2022-07-01 15:43:42 -07:00
.github redirect to libp2p/specs for general libp2p ideas (#1388) 2022-04-18 13:59:05 -07:00
config switch from github.com/libp2p/go-stream-muxer-multistream to p2p/muxer/muxer-multistream 2022-05-20 12:41:52 +02:00
examples chore: update examples to go-libp2p v0.20.0 (#1557) 2022-05-28 02:24:51 -07:00
p2p Pass endpoint information to resource manager's OpenConnection (#1633) 2022-07-01 15:43:42 -07:00
scripts fix: mkreleaselog exclude autogenerated files (#1567) 2022-05-26 08:32:15 -07:00
.codecov.yml turn off stupid codecov annotations 2020-09-14 19:35:21 +03:00
.gitignore Add .gitignore for each example 2021-05-10 11:54:35 +01:00
LICENSE added docs 2015-09-30 19:08:00 -04:00
README.md remove workspace and packages section from README (#1563) 2022-05-27 02:59:16 -07:00
defaults.go switch from github.com/libp2p/go-libp2p-tls to p2p/security/tls 2022-04-27 12:00:11 +02:00
error_util.go refactor for transport changes 2018-06-04 21:22:24 -07:00
go.mod Pass endpoint information to resource manager's OpenConnection (#1633) 2022-07-01 15:43:42 -07:00
go.sum Pass endpoint information to resource manager's OpenConnection (#1633) 2022-07-01 15:43:42 -07:00
libp2p.go Doc: QUIC is default when no transports set (#1250) 2021-12-04 05:52:56 -08:00
libp2p_test.go remove flaky TestTcpSimultaneousConnect (#1425) 2022-04-22 09:19:32 -07:00
limits.go adjust circuit protocol limits to give some room for the client 2022-01-18 12:30:47 +04:00
options.go implement relay discovery in autorelay 2022-03-31 11:29:41 +01:00
options_filter.go Fixed bug for inbound connections gated by the deprecated filter option (#1004) 2020-09-16 10:37:36 +05:30
package-list.json Cleanup some references to old examples repo 2021-05-10 11:46:43 +01:00
version.json release v0.20.0 (#1530) 2022-05-25 07:26:59 -07:00

README.md

libp2p hex logo

The Go implementation of the libp2p Networking Stack.

Go Reference

Table of Contents

Background

libp2p is a networking stack and library modularized out of The IPFS Project, and bundled separately for other tools to use.

libp2p is the product of a long, and arduous quest of understanding -- a deep dive into the internet's network stack, and plentiful peer-to-peer protocols from the past. Building large-scale peer-to-peer systems has been complex and difficult in the last 15 years, and libp2p is a way to fix that. It is a "network stack" -- a protocol suite -- that cleanly separates concerns, and enables sophisticated applications to only use the protocols they absolutely need, without giving up interoperability and upgradeability. libp2p grew out of IPFS, but it is built so that lots of people can use it, for lots of different projects.

To learn more, check out the following resources:

Usage

This repository (go-libp2p) serves as the entrypoint to the universe of packages that compose the Go implementation of the libp2p stack.

You can start using go-libp2p in your Go application simply by adding imports from our repos, e.g.:

import "github.com/libp2p/go-libp2p"

Examples

Examples can be found in the examples folder.

Development

Tests

go test ./... will run all tests in the repo.

Contribute

go-libp2p is part of The IPFS Project, and is MIT-licensed open source software. We welcome contributions big and small! Take a look at the community contributing notes. Please make sure to check the issues. Search the closed ones before reporting things, and help us with the open ones.

Guidelines:

  • read the libp2p spec
  • ask questions or talk about things in our discussion forums, or open an issue for bug reports, or #libp2p on freenode.
  • ensure you are able to contribute (no legal issues please -- we use the DCO)
  • get in touch with @marten-seemann about how best to contribute
  • have fun!

There's a few things you can do right now to help out:

  • Go through the modules below and check out existing issues. This would be especially useful for modules in active development. Some knowledge of IPFS/libp2p may be required, as well as the infrasture behind it - for instance, you may need to read up on p2p and more complex operations like muxing to be able to help technically.
  • Perform code reviews.
  • Add tests. There can never be enough tests.

Supported Go Versions

We test against and support the two most recent major releases of Go. This is informed by Go's own security policy.