Agree on signature encoding about lds-ecdsa-secp256k1-2019.js HOT 5 CLOSED

It would be ideal to pick a signature method that is compatible with the tooling built by jolocom and uport already.

@christianlundkvist @Exulansis

Whatever we decide, it needs to be clearly defined in the spec, in plain terms, and there needs to be at least a javascript test.

Ideally, there should be at least one implementation in a different language for cross validation of spec compliance.

from lds-ecdsa-secp256k1-2019.js.

@thehenrytsai this suite could potentially use the same signing method that sidetree uses. If you have any strong arguments for leveraging the same type of signature here, I'd love your input.

I believe this code is equivalent to the code used in sidetree core:

https://github.com/decentralized-identity/element/blob/master/packages/element-lib/src/func/signEncodedPayload.js

from lds-ecdsa-secp256k1-2019.js.

I consider this repo to be one of the best references for JSON-LD Signature Suite implementation in JS:

digitalbazaar/jsonld-signatures#52

We should be concerned about updating the JOSE registry.

from lds-ecdsa-secp256k1-2019.js.

Does anyone know how to get the JOSE algorithm registry updated, or who a champion might be for this task?

https://tools.ietf.org/id/draft-ietf-cose-webauthn-algorithms-00.html

This is required to have valid JWS which use secp256k1. Anything else might look correct, but won't be official.

from lds-ecdsa-secp256k1-2019.js.

ES256K (JWS) Unencoded Payload Option, same as EdDSA used in Ed25519Signature2018 ... https://tools.ietf.org/html/rfc7797#section-6

from lds-ecdsa-secp256k1-2019.js.