The following functions are desirable to implement the Identity Issuer. It would be great if all live in the same package called idiss fn validate_request(_idr :IdentityObjectRequest) -> bool This function returns true if the IdentityObjectRequest _idr is valid or not fn createIdentityObject(_idr :IdentityObjectRequest, _idi :IdentityInfo, _privateKey :string) -> IdentityObject This function returns a signed IdentityObject. It use the _privateKey to sign.

Author Pelle Braendgaard pelle@notabene.id Andres Junge andres@notabene.id Preface The conc DID method specification conforms to the requirements specified in the DID specification, currently published by the W3C Credentials Community Group. For more information about DIDs and DID method specifications, please see the DID Primer Abstract Decentralized Identifiers (DIDs, see [1]) are designed to be compatible with any distributed ledger or network.

# ethr-did for private networks The `ethr-did` method registers all the "key operations" in a smart contract on any EVM compatible network. The `ethr-did-resolver` can resolve any `ethr-did` on the most popular Ethereum networks (mainnet, rinkeby, kovan, etc), but also can be configured to resolve on private networks. Before resolving a `did` on a private network the smart contract (the registry) needs to be deployed on the network. Also the resolver needs to be configured to use this registry