Did-core: Restrict the number of key representation members
publicKeyJwk, publicKeyBase58.... you should only be allowed to use 1 of these in a did core vm.
Someday it will be obvious which of these is the most common for all key types.
OR13
All 8 comments
cc @msporny as discussed on the call.
OR13
on 23 Jul 2020
Yes, agreed... the reasoning being that we don't want people to try to express the same key in two different formats and accidentally put in two different keys. By restricting to one used vs. the other, we eliminate a lot of error checking code.
msporny
on 24 Jul 2020
I believe a normative statement here, would address this issue:
https://w3c.github.io/did-core/#verification-methods
we should generalize this to account for non public key verification material.
OR13
on 28 Jul 2020
We need to add guidance that you cannot include multiple key representations in the same verification method. needs pr.
OR13
on 26 Aug 2020
Needs a PR
OR13
on 23 Sep 2020
Looks like this is done and can be closed?
rhiaro
on 27 Oct 2020
agreed, this should be closed.
OR13
on 28 Oct 2020
Issue submitter agrees that the issue has been addressed. Closing.
msporny
on 3 Nov 2020
Related issues
mitfik
路
7Comments
dmitrizagidulin
路
6Comments
brentzundel
路
7Comments
awoie
路
8Comments
brentzundel
路
6Comments
Most helpful comment
Yes, agreed... the reasoning being that we don't want people to try to express the same key in two different formats and accidentally put in two different keys. By restricting to one used vs. the other, we eliminate a lot of error checking code.