-
Notifications
You must be signed in to change notification settings - Fork 50
Bump bitcoin dependency requirement to v0.32.6 to reflect used API
#266
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
Bump bitcoin dependency requirement to v0.32.6 to reflect used API
#266
Conversation
thunderbiscuit
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.
ACK c9c8806.
oleonardolima
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.
ACK c9c8806
luisschwab
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.
ACK c9c8806
Starting with commit `f6fd9853e`, `bdk_wallet` makes use of
`bitcoin::key::TweakedKeyPair::to_keypair` which was introduced with
v0.32.6. Here, we adjust the minimum API requirement in `Cargo.toml`, as
BDK 2.0.0 builds could otherwise fail with:
```
error[E0599]: no method named `to_keypair` found for struct `TweakedKeypair` in the current scope
--> /home/tnull/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/bdk_wallet-2.0.0/src/wallet/signer.rs:580:14
|
578 | None => keypair
| _________________-
579 | | .tap_tweak(secp, psbt_input.tap_merkle_root)
580 | | .to_keypair(),
| | -^^^^^^^^^^ method not found in `TweakedKeypair`
| |_____________|
|
For more information about this error, try `rustc --explain E0599`.
```
c9c8806 to
af792ea
Compare
|
reACK af792ea |
Description
Starting with commit
f6fd9853e,bdk_walletmakes use ofbitcoin::key::TweakedKeyPair::to_keypairwhich was introduced with v0.32.6. Here, we adjust the minimum API requirement inCargo.toml, as BDK 2.0.0 builds could otherwise fail with: