IDs and Encoding

Knowing the overall message structure is great, but it’s not very useful if you can’t construct the metadata. To do this, there are four parts.

base_58

This encoding is taken from Bitcoin. If you’ve ever seen a Bitcoin address, you’ve seen base_58 encoding in action. The goal behind it is to provide data compression without compromising its human readability. Base_58, for the purposes of this protocol, is defined by the base58 python module.

Subnets

The last element is the ‘subnet ID’ we referred to in the previous section. This object is used to weed out undesired connections. If someone has the wrong protocol object, then your node will reject them from connecting. A rough definition would be as follows:

class protocol(namedtuple("protocol", ['subnet', 'encryption'])):
    @property
    def id(self):
        info = [str(x) for x in self] + [protocol_version]
        h = hashlib.sha256(''.join(info).encode())
        return base58.b58encode(h.digest())

Or more explicitly in javascript:

class protocol {
    constructor(subnet, encryption) {
        this.subnet = subnet;
        this.encryption = encryption;
    }

    get id() {
        var info = [this.subnet, this.encryption, protocol_version];
        var hash = SHA256(info.join(''));
        return to_base_58(BigInt(hash, 16));
    }
}

Node IDs

A node ID is taken from a SHA-384 hash of three other elements. First, your outward facing address. Second, the ID of your subnet. Third, a ‘user salt’ generated on startup. This hash is then converted into base_58.

Message IDs

A message ID is also a SHA-256 hash. In this case, it is on a message’s payload and metadata

To get the hash, first join each packet together in the order: [msg.msg_type, msg.sender, msg.time, ...msg.payload]. Then encode this in msgpack, pass it through SHA-256, and return the resulting binary digest.