Orie Steele

I'm not opposed to `did:elem` or `did:ethr` supporting CAIP-10 aliases for DIDs... IF the actual method code is being used.... however... there is not way to actually FORCE that... so...

Consider also... there will be private networks that use element / ethr dids....

Cross linking: https://github.com/w3c/did-spec-registries/issues/102

However, this could be very useful for P2P UA connections for PWAs. Imagine you have 2 wallet apps, which are managing keys for DIDs. The 2 apps configure a serviceEndpoint...

@filips123 thanks for opening this! As you noted, we'll need to keep an eye on truffle and upgrade once they add support.

Bumping this issue to a bug, we really would love to use node 12... especially because it is a requirement for https://github.com/panva/jose

sadness... thanks for pinging those issues.

Example of a method spec: https://digitalbazaar.github.io/did-method-key/#format (key format and operations should be defined in readme)

We should add this transform to the library, since its likely to be needed until a better solution is available.

We should leave this open until fragids are valid according to the did core spec, or we don't use them.