You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 23, 2022. It is now read-only.
Should this also be defined? The x attribute would just be the G1 and G2 public keys, concatenated. This key type is already supported by multicodec, for instance.
The text was updated successfully, but these errors were encountered:
Hmm, not sure about this one. Where do we use it? I'm open to it if there's good reason, but would like to keep things as closely aligned to pairing friendly curves if possible.
It's simply a representation for when you don't want to be limited to just the G1 or G2 public key. You could put both into a keyset, but then it's less obvious that they're related. Here's the multicodec entry: https://github.com/multiformats/multicodec/blob/master/table.csv#L86
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Should this also be defined? The
x
attribute would just be the G1 and G2 public keys, concatenated. This key type is already supported by multicodec, for instance.The text was updated successfully, but these errors were encountered: