Multiplex encrypted connections to peers over a p2p network.
npm i -s p2plex
const p2plex = require('p2plex')
const plex1 = p2plex()
const plex2 = p2plex()
plex1.on('connection', (peer) => {
peer.receiveStream('example').on('data', (data) => {
console.log('Got data from', peer.publicKey, ':', data.toString('utf8'))
plex1.destroy()
plex2.destroy()
})
})
plex2.findByPublicKey(plex1.publicKey).then((peer) => {
peer.createStream('example').end('Hello World!')
})
This module combines Hyperswarm for P2P networking, Noise-peer for encrypted communication, and Multiplex for sending multiple streams over a single connection. The deduplication happens under the hood. Your application should focus on opening and closing streams on peers and not worry about whether the peer has just connected or it was connected already. Once all the multiplexed streams for a peer end, the connection will be dropped automatically.
Initialize a new p2plex instance.
keyPair
: is a public/private key pair for transport encryption / authentication. If you don't specify one, it will be auto-generated.listenSelf
: This controls whether you'll start advertising yourself for people to find you withfindByPublicKey
.true
by default.opts
: These options get passed down tohyperswarm
andnoise-peer
. This gives you more control over those modules if you know what you're doing.
This is a Buffer object containing your public key. Your application can use this as your identity in the swarm and can be exchanged with peers to enable connecting to you later.
This is an object containing your key pair with the publicKey
and secretKey
. You might want to save this for later if you want a persistant identity.
This is a Set of all the currently connected peers.
This is the raw hyperswarm instance. You probably shouldn't mess with it unless you really know what you're doing.
This event gets emitted every time a new peer gets connected.
peer
: is aPeer
object representing the connection to someone in the network.
This method will attempt to discover a peer with the given public key on the network. You should probably wrap this in a timeout. PRs for introducing cancellation would be appreciated.
publicKey
is a Buffer containing the other peers' public key.peer
: is aPeer
object representing the connection to someone in the network.
This method will attempt to discover a peer under a given topic with a given public key.
If you don't specify the announce and lookup options, the defaults will be used.
You should probably wrap this in a timeout. PRs for introducing cancellation would be appreciated.
Note: There's currently a bug where the deduplication logic ends up emitting errors. To mitigate this, have one side set announce:true,lookup:false
and the other side set announce:false,lookup:true
.
topic
should be a 32 byte Buffer which is the key you want to use to find other peers.publicKey
is a Buffer containing the other peers' public key.announce
sets whether you will be announcing your existance for this key to get incoming peer connections.lookup
Sets whether you will be actively searching for peers on the network and making outgoing connections.peer
: is aPeer
object representing the connection to someone in the network.
Starts finding peers on the network. Resolves once a full lookup has been completed. You usually don't need to await this promise and keep going while it does stuff in the background.
topic
should be a 32 byte Buffer which is the key you want to use to find other peers.announce
sets whether you will be announcing your existance for this key to get incoming peer connections.lookup
Sets whether you will be actively searching for peers on the network and making outgoing connections.
Stops finding peers on the network and removes all trace of itself from the p2p network for this key.
topic
should be a 32 byte Buffer which is the key you want to use to find other peers.
Gracefully disconnects from all peers, removes itself from the p2p network, and shuts down the p2p network instance.
Every peer will have their public key populated so that you can verify their identity or save it for use later.
A boolean representing whether this peer represents an incoming connection or an outgoing connection.
This is an array of topic names that this peer has been discovered for on the network. Might be empty for incomming connections.
This gets emitted when a topic has been associated with a peer. This gets emitted when peer initially connects, and then whenever the swarm discovers them advertising on another topic after already connecting.
This gets emitted when the peer gets a new stream over the multiplex connections.
stream
Is a node-style Duplex stream you can read and write from.id
is a String representing the name given to the stream when it was being created.
This gets emitted when the peer's connection has been severed at the network level.
This gets emitted when there is an error either in the connection or the multiplex module
Create a stream over the multiplexer. The other side should use peer.receiveStream(id)
to get the stream.
id
is a string which identifies the stream on both sides.
Recieves a stream over the multiplexer. The other side should use peer.createStream(id)
to get the stream.
Create a shared stream over the multiplexer. If both sides create a shared stream with the same id, data from one end will go to the other.
Tell the swarm to avoid connecting to this peer in the future. This can be useful if there's misbehaving peers or giving users more control.
Gracefully disconnects from the peer and resolves once the disconnection is complete.
Big thanks to playproject.io for sponsoring this work for use in the DatDot project.