-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Padding point gen using Try-And-Increment #32
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
82c80dc
Generate padding point using ChaCha20Rng directly
davxy 78b30bb
Blake2b
davxy 105b1e7
Generate padding using TAI
davxy cfa6076
Blanks
davxy 535630a
Keep h2c internal
davxy 644dc5d
Nit
davxy 9e6a372
Nit Nit
davxy a458018
Change padding seed string
davxy File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@burdges do we care if it is in the subgroup? Just curious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
he asked the same question here: #31 (review)
But I guess yes? As the SEED is not in the prime order subgroup, if you add a padding point not in the prime order subgroup you may end-up with the point at infinity right? Which is not managed in the constraints (and primarily that is why the SEED is chosen to be out of the prime subgroup).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it. We cannot compute
x+x
in the SNARK, onlyx+y
withx != y
. As our snark never checks thatx != y
, we need all our additions to bex != y
implicitly.We have two padding points, the start point
hs
and the empty pointhe
, maybe equal. We compute(..((hs + x[0]) + x[1]) + .. + x[n]) - hs
where thex[i]
are either a public key if in the bitfield, or zero=infinity if not in the bitfield, orhe
no public key exists there.We need
-2 hs
to not be a combination ofx[i]
, butn << group_order
, so eitherhs
should be outside the prime order subgroup, or else we should've proofs of possession for the public keys.We should presumably just do proofs of possession, because that'll work for prime order curves by bn254, but if skipped the proofs of possession then
he != hs
matters, buths = he + coset_element
works.