BLIP6: Make BloomID DID Compatible

[ipatka]

Simple Summary

Make the BloomID mobile app DID compatible to improve interoperability.

Abstract

Bloom uses Ethereum keypairs to identify unique BloomID users. Users currently sign up for Bloom by downloading the iOS app, Android app or via Metamask on web. Bloom should add DIDs to user profiles which resolve to documents explaining the BloomID schema.

Motivation

This change will improve Bloom's interoperability within the decentralized identity ecosystem.

Specification

The below example is taken from the W3C DID Data Model Draft v0.12 (https://w3c-ccg.github.io/did-spec/)

TODO update this with example Bloom DID document.

{
  "@context": "https://w3id.org/did/v1",
  "id": "did:example:123456789abcdefghi",
  "authentication": [{
    // this key can be used to authenticate as did:...fghi
    "id": "did:example:123456789abcdefghi#keys-1",
    "type": "RsaVerificationKey2018",
    "controller": "did:example:123456789abcdefghi",
    "publicKeyPem": "-----BEGIN PUBLIC KEY...END PUBLIC KEY-----\r\n"
  }],
  "service": [{
    "type": "ExampleService",
    "serviceEndpoint": "https://example.com/endpoint/8377464"
  }]
}

Rationale

TODO

Backwards Compatibility

Within the Bloom ecosystem no changes will be needed because Bloom endpoints already know how to interpret BloomIDs. Once this change is made users will likely need to update their mobile app in order to interface with other DID compliant services.

Test Cases

TODO

Implementation

TODO

Copyright

Copyright and related rights waived via CC0. Based on the Ethereum Improvement Proposal template.