libp2p implementation in Nim https://status-im.github.io/nim-libp2p/docs/
Go to file
Giovanni Petrantoni 3b69cef2d2
Fix CI, chronicles bump (#122)
* Disable new fragmentation tests

* Bump chronicles version requirement
2020-03-27 15:02:21 +09:00
doc Update Readme (#103) 2020-03-16 08:43:08 +01:00
examples Update Readme (#103) 2020-03-16 08:43:08 +01:00
libp2p Allow to specify a read size in readLp (#117) 2020-03-26 15:06:47 +09:00
tests Disable new fragmentation tests (#119) 2020-03-27 10:47:30 +09:00
.appveyor.yml Fix Appveyor problems with go-lang bug. 2019-10-07 21:56:08 +03:00
.gitignore misc: cleanup mplex 2019-10-11 08:15:24 +09:00
.travis.yml Cleanup (#55) 2019-12-10 14:50:35 -06:00
LICENSE Initial commit 2018-11-19 03:58:31 +02:00
LICENSE-APACHEv2 Initialize travis and licenses. 2018-11-19 04:04:47 +02:00
LICENSE-MIT Initialize travis and licenses. 2018-11-19 04:04:47 +02:00
README.md Update README.md 2020-03-16 16:17:31 +08:00
azure-pipelines.yml Set up CI with Azure Pipelines (#72) 2020-02-06 16:07:50 +01:00
libp2p.nim Fixes and tweaks related to the beacon node integration 2019-12-08 23:58:43 +02:00
libp2p.nimble Fix CI, chronicles bump (#122) 2020-03-27 15:02:21 +09:00

README.md

libp2p hex logo

The Nim implementation of the libp2p Networking Stack.

Introduction

An implementation of libp2p in Nim. Also provides a Nim wrapper of the Libp2p Go daemon.

Project Status

The current native Nim libp2p implementation support is experimental and shouldn't be relied on for production use. It is under active development and contributions are highly welcomed. :)

Check our examples folder to get started!

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 the 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 suite of networking protocols 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.

  • Learn more about libp2p at libp2p.io and follow our evolving documentation efforts at docs.libp2p.io.
  • Here is an overview of libp2p and its implementations in other programming languages.

Install

nimble install libp2p

Prerequisite

Usage

API

The specification is available on API.md (coming soon).

Getting Started

Please read the GETTING_STARTED.md guide.

Tutorials and Examples

Examples can be found in the examples folder.

Using the Go Daemon

Please find the installation and usage intructions in GO_DAEMON.md.

Examples can be found in the examples/go-daemon folder;

Development

Clone and Install dependencies:

git clone https://github.com/status-im/nim-libp2p
cd nim-libp2p
nimble install

Tests

Prerequisite

Run unit tests

# run all the unit tests
nimble test

Packages

List of packages currently in existence for nim-libp2p:

Libp2p

Transports

Secure Channels

Stream Multiplexers

Utilities

Data Types

Pubsub

Packages that exist in the original libp2p specs and are under active development:

  • libp2p-daemon
  • libp2p-webrtc-direct
  • libp2p-webrtc-star
  • libp2p-websockets
  • libp2p-spdy
  • libp2p-bootstrap
  • libp2p-kad-dht
  • libp2p-mdns
  • libp2p-webrtc-star
  • libp2p-delegated-content-routing
  • libp2p-delegated-peer-routing
  • libp2p-nat-mgnr
  • libp2p-utils

** Note that the current stack reflects the minimal requirements for the upcoming Eth2 implementation.

Contribute

The libp2p implementation in Nim is a work in progress. We welcome contributors to help out! Specifically, you can:

  • Go through the modules 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 infrastructure behind it.
  • Perform code reviews. Feel free to let us know if you found anything that can a) speed up the project development b) ensure better quality and c) reduce possible future bugs.
  • Add tests. Help nim-libp2p to be more robust by adding more tests to the tests folder.

Core Developers

@cheatfate, Dmitriy Ryajov, Giovanni Petrantoni, Zahary Karadjov

License

Licensed and distributed under either of

or

at your option. This file may not be copied, modified, or distributed except according to those terms.