-
Notifications
You must be signed in to change notification settings - Fork 37.7k
RPC: Return external_signer in getwalletinfo #24307
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
RPC: Return external_signer in getwalletinfo #24307
Conversation
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.
utACK b75f4c8
utACK b75f4c8 |
#21928 contains this change as well, though it's valid on its own. |
@prayank23 my PR is almost a year old. But if this gets merged first I'll rebase it of course. |
@Sjors Didn't know about your PR. Was playing around with external signer stuff and at one moment wanted to check is that flag really set for a specific wallet and noticed I can't do that. Anyway, this one is simple change, should be easy to review, test and merge sooner. |
TBH I can't review all the things in #21928 This looks ready for review and merge :) |
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
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.
utACK b75f4c8
ACK b75f4c8 |
b75f4c8 RPC: Return external_signer in getwalletinfo (Kristaps Kaupe) Pull request description: Add `external_signer` to the result object of `getwalletinfo` RPC which indicates whether `WALLET_FLAG_EXTERNAL_SIGNER` flag is set for the wallet. ACKs for top commit: S3RK: utACK b75f4c8 achow101: ACK b75f4c8 prayank23: utACK bitcoin@b75f4c8 brunoerg: utACK b75f4c8 Tree-SHA512: 066ccb97541fd4dc3d9728834645db714a3c8c93ccf29142811af4d79cfb9440a97bbb6c845434a909bc6e1775ef3737fcbb368c1f0582bc63973f6deb17a45f
Seems like this should probably be a string indicating the external signer program... but I guess changing it later is okay? |
Fine by me :-) I'll rebase. @luke-jr that would just echo |
For now, yes - but eventually it'd be ideal to have wallets with different external signers. |
I agree with @luke-jr, different external signers for different wallets in the future makes sense. |
To clarify: different external signer programs, e.g. alternatives to HWI. You can already have multiple wallets each using a different (type of) physical device, all via HWI. |
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 b75f4c8
Add
external_signer
to the result object ofgetwalletinfo
RPC which indicates whetherWALLET_FLAG_EXTERNAL_SIGNER
flag is set for the wallet.