-
Notifications
You must be signed in to change notification settings - Fork 1.2k
backport: merge bitcoin#22029, #27538, #21100, #27542, #24005, partial bitcoin#19953, #23394, #20292, #20161, #20842, #26222 (secp256k1 tests) #5873
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
Conversation
UdjinM6
left a comment
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.
utACK
PastaPastaPasta
left a comment
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.
utACK for merging via merge commit
includes: - ca83ffc (only changes to test/ functional/test_framework/key.py)
includes: - 50eb0c2 (only changes to test/ functional/test_framework/key.py)
includes: - 1d22300
These changes were introduced in bitcoin#15514 (Update Transifex links), which ordinarily do not apply to Dash as it uses its own Transifex account but not mentioned in the name are updates to Doxygen URLs.
The changes are a portion of bitcoin#17873, the rest of which is merged into `developer-notes.md`, leaving this change out for some reason.
…p classes to test framework notes: - excludes changes to test/functional/feature_taproot.py
cfc2c4e to
3710439
Compare
knst
left a comment
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.
post-utACK
Additional Information
As mentioned in a comment on dash#5575, partials will remain present as a lot of the associated changes needed for BIP324 coincide with work on Taproot.
This does come with the problematic side effect of complicating Taproot backporting efforts should it be undertaken in the future as the codebase would contain bits and pieces of code that assume changes in Taproot logic, for example, using APIs that have already been changed, requiring OOO modifications to be usable.
bitcoin#23394 is listed as unmerged despite the changes making it to the codebase vide merge commit bitcoin@5ccab71, see comment.
bitcoin#27542 is a followup to bitcoin#23716 (which was backported via dash#4843)
Breaking Changes
None, changes are limited to Python-based tests, one fuzzing test and code comments.
Checklist: