-
Notifications
You must be signed in to change notification settings - Fork 37.7k
Bugfix: chainparams: Add missing (always enabled) Taproot deployment for Signet #20157
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
How is this bug observable? |
I didn't try, but in theory the deployment params are going to be uninitialized and could be anything? |
taproot is already activated on global(?) signet? how to activate manually on my own custom signet? |
cb2bf18
to
b645e99
Compare
b645e99
to
2d5793c
Compare
utACK 2d5793c |
@kallewoof @ajtowns are you ok with having taproot always active on signet? @luke-jr Can you update the PR title as it's no longer disabled. |
Yep! |
review ACK 2d5793c |
Master:
|
Checked that this pull fixes the uninitialized read and also prints:
|
…) Taproot deployment for Signet 2d5793c Bugfix: chainparams: Add missing (disabled) Taproot deployment for Signet (Luke Dashjr) Pull request description: Is there a way we can trigger compiler warnings if a deployment is undefined? ACKs for top commit: decryp2kanon: utACK 2d5793c MarcoFalke: review ACK 2d5793c Tree-SHA512: 135cefae0f8dc552b0f682c2b87cabca7a4716290a36410a55968850e803a5049234e3cc597c8ef8d7917ae5d5ea3fb851e160df171b6793114c6bc01c5ea3e7
Is there a way we can trigger compiler warnings if a deployment is undefined?