From: Daniela Brozzoni Date: Mon, 13 Nov 2023 09:08:48 +0000 (+0100) Subject: Merge bitcoindevkit/bdk#1200: fix(bdk): Check if we're using the correct internal... X-Git-Tag: v1.0.0-alpha.3~22 X-Git-Url: http://internal-gitweb-vhost/script/%22https:/struct.EncoderStringWriter.html?a=commitdiff_plain;h=3fdab87ee7c02439b18a9e114ff588b282525402;p=bdk Merge bitcoindevkit/bdk#1200: fix(bdk): Check if we're using the correct internal key before signing e553231eae45dc6d263a1fce2a3a9c46f6af2510 fix(bdk): Check if we're using the correct... ...internal key before signing (Daniela Brozzoni) Pull request description: ### Description Fixes #1142 We would previously sign with whatever x_only_pubkey we had in hand, without first checking if it was the right key or not. This effectively meant that adding multiple taproot PrivateKey signers would produce unbroadcastable transactions. ### Changelog notice - Fix a bug related to taproot signing with internal keys. We would previously sign with the first private key we had, without checking if it was the correct internal key or not. ### Checklists #### All Submissions: * [x] I've signed all my commits * [x] I followed the [contribution guidelines](https://github.com/bitcoindevkit/bdk/blob/master/CONTRIBUTING.md) * [x] I ran `cargo fmt` and `cargo clippy` before committing #### Bugfixes: * [ ] This pull request breaks the existing API * [x] I've added tests to reproduce the issue which are now passing * [x] I'm linking the issue being fixed by this PR ACKs for top commit: evanlinjin: ACK e553231eae45dc6d263a1fce2a3a9c46f6af2510 Tree-SHA512: c4abbcd27935b8ce80a70b6e0843507866e3d075939f0b01504c090929ed96b4b9c6fee599f701e69960a6c86175682cc6d7f8cc4c3fb1d08a74b7563f8ca145 --- 3fdab87ee7c02439b18a9e114ff588b282525402