libp2p implementation in Go
Go to file
Jeromy Johnson be1f55801d Merge pull request #22 from ipfs/feat/fallback-dialer
Add fallback dialer
2016-03-04 16:49:02 -08:00
loggables update version of go-multiaddr 2016-03-03 13:03:24 -08:00
p2p fix fallback code and add a few new tests 2016-03-04 16:16:58 -08:00
testutil update version of go-multiaddr 2016-03-03 13:03:24 -08:00
.gitignore vendor in go-detect-race 2015-11-23 17:04:47 -08:00
.travis.yml fix fallback code and add a few new tests 2016-03-04 16:16:58 -08:00
CONTRIBUTE.md added docs 2015-09-30 19:08:00 -04:00
LICENSE added docs 2015-09-30 19:08:00 -04:00
Makefile fix gx installs to gateway 2016-03-03 14:41:39 -08:00
README.md Remove superfluous square bracket 2016-02-16 20:57:34 +01:00
TODO migrate to gx namespace 2015-11-18 16:11:24 -08:00
package.json use multiaddr format to do validation of addresses 2016-03-03 14:56:00 -08:00

README.md

libp2p implementation in Go.

GoDoc Build Status

libp2p implementation in Go

Description

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.

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

Contribute

libp2p implementation in Go is a work in progress. As such, 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.

Usage

go-libp2p repo will be a place holder for the list of Go modules that compose Go libp2p, as well as its entry point.

Install

$ go get -u github.com/ipfs/go-libp2p

Run tests

$ cd $GOPATH/src/github.com/ipfs/go-libp2p
$ GO15VENDOREXPERIMENT=1 go test ./p2p/<path of folder you want to run>

Interface

Modules

  • libp2p (entry point)
  • Swarm
  • Peer Routing
    • libp2p-kad-routing
    • libp2p-mDNS-routing
  • Discovery
    • libp2p-mdns-discovery
    • libp2p-random-walk
    • libp2p-railing
  • Distributed Record Store
  • Generic
    • PeerInfo
    • PeerId
    • multihash
    • multiaddr
    • multistream
    • multicodec
    • ipld
    • repo
  • Specs
  • Website