-
Notifications
You must be signed in to change notification settings - Fork 649
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
Specify Signing Keys in CLI Wallet #2048
Comments
Actually we have another option: extend/fix the |
It's best if we can fix this in 4.0.0. If we can't, we should fix it asap. |
Merged quick fix in #2049. |
Created #2202 for fixing APIs. Closing this issue. |
User Story
Users of BSIP 40, which is available in BitShares 4.0.0, requires client software that can add a signature to a transaction.
The CLI Wallet can sign transactions with the keys in the wallet but only with keys that are directly required by operations in a transaction. For example, the transfer of funds from Alice's account requires Alice's signature.
BSIP 40 allows allows transactions to be signed by additional accounts, keys, and authorities that have been authorized by the required party. For example, Alice could authorize Bob to transfer funds from her account. Therefore, Bob should be able to sign such a transaction by signing with his account's active key.
The CLI Wallet does not currently allow a user to insist on signing a transaction that does not obviously require it. There should be a way for CLI Wallet users to insist on signing a transaction with any key in their wallet.
Impacts
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.
The text was updated successfully, but these errors were encountered: