Java Smalltalk Makefile Shell Batchfile PowerShell
Latest commit 8c6ca04 May 19, 2017 @gappleto97 gappleto97 Migrate C++ to submodule
Permalink
Failed to load latest commit information.
.scripts
c2p @ d0073d2 Add c2p as submodule May 19, 2017
cp2p @ 4b05313 Migrate C++ to submodule May 19, 2017
docs Migrate js to submodule May 19, 2017
js2p @ 70b6813 Update submodule May 19, 2017
jv_src Increment version number Jan 1, 2017
py2p @ 359b2c6 Correct minor makefile error May 19, 2017
sm_src
.babelrc Add compatability plugin Feb 8, 2017
.codeclimate.yml Disable require check Apr 27, 2017
.codecov.yml Add codecov config (will cause merge issues later) Jan 23, 2017
.coveragerc Fix errors Aug 25, 2016
.gitattributes Correct language statistics [skip ci] Nov 15, 2016
.gitignore Add beginings of sphinx documentation Aug 3, 2016
.gitmodules Migrate C++ to submodule May 19, 2017
.npmignore Add .npmignore [skip ci] Oct 12, 2016
.travis.yml Add testing for node v7 May 5, 2017
CONTRIBUTING.rst Update python documentation Sep 2, 2016
LICENSE Relicense to LGPL v3 Jun 3, 2016
Makefile Make builds work again May 19, 2017
README.md Correct typos and add ethereum address [skip ci] Apr 11, 2017
Senior Project Longform.pdf Add paper for project turnin Apr 30, 2017
appveyor.yml Add testing for node v7 May 5, 2017
c_src Add symlink to c_src (temporary measure) May 19, 2017
js_src Migrate js to submodule May 19, 2017
py_src Switch python to track submodule May 19, 2017
shippable.yml Add testing for node v7 May 5, 2017

README.md

To see a better formatted, more frequently updated version of this, please visit docs.p2p.today, or for the develop branch, dev-docs.p2p.today.

Current build status:

shippable travis appveyor codeclimate codecov

waffleio_queued waffleio_in_progress waffleio_in_review

Goal

We are trying to make peer-to-peer networking easy. Right now there's very few libraries which allow multiple languages to use the same distributed network.

We're aiming to fix that.

What We Have

There are several projects in the work right now. Several of these could be considered stable, but we're going to operate under the "beta" label for some time now.

Base Network Structures

All of our networks will be built on common base classes. Because of this, we can guarantee some network features.

  1. Networks will have as much common codebase as possible
  2. Networks will have opportunistic compression across the board
  3. Node IDs will be generated in a consistent manner
  4. Command codes will be consistent across network types

Mesh Network

This is our unorganized network. It operates under three simple rules:

  1. The first node to broadcast sends the message to all its peers
  2. Each node which receives a message relays the message to each of its peers, except the node which sent it to them
  3. Nodes do not relay a message they have seen before

Using these principles you can create a messaging network which scales linearly with the number of nodes.

Currently there is an implementation in Python and Javascript. More tractable documentation can be found in their tutorial sections. For a more in-depth explanation you can see it's specifications or this slideshow.

Sync Table

This is an extension of the above network. It inherits all of the message sending properties, while also syncronizing a local dictionary-like object.

The only limitation is that it can only have string-like keys. There is also an optional "leasing" system, which is enabled by default. This means that a user can own a particular key for a period of time.

Currently there is an implementation in Python and Javascript. More tractable documentation can be found in their tutorial sections. Protocol specifications are in progress.

Chord Table

This is a type of distributed hash table based on an MIT paper which defined it.

The idea is that you can use this as a dictionary-like object. The only limitation is that it can only have string-like keys. It uses five separate hash tables for hash collision avoidance and data backup in case a node unexpectedly exits.

Currently there is an implementation in Python and Javascript. More tractable documentation can be found in their tutorial sections. Protocol specifications are in progress.

Contributing, Credits, and Licenses

Contributors are always welcome! Information on how you can help is located on the Contributing page.

Credits and License are located on their own page.

Donate

Bitcoin: 1BwVXxPj9JSEUoAx3HvcNjjJTHb2qsyjUr

Ethereum: 0x0eb3BD61f48959662AC9411E5A2EC71aC845B687