Resolve Peer DID

NOTE:Only DID:peer:2. (method type 2) is supported.

  

Resolver Result ::

Create a DID:peer

To create a new DID:peer, you need to provide at least one key. You can add more keys and services if needed.
NOTE: Only DID:peer:2. (method type 2) is supported.

Keys

DID:peer supports two types of keys: Verification and Encryption. You can add multiple keys of each type.

  • Verification
    		•  - Appears in the DID Document authentication and assertionMethod fields
  • Recommend Ed25519 key type for signing
    		•
  • Encryption
    		•  - Appears in the DID Document keyAgreement field
  • Recommend Secp256K1 key type for encryption, supports recryption capabilities
    		•

    You can specify an existing Multibase Public Key if already created (i.e. for example did:key:(z6Mk...)).
    If left blank, keys will be autogenerated and private keys shown below.

    Important: For DIDComm you must create a new DID:peer with at least one Verification and one Encryption key.

    NOTE: The order of these keys reflects the key identifier names used!
    NOTE: For simplicity auto-generated keys are Ed25519 based. EdDSA + Curve25519

    Key ID Purpose Type Multibase Public Key

    Services

    DID:peer allows you to specify service statements that can be used for example to describe how DIDComm messages can be sent to a mediator service. You can specify multiple services.

  • Type
    		•  - Defaults to DIDCommMessaging
  • URI
    		•  - Service endpoint address E.g. (https://127.0.0.1:7037/)
  • Accept
    		•  - Array of accepted message types for this service. Defaults to didcomm/v2
  • Routing Keys
    		•  - Array of DID public-keys that can be used for this defined service. Format must be did:method:identifier#key-id

    NOTE: The order of these services reflects the service identifier names used!
    NOTE: All attributes are required in describing the service!
    NOTE: Separate multiple items in Arrays with ';'




    Examples

    Alice wants to send a DIDComm message to Bob. Bob utilizes a DIDComm mediator to handle his incoming messages, this is described in Bob's DID Document via a defined service.

    Alice

    Alice represents herself with a Decentralized Identifier (DID) that contains the following:

    Example Alice DID 

    did:peer:2.Vz6MknrybrXop8wjecgH5gNZ4bajiztB1EuJ1aPJW1PsLaFcP.EzDnaeYzK9dTHipxp7QxvUADomBdLsSSvPsHBMc93g4BvSviHZ.SeyJ0IjoiZG0iLCJzIjp7InVyaSI6Imh0dHBzOi8vbG9jYWxob3N0OjcwMzcvIiwiYWNjZXB0IjpbImRpZGNvbW0vdjIiXSwicm91dGluZ19rZXlzIjpbXX19

    Bob

    Bob represents himself with a Decentralized Identifier (DID) that contains the following:

    Example Bob DID 

    did:peer:2.Vz6MkfRViUo3fADYPnpQeyJLCgtGsMfwqSUcEq7Jx6VrbA2Yg.EzDnaezTcKcJKooedjzf1tzFZs1eqVJwipRWDjDHJ7svXDpm6C.SeyJ0IjoiZG0iLCJzIjp7InVyaSI6Imh0dHBzOi8vbG9jYWxob3N0OjcwMzcvIiwiYWNjZXB0IjpbImRpZGNvbW0vdjIiLCJkaWRjb21tL2FpcDI7ZW52PXJmYzU4NyJdLCJyb3V0aW5nX2tleXMiOlsiZGlkOnBlZXI6Mi5WejZNa3Y1cGNtRXN6a3A0dExmQXZIZk14TUU3R1R3VnNwdUVURG9uOUMyTFh5UzQ5LkV6RG5hZXBjdmNRaWZFdUdrdGpGYXpaMUZNVHpFTGY2aFdXY1dvRmFRZFRKclI4OUx6LlNleUowSWpvaVpHMGlMQ0p6SWpwN0luVnlhU0k2SW1oMGRIQnpPaTh2Ykc5allXeG9iM04wT2pjd016Y3ZJaXdpWVdOalpYQjBJanBiSW1ScFpHTnZiVzB2ZGpJaVhTd2ljbTkxZEdsdVoxOXJaWGx6SWpwYlhYMTkja2V5LTIiXX19

    Mediator

    Affinidi offers a mediator node that can be used to route messages between two parties. Bob uses this mediator to receive messages.
    This mediator is referenced in Bob's DID Document via a defined service for DIDComm messaging. The Mediator's DID contains:

    Example Mediator DID 

    did:peer:2.Vz6Mkv5pcmEszkp4tLfAvHfMxME7GTwVspuETDon9C2LXyS49.EzDnaepcvcQifEuGktjFazZ1FMTzELf6hWWcWoFaQdTJrR89Lz.SeyJ0IjoiZG0iLCJzIjp7InVyaSI6Imh0dHBzOi8vbG9jYWxob3N0OjcwMzcvIiwiYWNjZXB0IjpbImRpZGNvbW0vdjIiXSwicm91dGluZ19rZXlzIjpbXX19