Skip to main content

Credentials

warning

This feature is currently in the experimental stage of development. Do not use it in production environments or presume it is secure. Expect breaking changes.

The Credentials screen allows a user to decrypt, accept, or issue verifiable credentials. Users must register a schema on the MDIP network, or select an existing schema's DID, before a credential can be issued.

The credential's subjects are listed from known Agent DIDs contained in the wallet (from the IDENTITIES and DIDS screens).

Credentials screen

The credential screen also allows the issuing user to fill in the credential with recipient-specific content. The credential below attests Bob's membership to Alice:

Issue Credential

HELD Screen​

In the "HELD" Credentials screen, a user can chose from a variety of options:

Held Credentials

  • Resolve: This will display the public (encrypted) view of the credential. Resolving a credential confirms it exists in the MDIP Gatekeeper node.

  • Decrypt: If the credential is encrypted to the current DID, this will decrypt the cypher_receiver field using the DID keys.

  • Remove: This removes a credential from the user's wallet.

  • Publish: This publishes the existence of the credential to the DID manifest, which is visible to the public. The content of the credential is nulled, but the header contains valuable information, notably the DID of the issuer and the DID of the credential schema.

  • Reveal: This reveals the full content of a credential to the DID manifest, which is visible to the public. The content of the credential is decrypted and included in the DID manifest.

  • Unpublish: This removes the credential from a DID manifest. Note: other nodes on the network may retain the history of a DID; once published or revealed a credential has been winessed by other nodes.

The image below shows a portion of Bob's Agent DID with a revealed "isMember: true" credential in the visible portion of his DID document:

revealed membership