sighash_type
made explicit along with a bump in bitcoind
version for CI testing
#415
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.
Since the Bitcoin Core ignores the sighash type specified inside the PSBT inputs,
sign_psbt
relied on the default value ofsighash_type
which aligned with our requirements. bitcoin/bitcoin#22514 changed the default value fromSIGHASH_ALL
toSIGHASH_DEFAULT
. Makingsighash_type
explicit fixes the minor breaking change caused by the update in the bitcoin wallet. Note that sincesighashtype
parameter comes after thesign
parameter, the value ofsign
has been set to the default value,true
.Along with the fix,
bitcoind
version used in CI has been bumped from22.0
to23.0
.This issue closes #414.