Use DIDs

[fazo96]

Big changes to the whole implementation to drop keypairs in favor of a Distributed IDentity system for identifying Vendors, Marketplaces and Customers.

The Vendor-Marketplace cosigned key is still a key using the old system and not a DID.

Most impacted internal modules:

• OrbitDB: added new functionality so that it acts as a DID ID to DID Multihash map to lookup DID Documents by ID. This is used automatically
• Crypto module: moved some functionality to the DID module for operations that are now done using DIDs such as signReviewRecord
• DID module: this is new
• IPFS Utils module: has new functions to put/get objects as JSON in IPFS. This is because the DIDs are stored in IPFS using the dag-pb format with a string with json inside. Instead, the other data structures are stored with dag-pb and our protobuf encoded binaries inside
• Persistence: the customer key does not exist anymore, instead a DID is created, published and persisted automatically. Can also be imported or exported (we will use this in the wallet)
• Validator: now expects/uses DIDs

Impact in other projects:

Other projects will need to be updated for these changes

• [ ] Wallet: will need to use the DID functions through ChluIPFS
• [ ] Marketplace: will need to use DIDs for itself and for the vendors instead of keys

What's missing

• [x] key_location and fields like that should not be used for DIDs like they are in this version, I should use new protobuf fields (following our short discussion on slack). I forgot to do this before submitting the PR
• [x] importing a DID should publish it if it's not published yet
• [ ] Security: DID put operations in orbit-db should be DID-Signed. Even better, we should also get orbit-db to use the DID keypair for its own signing operations no, better push this to later. DID get operations should then verify the signature
• [x] crypto module should use elliptic for the crypto stuff
• [ ] update the protocol to reflect these changes
• [ ] unverified reviews need to be implemented and properly handled

[kulpreet]

@fazo96 about

IPFS Utils module: has new functions to put/get objects as JSON in IPFS. This is because the DIDs are stored in IPFS using the dag-pb format with a string with json inside. Instead, the other data structures are stored with dag-pb and our protobuf encoded binaries inside

Should we not try to align these?

[fazo96]

IPFS Utils module: has new functions to put/get objects as JSON in IPFS. This is because the DIDs are stored in IPFS using the dag-pb format with a string with json inside. Instead, the other data structures are stored with dag-pb and our protobuf encoded binaries inside

Should we not try to align these?

@kulpreet good point, here's how it works now

Verified Reviews

object --> protobuf binary buffer (using our protobufs) --> (we enter IPFS logic here) dag-pb binary buffer --> IPFS

Unverified Reviews

Let's not focus on unverified reviews in this PR, but I'm including this to be thorough

object --> String (using JSON.stringify) --> utf-8 encoded binary buffer --> (we enter IPFS logic here) dag-pb binary buffer --> IPFS

DIDs

object --> String (using JSON.stringify) --> utf-8 encoded binary buffer --> (we enter IPFS logic here) dag-pb binary buffer --> IPFS

@kulpreet We can either use JSON for Verified Reviews or we write/use protobufs for DIDs and Unverified Reviews. I'd go for JSON but I trust your judgement more on these kind of things, so it's up to you and I think you said on slack we'll go with protobufs

About Unverified Reviews, I'd leave that out of this PR and just focus on DIDs for now