Skip to content

Conversation

Zshan0
Copy link
Collaborator

@Zshan0 Zshan0 commented Jun 13, 2022

Since the Bitcoin Core ignores the sighash type specified inside the PSBT inputs, sign_psbt relied on the default value of sighash_type which aligned with our requirements. bitcoin/bitcoin#22514 changed the default value from SIGHASH_ALL to SIGHASH_DEFAULT. Making sighash_type explicit fixes the minor breaking change caused by the update in the bitcoin wallet. Note that since sighashtype parameter comes after the sign parameter, the value of sign has been set to the default value, true.

Along with the fix, bitcoind version used in CI has been bumped from 22.0 to 23.0.

This issue closes #414.

Zshan0 added 2 commits June 17, 2022 18:02
The change of default `sighash` type in `bitcoind` was a minor breaking
change.
@Zshan0
Copy link
Collaborator Author

Zshan0 commented Jun 17, 2022

Keeping the sighash_type as SigHashType::All was throwing an error:

Error while updating tip: \'Bitcoind server error: RPC error response: RpcError { code: -1, message: "SIGHASH_ALL is not a valid sighash parameter.", data: None }\''

After looking at cljdocs I changed the value to "ALL" and the tests passed locally. I was not able to find the correct Macro for it, please let me know if there are any more changes required.

Copy link
Member

@darosior darosior left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK cd21ab8

Let's see what's up with the MacOS CI..

@darosior darosior merged commit e72146e into revault:master Jun 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Minor API break by Bitcoin Core wallet
2 participants