Skip to content
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

Implement BIP 118 validation (SIGHASH_ANYPREVOUT) #67

Merged
merged 9 commits into from
Oct 9, 2024

Conversation

ajtowns
Copy link

@ajtowns ajtowns commented Sep 2, 2024

Forward port from #56

@ajtowns ajtowns added the bip118 label Sep 2, 2024
@ajtowns ajtowns added this to the 28.x milestone Sep 2, 2024
@ajtowns ajtowns force-pushed the 202409-inq28-apo branch 2 times, most recently from 587e8d0 to 82a4cdd Compare September 2, 2024 03:37
@ajtowns ajtowns deleted the branch bitcoin-inquisition:28.x October 3, 2024 14:07
@ajtowns ajtowns closed this Oct 3, 2024
@ajtowns ajtowns reopened this Oct 7, 2024
ajtowns and others added 9 commits October 9, 2024 15:33
Introduce `KeyVersion` in preparation for defining new behaviours via
BIP 342's "unknown public key type" upgrade mechanism.
… was conserved

This fuzz targets copied the SignatureHashSchnorr function for Bitcoin
Core 23.0 and checks the output of the APO-ready SignatureHashSchnorr
from this branch against it.

This is to make sure the behaviour of the function was not changed for
non ANYPREVOUT keys, which would make some previously valid signatures
invalid and, even worse, some previously invalid signatures valid.
@ajtowns ajtowns marked this pull request as ready for review October 9, 2024 05:44
@ajtowns ajtowns merged commit aa0c738 into bitcoin-inquisition:28.x Oct 9, 2024
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants