feat(signer): merge internal and external signer containers#251
Closed
ndungudedan wants to merge 1 commit intobitcoindevkit:masterfrom
Closed
feat(signer): merge internal and external signer containers#251ndungudedan wants to merge 1 commit intobitcoindevkit:masterfrom
ndungudedan wants to merge 1 commit intobitcoindevkit:masterfrom
Conversation
Currently BDK stores signers in two separate SignersContainer instances - one for internal keychain and one for external. This separation is unnecessary since: 1. Most signers can sign for both keychains 2. Both containers are always called during signing 3. The separation adds complexity without benefits This change: - Adds an `extend` method to SignersContainer to support merging containers - Keeps a single signer container in Wallet Closes bitcoindevkit#186
Contributor
Collaborator
|
Thanks for your contribution. I agree with @oleonardolima, assuming we go ahead with #70, then this issue probably won't be as relevant. |
Author
|
Thanks! Closing the PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Currently BDK stores signers in two separate SignersContainer instances - one for internal keychain and one for external. This separation is unnecessary since:
This change:
extendmethod to SignersContainer to support merging containersCloses #186
Notes to the reviewers
Incompatible change descriptor, from the export module. On further investigation, I see that the export node returns the change descriptor as a public key while the derived change descriptor is a private key. I am not sure why this is case and a second review would be great:Checklists
All Submissions:
cargo +nightly fmtandcargo clippybefore committingNew Features:
Bugfixes: