Skip to content

Commit

Permalink
Update draft-bradleylundberg-cfrg-arkg.md
Browse files Browse the repository at this point in the history
  • Loading branch information
AltmannPeter authored Apr 11, 2024
1 parent 1e6df6b commit 8b0c85c
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions draft-bradleylundberg-cfrg-arkg.md
Original file line number Diff line number Diff line change
Expand Up @@ -330,9 +330,8 @@ A concrete ARKG instantiation MUST specify the instantiation
of each of the above functions and values.

The output keys of the `BL` scheme are also the output keys of the ARKG instance as a whole.
For example, the output key for EdDSA using Ed25519 or Ed448 is generated by invoking the required routines in RFC 8032 [section 5.1](https://www.rfc-editor.org/rfc/rfc8032#section-5.1) and [section 5.2](https://www.rfc-editor.org/rfc/rfc8032#section-5.2) respectively. Relatedly, for ECDSA over NIST curves the output key is generated by invoking the key generation routine specified in ANSI X9.62; and ECDH over NIST curves uses the key generation routine specified in [NIST SP 800-56A](https://csrc.nist.gov/pubs/sp/800/56/a/r3/final).
These output keys enable use cases where any procedure that involves the private key and the blinding key generates an output that is independent of one involving only the private key.

For example, if `BL-Blind-Public-Key` and `BL-Blind-Secret-Key` output keys for ECDSA over NIST P-256,
then the ARKG instance will also output keys for ECDSA over NIST P-256.

Instantiations MUST satisfy the following compatibility criteria:

Expand Down

0 comments on commit 8b0c85c

Please sign in to comment.