Skip to content
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

Add support for ethereumAddress public key type in @context #55

Open
awoie opened this issue Sep 27, 2019 · 3 comments · May be fixed by #56
Assignees

Comments

@awoie
Copy link
Contributor

@awoie awoie commented Sep 27, 2019

The final community specification allows for ethereumAddress public key types. We have to add the respective key type to the context to be recognized by 3rd party applications, e.g., uniresolver.io.

After following the discussion in w3c-ccg/did-spec#270, it seems like we should at least support all public key types that were mentioned in the W3C CCG DID spec.

@selfissued

This comment has been minimized.

Copy link

@selfissued selfissued commented Oct 8, 2019

We should be removing public key formats from the spec - not adding them. We should get down to one key format to increase interoperability of implementations - preferably JWK.

@awoie

This comment has been minimized.

Copy link
Contributor Author

@awoie awoie commented Nov 4, 2019

@selfissued In general, I'm also in favor of having fewer representations of public keys. Nevertheless, some people, e.g., uPort, are using ethereumAddress: 0xabc... to express the "public key" which in this case is rather a parameter for the verification/ authentication. Technically, it is not a public key, just the last 20 bytes of the keccak of a public key, i.e., the Ethereum Address. This is needed because in some cases, e.g., smart contracts, we are not able to propagate the real public key in the DID Document and only have access to the ethereumAddress. Because secp256k1 keys are used we are still able to authenticate a message based on the message text, the message signature and the hash of the public key.

@selfissued Do you think it is likely that we can register a JWK representation for ethereumAddress?

@selfissued

This comment has been minimized.

Copy link

@selfissued selfissued commented Nov 5, 2019

This sounds like it's a cryptographically derived Key ID - not the key itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.