Skip to main content

Linked Verifiable Presentations

The UniTrust instances A, B and C have the same initial configuration and are publicly available. Instance A fulfills the role of the Issuer, instance C is the Holder and instance B is the Verifier in this scenario. All instances can serve all roles in different scenarios without redeployments or changes in configuration.

Flow description​

  1. A publishes its DID document (including its public keys) to the IOTA network
  2. A creates a credential including some statement about C (such as an endorsement or statement of collaboration)
  3. A offers the credential to C
  4. C checks the offer, accepts the credential and stores it in their organizational wallet (non-public)
  5. C decides to present this credential to the public by including it in its DID document, then publishes an update to the IOTA network
  6. Organization B wants to make business with C and wants to assess the trustworthiness before proceeding. B resolves the IOTA DID document (found through domain linkage under the domain https://identity.example.com) and finds the endorsement credential originally signed by A. B can be sure that C is endorsed by A and decides if it wants to proceed with business.