tl;dr webrtc-explorer is a Chord inspired P2P overlay network designed for the Web platform (browsers), using WebRTC as its transport between peers and WebSockets for Signaling data. Essentially, it enables your peers (browsers) to communicate between each other without the need to have a server as a mediator of messages.


• Ids have 48 bits (so that is a multiple of 4 (for hex notation) and doesn't require importing a big-num lib to handle over 53 bits operations)
• The number of fingers of each peer is flexible, however it is recommended to not pass 16 per node (due to browser resource constraints)
• Each peer is responsible for a segment of the hash ring
• The signaling server for webrtc-explorer can be found at: https://github.com/diasdavid/webrtc-explorer-signalling-server

webrtc-explorer uses browserify

var Explorer = require('webrtc-explorer');

var config = {
    signalingURL: 'https://url-to-webrtc-ring-signaling-server.com'
};
var peer = new Explorer(config);

peer.events.on('ready', function () {
    // this node is ready
});

peer.events.on('registered', function(data){
    // peer registered with data.peerId
});

peer.register();

peerIds are 48 bits represented in a string using hex format. To send, in one peer:

var data = 'hey peer, how is it going';

peer.send('abcd0f0fdbca', data);

To receive, in another peer (responsible for that Id)

peer.events.on('message', function(envelope){
    // message from the other peer envelope.data
});

add the logging flag to your config

var config = {
    //...
    logging: true
};

To understand fully webrtc-explorer's core, it is crucial to be familiar with the Chord. webrtc-explorer levarages important battle experience from building webrtc-ring - https://blog.daviddias.me/2014/12/20/webrtc-ring

• I'll upload my notes and images soon, I'm trying to make them as legible as possible. If you have a urgency in one of the parts, please let me know, so that I put that one as a priority.