Open
Conversation
proving time 115s -> 50s on M1 Max
Already patched in workspace root
This probably is not safe, since prover can choose beta*G to fit any taproot on-chain and then show inlcusion proof for it.
So we can use the sha256 precompile
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
1 participant
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.
This is a rewrite of the tool where we remove signature verification. Instead we focus on proving inclusion in the UTXO set of a key on the form
P_out = P + beta *G, wherebetais a blinding factor.The ownership can still be verified by signing for
P, without revealingP_out.This achieves significant speedups, since we are no longer doing signature verification in the ZK environment.