Abstract: A request is generated for verifiable claims that are related to services that a user is to provide to an entity that requests the services from the user. The request for the services is then provided to the requesting entity. The requested verifiable claims are then received from the requesting entity and are verified to determine that they are valid. If the received verifiable claims are valid, the user is authorized to provide the services to the requesting entity.

Abstract: The presentation of a verifiable credential that is represented within a data structure that represents the verifiable credential as well as usage data of the verifiable credential. The usage of the verifiable credential is monitored, such that as usage of the verifiable credential changes or progresses, the stored usage data also changes. This data structure may be used to not only cause visual representations of the verifiable credential to be displayed to the user, but the user can selectively cause at least some of that usage data to also be presented to the user. Thus, the user can easily keep track of how their verifiable credential is being used, regardless of where or from which device the verifiable credential is presented.

Abstract: The resolving of a decentralized identifier at a customized security level. When a decentralized identity is resolved, it is resolved into a data structure (e.g., a document) that corresponds to the decentralized identity. The resolving includes causing a user interface to be rendered to the user, detecting user interaction with the user interface, and then based on that user interaction identifying a level of resolver security to use when resolving that decentralized identifier. The method then resolve the decentralized identity using that identifier level of resolver security. As an example, higher levels of resolver security may be obtained by using consensus from multiple resolvers.

Abstract: Embodiments disclosed herein are related to computing systems and methods for a DID owner to select a permission scope for sharing DID-associated data. A set of permission scopes are accessed for DID-associated data. The DID-associated data is associated with a DID of a DID owner. The set of permission scopes define entities whom are to be given access to the DID-associated data by the DID owner. The DID owner is prompted to select a specific permission scope of the set of permission scopes for one or more of the DID-associated data. The selected permission scope is applied to the one or more of DID-associated data. The selected permission scope defines the specific entities that are to be given access to the one or more of the DID-associated data.

Abstract: Embodiments disclosed herein are related to computing systems and methods for generating one or more pseudonymous names for use by a Decentralized Identifier (DID) owner when interacting with third party entities. An indication is received from a DID owner who is associated with a DID. The indication indicates that the DID owner desires to interact with various third party entities. A list is generated of pseudonymous names that are to be used in place of the DID as the DID owner interacts with the one or more third party entities. A selection is received for a specific one of the generated pseudonymous names. The selected specific pseudonymous name is bound to the DID so that the selected specific pseudonymous name is used during the interaction.

Abstract: The presentation of a verifiable credential that is represented within a data structure that represents the verifiable credential as well as usage data of the verifiable credential. The usage of the verifiable credential is monitored, such that as usage of the verifiable credential changes or progresses, the stored usage data also changes. This data structure may be used to not only cause visual representations of the verifiable credential to be displayed to the user, but the user can selectively cause at least some of that usage data to also be presented to the user. Thus, the user can easily keep track of how their verifiable credential is being used, regardless of where or from which device the verifiable credential is presented.

Abstract: The resolving of a decentralized identifier at a customized security level. When a decentralized identity is resolved, it is resolved into a data structure (e.g., a document) that corresponds to the decentralized identity. The resolving includes causing a user interface to be rendered to the user, detecting user interaction with the user interface, and then based on that user interaction identifying a level of resolver security to use when resolving that decentralized identifier. The method then resolve the decentralized identity using that identifier level of resolver security. As an example, higher levels of resolver security may be obtained by using consensus from multiple resolvers.

Abstract: Embodiments disclosed herein are related to computing systems and methods for a DID owner to select a permission scope for sharing DID-associated data. A set of permission scopes are accessed for DID-associated data. The DID-associated data is associated with a DID of a DID owner. The set of permission scopes define entities whom are to be given access to the DID-associated data by the DID owner. The DID owner is prompted to select a specific permission scope of the set of permission scopes for one or more of the DID-associated data. The selected permission scope is applied to the one or more of DID-associated data. The selected permission scope defines the specific entities that are to be given access to the one or more of the DID-associated data.

Abstract: Embodiments disclosed herein are related to computing systems and methods for generating one or more pseudonymous names for use by a Decentralized Identifier (DID) owner when interacting with third party entities. An indication is received from a DID owner who is associated with a DID. The indication indicates that the DID owner desires to interact with various third party entities. A list is generated of pseudonymous names that are to be used in place of the DID as the DID owner interacts with the one or more third party entities. A selection is received for a specific one of the generated pseudonymous names. The selected specific pseudonymous name is bound to the DID so that the selected specific pseudonymous name is used during the interaction.