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.

Sign up for GitHub

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

Jump to bottom

Details-on-ARKG-instance-output #16

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Details-on-ARKG-instance-output #16

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bcbc4f7
Details-on-ARKG-instance-output
AltmannPeter Apr 9, 2024
1e6df6b
Update draft-bradleylundberg-cfrg-arkg.md
AltmannPeter Apr 11, 2024
8b0c85c
Update draft-bradleylundberg-cfrg-arkg.md
AltmannPeter Apr 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions draft-bradleylundberg-cfrg-arkg.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -330,8 +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, if `BL-Blind-Public-Key` and `BL-Blind-Secret-Key` output ECDSA keys,
then the ARKG instance will also output ECDSA keys.
An ARKG derived blinded private public key pair enables use cases where any procedure that involves the private key and the blinding key generates an output that is independent from one involving only the private key. Each blinding key is also a private key for a given procedure over a particular curve.
For example, the blinding 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, and a blinding key for ECDH over X25519 assumes a suitably generated X25519 key pair. Relatedly, for ECDSA over NIST curves the blinding 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).

Instantiations MUST satisfy the following compatibility criteria:

Expand Down
Loading