feat: record interface

[vasco-santos]

This PR adds the record-interface.

The record-interface primary goal is to guarantee that any record implementation will be compliant with the expectations of a libp2p envelope.

js-libp2p will start by having a single implementation of the record-interface, known as a peer-record. This implementations will be used to share peers' multiaddrs across the network with security guarantees, thanks to the libp2p envelope where the records will be wrapped into.

Open questions:

• Should we have tests for the unmarshal operation in the interface tests? I think that we should have the unmarshal and then rely on isEqual to verify if the unmarshal operation resulted in the same content as before the marshal

A record implementation will now look as follows:

class PeerRecord extends Record {
  // ....
}

PeerRecord.createFromProtobuf = (buf) => {
  // ...
}

module.exports = PeerRecord

The createFromProtobuf will return an instance of the Peer Record.

References:

• RFC: Signed Address Records specs#217
• https://github.com/libp2p/go-libp2p-core/blob/master/record/record.go

[jacobheun]

Looks good aside from the change from isEqual to equals

[vasco-santos]

This should be ready to get merged in.
@jacobheun would you prefer this to get merged on a 0.3 branch before rolling all the releases?

[jacobheun]

would you prefer this to get merged on a 0.3 branch

master is 0.3 and I think we're fine to move there, this is backwards compatible.

[vasco-santos]

lol yes, github UI shows the latest release in the git repo and not the latest 🤦‍♂️