Feat/did key

[eike-hass]

Description of change

Please write a summary of your changes and why you made them.

Links to any relevant issues

Be sure to reference any related issues by adding fixes issue #.

Type of change

Add an x to the boxes that are relevant to your changes.

• [ ] Bug fix (a non-breaking change which fixes an issue)
• [ ] Enhancement (a non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Documentation Fix

How the change has been tested

Describe the tests that you ran to verify your changes. Make sure to provide instructions for the maintainer as well as any relevant configurations.

Change checklist

Add an x to the boxes that are relevant to your changes.

• [ ] I have followed the contribution guidelines for this project
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes

[UMR1352]

@eike-hass what do we want to do with this? The implementation only supports a portion of the did:key specification and has not been thoroughly documented nor tested

[eike-hass]

@eike-hass what do we want to do with this? The implementation only supports a portion of the did:key specification and has not been thoroughly documented nor tested

we need did:key support for Selv and might need to extend to did:jwk es well. I think we should be okay with only considering ed25519 support for now though and rethink for 2.0. Long story short: We should try to get this in an acceptable state and merge mid-term.