Stream that implements the hypercore protocol
npm install hypercore-protocol
For detailed info on the messages sent on each channel see simple-hypercore-protocol
Note that the latest version of this is Hypercore Wire Protocol 7, which is not compatible with earlier versions.
const Protocol = require('hypercore-protocol')
// create two streams with hypercore protocol
const streamA = new Protocol(true) // true indicates this is the initiator
const streamB = new Protocol(false) // false indicates this is not the initiator
// open two feeds specified by a 32 byte key
const key = Buffer.from('deadbeefdeadbeefdeadbeefdeadbeef')
const channel = streamA.open(key)
const remoteFeed = streamB.open(key, {
// listen for data in remote feed
ondata (message) {
console.log(message.value.toString())
}
})
// add data to feed
channel.data({ index: 1, value: '{ block: 42 }'})
streamA.pipe(streamB).pipe(streamA)
output => { block: 42 }
Create a new protocol duplex stream.
Options include:
{
encrypted: true, // set to false to disable encryption if you are already piping through a encrypted stream
noise: true, // set to false to disable the NOISE handshake completely. Requires encrypted = false, and also disables the capability verification
timeout: 20000, // stream timeout. set to 0 or false to disable.
keyPair: { publicKey, secretKey }, // use this keypair for the stream authentication
onauthenticate (remotePublicKey, done) { }, // hook to verify the remotes public key
onhandshake () { }, // function called when the stream handshake has finished
ondiscoverykey (discoveryKey) { }, // function called when the remote stream opens a channel you have not
onchannelclose (discoveryKey, publicKey) { } // function called when a feed-channel closes
}
Emitted when the remote opens a feed you have not opened.
Also calls stream.handlers.ondiscoverykey(discoveryKey)
Emitted when the stream times out. Per default a timeout triggers a destruction of the stream, unless you disable timeout handling in the constructor.
Set a stream timeout.
Send a keep alive ping every ms, if no other message has been sent. This is enabled per default every timeout / 2 ms unless you disable timeout handling in the constructor.
A nanoguard instance that is used to guard the final closing of the stream. Internally this guard is ready'ed before the stream checks if all channels have been closed and the stream is finalised. Call wait/continue on this guard if need asynchrously add more channels and don't want to stream to finalise underneath you.
The remotes public key.
Your public key.
The remote peers IP if piped over a TCP or UTP stream.
The remote peers connection type. Either 'tcp', 'utp', or 'unknown'.
Returns true if the remote sent a valid capability for the key when they opened the channel.
Use this in ondiscoverykey
to check that the remote has the key corresponding to the discovery key.
Static method to check if an object is a hypercore protocol stream.
Static method to generate an static authentication key pair.
Signal the other end that you want to share a hypercore feed.
The feed key will be hashed and sent as the "discovery key" which protects the feed key from being learned by a remote peer who does not already possess it. Also includes a cryptographic proof that the local possesses the feed key, which can be implicitly verified using the above remoteVerified
api.
See the protobuf schema for more info on this messsage
The handlers
is an object of functions for handling incoming messages and is described below.
You can call this method to signal to the other side that you do not have the key
corresponding to the discoveryKey. Normally you would use this together with the ondiscoverykey
hook.
Destroy the stream. Closes all feeds as well.
Gracefully end the stream. Closes all feeds as well. This is automatically called after the prefinalise guard and all channels have been closed.
Send an options
message. See the protobuf schema for more info on this messsage
Called when a options message has been received.
Send an status
message. See the protobuf schema for more info on this messsage
Called when a status message has been received.
Send a have
message. See the protobuf schema for more info on this messsage
Called when a have
message has been received.
Send a unhave
message. See the protobuf schema for more info on this messsage
Called when a unhave
message has been received.
Send a want
message. See the protobuf schema for more info on this messsage
Called when a want
message has been received.
Send a unwant
message. See the protobuf schema for more info on this messsage
Called when a unwant
message has been received.
Send a request
message. See the protobuf schema for more info on this messsage
Called when a request
message has been received.
Send a cancel
message. See the protobuf schema for more info on this messsage
Called when a cancel
message has been received.
Send a data
message. See the protobuf schema for more info on this messsage
Called when a data
message has been received.
Send an extension
message. id
should be the index an extension name in the extensions
list sent in a previous options
message for this channel.
Called when an extension
message has been received. id
is the index of an extension name received in an extension list in a previous options
message for this channel.
Close this channel. You only need to call this if you are sharing a lot of feeds and want to garbage collect some old unused ones.
Called when this feed has been closed. All feeds are automatically closed when the stream ends or is destroyed.
An alias to stream.destroy
.
You can also send custom messages over the stream unrelated to any channel or hypercore feed. You usually don't need this but can be useful if you are bootstrapping a specific protocol on top.
Register a new stream extension named name
.
handlers.onmessage(message)
is called when an unchanneled extension message is received for this extension.handlers.onerror(error)
in case there was an encoding error.handlers.encoding
can be set tojson
,utf-8
,binary
or any abstract encoding to automatically decode/encode messages.
Send an extension message.
Destroy this extension. Unregisters it from the stream as well.
The hypercore protocol consists of two phases. A handshake phase and a message exchange phage.
For the handshake Noise is used with the XX pattern. Each Noise message is sent with varint framing. After the handshake a message exchange phased is started.
This uses a basic varint length prefixed format to send messages over the wire.
All messages contains a header indicating the type and feed id, and a protobuf encoded payload.
message = header + payload
A header is a varint that looks like this
header = numeric-feed-id << 4 | numeric-type
The feed id is just an incrementing number for every feed shared and the type corresponds to which protobuf schema should be used to decode the payload.
The message is then wrapped in another varint containing the length of the message
wire = length(message) + message + length(message2) + message2 + ...
MIT