-
Notifications
You must be signed in to change notification settings - Fork 96
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
Transaction signing regression #5340
Comments
@Lemii we removed the overall ability to have second passphrase as it was a legacy feature.. with new account management you can add as many accounts in account management as it involves encryption etc..
This should help? |
I'm familiar with the workflow of signing a multisig transaction with multiple accounts using the download function, however it is much less user-friendly than being able to sign it immediately. Even though it is considered a 'legacy feature' now, please bare in mind that there are a great number of users coming from the old version that are using a multisig account. It might be worth reconsidering reverting the removal of this feature. |
Continuous flow for signing a multi-signature transactionWhen this state is true:
And a user tries to sign a transaction from MultiSigAccount1 there should be a continuous flow to signing with MultiSigAccount2. Refer to this design for the flow. |
Expected behavior
Being given the ability to immediately sign a transaction with a second multisig passphrase, just like in the current version (v2.3.0).
Actual behavior
A window is shown to download the transaction, without an option to sign it with another passphrase instead.
Steps to reproduce
Which version(s) does this affect? (Environment, OS, etc...)
Version 3.0.0-rc.1
The text was updated successfully, but these errors were encountered: