publicKeyMultibase doesn't appear to be showing in the did document resolver
Closed this issue · 6 comments
Hmm did:web:aviary.pub
seems to be down right now, so I can't try it myself. Could you share the full DID document?
Normally, "publicKeyMultibase" should be supported by the UI, see here: https://github.com/decentralized-identity/universal-resolver-frontend/blob/main/src/components/result/VerificationMethod.jsx#L15
Yes, apologies that domain is my ngrok tunnel domain so I need my local setup booted. Here is the full document
{
"@context": [
"https://www.w3.org/ns/did/v1"
],
"controller": "did:web:aviary.pub",
"id": "did:web:aviary.pub",
"keyAgreement": [
"did:web:aviary.pub#1"
],
"service": [
{
"accept": [
"didcomm/v2"
],
"id": "#didcomm",
"serviceEndpoint": "https://aviary.pub/didcomm",
"type": "DIDCommMessaging"
}
],
"verificationMethod": [
{
"controller": "did:web:aviary.pub",
"id": "did:web:aviary.pub#0",
"publicKeyMultibase": "z8FRmkyRH9xAsLCk51yXN2Qy6uq4eN4iAesa3v3Hv889v",
"type": "Ed25519VerificationKey2020"
},
{
"controller": "did:web:aviary.pub",
"id": "did:web:aviary.pub#1",
"publicKeyMultibase": "z7bNjXnt3EXhpy7UdzZUANa2CsBFpzKGFXsgvkBd9iHGo",
"type": "X25519KeyAgreementKey2020"
}
]
}
Ok, I think I've determined this is a json-ld problem after looking at it on the playground. I guess I need a context for those suite types. Searching for them now..
hmm added "https://www.w3id.org/security/suites/x25519-2020/v1" as a context but that doesn't seem to resolve the issue
@brianorwhatever I think this has been fixed now in 1a17332.
The latest version is already deployed at https://dev.uniresolver.io/. Could you check, and if you agree, close the issue?
Looks great, thanks for the fix @peacekeeper !