The Go implementation of the libp2p Networking Stack.
Table of Contents
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.
We will be writing a set of docs, posts, tutorials, and talks to explain what p2p is, why it is tremendously useful, and how it can help your existing and new projects. But in the meantime, check out
This repository (
go-libp2p) serves as the entrypoint to the universe of modules 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.:
go get or
go build, excluding the libp2p repos from Go modules proxy usage. You only need to do this the first time you import go-libp2p to make sure you latch onto the correct version lineage (see golang/go#34189 for context):
$ GOPRIVATE='github.com/libp2p/*' go get ./...
The Go build tools will look for available releases, and will pick the highest available one.
As new releases of go-libp2p are made available, you can upgrade your application by manually editing your
go.mod file, or using the Go tools to maintain module requirements.
Examples can be found in the examples folder.
Using the go-libp2p Workspace
While developing, you may need to make changes to several modules at once, or you may want changes made locally in one module to be available for import by another.
The go-libp2p workspace provides a developer-oriented view of the modules that comprise go-libp2p.
Using the tooling in the workspace repository, you can checkout all of go-libp2p’s module repos and enter “local mode”, which adds replace directives to the go.mod files in each local working copy. When you build locally, the libp2p depdendencies will be resolved from your local working copies.
Once you’ve committed your changes, you can switch back to “remote mode”, which removes the replace directives and pulls imports from the main go module cache.
See the workspace repo for more information.
Due to the difficulties in keeping both dependency management solutions up-to-date, gx support was ended in April 2019.
Ending gx support does not mean that existing gx builds will break. Because gx references dependencies by their immutable IPFS hash, any currently working gx builds will continue to work for as long as the dependencies are resolvable in IPFS.
However, new changes to go-libp2p will not be published via gx, and users are encouraged to adopt gomod to stay up-to-date.
If you experience any issues migrating from gx to gomod, please join the discussion at the libp2p forums.
go test ./... will run all tests in the repo.
Please start a release by opening a new Libp2p Release issue.
This table is generated using the module
List of packages currently in existence for libp2p:
||go-libp2p entry point|
||core interfaces, types, and abstractions|
||minimal implementation of the “host” interface|
||reference implementation of network state machine|
||uTorrent transport (UTP)|
||upgrades multiaddr-net connections into full libp2p transports|
||partial transport for building transports that reuse ports|
||SecIO crypto channel|
||TLS 1.3+ crypto channel|
||multistream multiplexed meta crypto channel|
||reference private networking implementation|
||YAMUX stream multiplexer|
||MPLEX stream multiplexer|
||reference implementation of peer metadata storage component|
||reference implementation of connection manager|
||record type and validator logic|
||Kademlia routing table helper types|
||Router based on Coral DHT|
||record-store over pubsub adapter|
||consensus protocols interfaces|
||consensus implementation over raft|
||multiple pubsub over libp2p implementations|
||a simple RPC library for libp2p|
||multiaddr filtering helpers|
||length prefixed data channel|
||address utilities for libp2p swarm|
||a variable size buffer pool for go|
||enables reuse of addresses|
||utils for sockaddr conversions|
||Go ‘net’ wrappers for libp2p|
||HTTP on top of libp2p streams|
|Testing and examples|
||a collection of testing utilities for libp2p|
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.
- read the libp2p spec
- please make branches + pull-request, even if working on the main repository
- ask questions or talk about things in issues, our discussion forums, or #libp2p or #ipfs on freenode.
- ensure you are able to contribute (no legal issues please — we use the DCO)
go fmtbefore pushing any code
go vettoo — some things (like protobuf files) are expected to fail.
- get in touch with @raulk and @mgoelzer 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.
The last gx published version of this module was: 6.0.41: QmTRN7hRxvGkxKxDdeudty7sRet4L7ZKZCqKsXHa79wmAc