Bulletproofs - #9
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fully rewrote the bulletproofs implementation.
Had to shorten the proof size significantly to handle size constraints - it's not useful for much beyond a PoC.
BUT as far as I know this is the first ever implementation of bulletproofs over BLS12-381. Other curves like ed25519 or secp256k1 are much better fits, we just don't have the builtins we need for those curves in Plutus yet.
Once we have the MSM optimizations for BLS (next hard fork I think?) or scalar addition / multiplication for ed25519 or secp256k1 in Plutus we could revisit this and see about making something more functional.