86aad883c8
|
||
|---|---|---|
| .github | ||
| config | ||
| examples | ||
| p2p | ||
| scripts | ||
| .codecov.yml | ||
| .gitignore | ||
| LICENSE | ||
| README.md | ||
| defaults.go | ||
| error_util.go | ||
| go.mod | ||
| go.sum | ||
| libp2p.go | ||
| libp2p_test.go | ||
| limits.go | ||
| options.go | ||
| options_filter.go | ||
| package-list.json | ||
| version.json | ||
README.md
The Go implementation of the libp2p Networking Stack.
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:
- Our documentation
- Our community discussion forum
- The libp2p Specification
- js-libp2p implementation
- rust-libp2p implementation
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.