-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Newcomer: How to specify multiple keys (RSA, SECP256K1) in a DID document #823
Comments
@kaimeinke No need to repeat the keys.. I think this is what you want:
|
Regarding the service endpoints, |
You can look at the examples from did;key here: https://did.key.transmute.industries/ and find replace the |
Dear @peacekeeper and @OR13 thank you very much, this was super helpful. Will check the DID:KEY example right away. I will remove the multiple # characters as they are not allowed. Then I would replace these IDs with URIs such as
|
I think we can close this one for now and I would go from here with the following DID Document. Thanks for your quick and great help, I'll come back when we did the next steps of our integration.
|
Dear did-core community,
as a newcomer to the DID specs I would like to learn how I can specify multiple keypairs in a DID document. In this example it should be RSA (incl. the certificate to validate the chain of trust) and SECP256K1 (for use in transactions in EVM-compatible DLT context).
If this is not the right place to ask, please excuse me for bringing it here. I would gladly take any recommendation where to turn with my question. Thanks a lot for your patience.
From the specs I anticipate I need to complete every of the following properties twice for each keypair:
For the RSA keys I want to expose a serviceEndpoint to retrieve the X509 certificate to check it against Trust Anchors in the eIDAS context.
Is this valid with one id and controller?
This is an example of how I envision it right now and I would be happy to take any advice as I could not find a fitting straightforward example, but a similar example like EXAMPLE 31: DID Document with many different key types.
Thanks a lot for your help.
Kai
The text was updated successfully, but these errors were encountered: