Troy Ronda

generating DID docs with verificationMethod rather than publicKey

1

[DID-Core v1](https://w3c.github.io/did-core/#verification-methods) now uses `verificationMethod` rather than the `publicKey` property. When generating DID documents, the `verificationMethod` property should be used. The [did:peer spec](https://identity.foundation/peer-did-method-spec/#verificationmethod) has now also been updated to use...

TinyGo and WASM

1

* Future: investigate usage of [TinyGo](https://tinygo.org) to create smaller WASM outputs (see #661). * It is likely that TinyGo goes not yet have enough language coverage to be used. *...

Cross-link: https://github.com/decentralized-identity/didcomm-messaging/issues/191

controller string should be populated to be more consistent with other DID implementations

3

Re: https://github.com/decentralized-identity/sidetree/pull/1009#discussion_r561435869 https://github.com/decentralized-identity/sidetree/pull/1006#discussion_r561056101 @OR13 wrote: > I strongly recommend against returning the empty string for the controller property.... if makes sidetree look different than every other did method, and its...

Common protocol parameter format

3

Are there any generic Sidetree protocol parameters that should have a common format? Here are our current trustbloc parameters: ``` { "genesisTime": 0, "multihashAlgorithm": 18, "maxOperationCount": 10, "maxOperationSize": 200000, "compressionAlgorithm":...

It would be helpful if the DotNet framework used https PIURIs (by default). From: https://github.com/hyperledger/aries-framework-go/pull/2655#discussion_r598255549

[DID-Core v1](https://w3c.github.io/did-core/#verification-methods) now uses `verificationMethod` rather than the `publicKey` property. The [did:peer spec](https://identity.foundation/peer-did-method-spec/#verificationmethod) has now also been updated to use `verificationMethod`.

The service type should be `did-communication` rather than `IndyAgent` in DID Exchange.