You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The routingKeys array was not needed as it was empty.
I reviewed the instructions in the did:peer spec and found them to be clear. What suggestions do you have for updates to either that spec or the OOB RFC to clarify?
Thanks for answering @TelegramSam. What’s still unclear to me is how to go from key to keyAgreement. If you’re using the did:key from the example above it includes both a ed25519 and x25519 key. Should we add the ed25519 key to the keyAgreement array (can’t use ed25519 for keyAgreement, only x25519)?
There is the following statement in the OOB spec:
I'm not sure what is supposed to be the
key
? Is it a recipient key? What if therecipientKeys
array contains more keys?Also, does it mean that we should take just
serviceEndpoint
from the service block? Let's say this is the service block from OOB invitation:Then CORRECT inputs into Peer DID encoding numalgo2 will be the following:
did:key:z6MkpTHR8VNsBxYAAWHut2Geadd9jSwuBV8xRoAnwWsdvktH
The service MUST NOT contain other attributes, right? This is an example of INCORRECT service, because it does not contain only
serviceEndpoint
:The text was updated successfully, but these errors were encountered: