Additional Key Generation

Normally, the Universal Registrar only uses cryptographic keys that are needed by the applicable DID method itself, in other words, keys that are needed for creating, updating, and deactivating DIDs. Depending on the DID method, these keys may or may not appear in the DID document.

For example, in the case of did:indy, the keys used to control the DID also appear in the DID document. In the case of did:ion on the other hand, the keys used to control the DID do not appear in the DID document. In the case of did:web, no keys at all are needed to control the DID.

Irrespective of these DID method-specific differences with regard to keys, it may sometimes be useful to add additional keys to a DID document. This can be done by adding a requestVerificationMethod property to the options input field. This property contains an array of verification method templates.

Example:

curl -H "Authorization: Bearer b082c420-df67-4b06-899c-b7c51d75fba0" \
     -X POST "https://api.godiddy.com/1.0.0/universal-registrar/create?method=web" \
     -H "Content-Type: application/json" \
     -d '{
       "didDocument": { },
       "options": {
         "requestVerificationMethod": [{
           "id": "#signingKey",
           "type": "Ed25519VerificationKey2018",
           "purpose": ["authentication", "assertionMethod"]
         }]
       },
       "secret":  { }
     }'