-
Notifications
You must be signed in to change notification settings - Fork 216
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
Uncompressed Bulletproof Rangeproofs #108
Closed
apoelstra
wants to merge
15
commits into
BlockstreamResearch:master
from
apoelstra:2020-11--bulletproofs1-uncompressed
+2,494
−517
Closed
Changes from 1 commit
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
e2061cb
MOVE ONLY: move Pedersen commitment stuff to generator module from ra…
apoelstra a4ce304
Revert "Remove unused scalar_sqr"
apoelstra 290c479
generator: cleanups in Pedersen/generator code
apoelstra 2cc4261
bulletproofs: add new empty module
apoelstra b2cdcee
bulletproofs: add API functionality to generate a large set of genera…
apoelstra 31b998d
bulletproofs: implement step 0 of the uncompressed prover
apoelstra 3385353
bulletproofs: implement step 1 of the uncompressed prover
apoelstra 28c5f18
bulletproofs: implement step 2 of the uncompressed prover
apoelstra 2e651b9
bulletproofs: implement the iterative step of the uncompressed prover
apoelstra 264924c
bulletproofs: implement prove/verify API, still have the actual EC ch…
apoelstra 28d8c3c
bulletproofs: finish the uncompressed verifier
apoelstra ecea06c
bulletproofs: add benchmark
apoelstra e22225c
bulletproofs: add SECP256K1_WARN_UNUSED_RESULT to all the non-void AP…
apoelstra c1d6e95
bulletproofs: use tagged hash for committed data within proof
apoelstra 6463ffb
bulletproofs: expose a macro returning proof-size
HalosGhost 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
bulletproofs: implement the iterative step of the uncompressed prover
commit 2e651b9cd0982e90b2c267f2247e4c8a0da17a5a
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
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.
What's the motivation for treating
x
separately fromy
andz
, given that each call tolr_generate
seems to create a freshlrgen
struct anyway?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.
y
andz
are constants.x
is a variable. By treatingx
separately we retain the ability to make copies of the lrgen generator rather than re-initializing it. (Indeed, we do this in Step 3 on line 380.)