Document generator creation procedure #71
Merged
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
This was referenced Feb 24, 2022
mikelodder7
reviewed
Feb 28, 2022
tplooker
commented
Mar 2, 2022
Closed
mikelodder7
approved these changes
Mar 3, 2022
tplooker
force-pushed
the
tl/create-generators
branch
from
89bb5c8
to
309e91f
Compare
Co-authored-by: Vasilis Kalos <kalosbasileios@gmail.com>
tplooker
force-pushed
the
tl/create-generators
branch
from
65c083f
to
ded91eb
Compare
BasileiosKal
approved these changes
Mar 10, 2022
|
Multiple approvals, open for two weeks, merging. |
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.
Initial stab at this attempting to document and resolve #38. In general I was keen to define a generic procedure that could take a seed scoped either globally, issuer or signature specific. Detail about the concrete seed we are using the BLS12-381 cipher suite is still missing.