Add BLS 12-381 g1 and g2 public key concatenated identifier #185
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Looking forward to using this representation. |
|
@rvagg @vmx can we get a review of this? let us know if we need to make any adjustments... the reason we need an encoding for both keys concatenated is to support w3c/vc-di-bbs#37 |
|
@OR13 could you please put it after |
tplooker
force-pushed
the
tl/add-blsG1andG2
branch
from
d288ac7 to
4a698cb
Compare
|
@vmx done |
rvagg
approved these changes
Sep 17, 2020
It is in the 2-byte range. Everything > |
vmx
approved these changes
Sep 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For certain signatures such as https://github.com/mattrglobal/bbs-signatures it is useful to have a single private key have a corresponding public key in both the G1 and G2 fields.