-
Notifications
You must be signed in to change notification settings - Fork 324
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
Move hardware signer into its own crate #872
Comments
Just to clarify, it would be moved to the same bdk workspace but in a different crate under |
danielabrozzoni
added a commit
to danielabrozzoni/bdk
that referenced
this issue
Oct 9, 2023
danielabrozzoni
added a commit
to danielabrozzoni/bdk
that referenced
this issue
Oct 9, 2023
danielabrozzoni
added a commit
to danielabrozzoni/bdk
that referenced
this issue
Oct 9, 2023
danielabrozzoni
added a commit
to danielabrozzoni/bdk
that referenced
this issue
Oct 9, 2023
danielabrozzoni
added a commit
to danielabrozzoni/bdk
that referenced
this issue
Nov 9, 2023
danielabrozzoni
added a commit
to danielabrozzoni/bdk
that referenced
this issue
Nov 24, 2023
danielabrozzoni
added a commit
to danielabrozzoni/bdk
that referenced
this issue
Dec 13, 2023
notmandatory
added a commit
that referenced
this issue
Jan 8, 2024
105d70e ref(hwi): Move hwi out of bdk (Daniela Brozzoni) Pull request description: Fixes #872 ### Description This commit moves the `hardwaresigner` outside of bdk and inside `bdk_hwi` ### Notes to the reviewers There are currently two issues with the code: - `TransactionSigner` dictates that `sign_transaction` must return a `SignerError` - but being `SignerError` defined inside of bdk, we can't modify it to include an hwi specific error! I don't know how we could fix this (other than getting rid of the trait altogether :)); for now I just added a `SignerError::Generic` variant, lmk if you have better ideas! - The hwi tests used the bdk utils to get a funded wallet for testing, which aren't available in `bdk_hwi`, which made me realize - maybe we should expose them so that we can use them across our crates, and also our users can use them to test their code? For now, I just left the test commented. ### Changelog notice - The old `hardwaresigner` module has been moved out of `bdk` and inside `bdk_hwi`. ### 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 #### New Features: ~~* [ ] I've added tests for the new feature~~ * [x] I've added docs for the new feature ACKs for top commit: notmandatory: reACK 105d70e Tree-SHA512: 9ae3cd035cc27bd7b2831e89c104f40771c6f165cb3bfe1a9052f820050fca7c19f4dd68f171c630a71a7d18ccdee5f94adbc497c6475bd257c2d01cc08109a1
casey-bowman
pushed a commit
to casey-bowman/bdk
that referenced
this issue
Jan 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It has its own very bespoke python runtime dependency and needs hardware to test (if I understand correctly). It doesn't need to be in the main
bdk
crate and I think it's desirable not to have non cargo dependencies for tests in the mainbdk
crate.The text was updated successfully, but these errors were encountered: