-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add offchain sequence management for multisig accounts #1448
Comments
This is a good feature. Thank you @freeelancer |
Thank you @anilcse. I see the changes and it has been a great improvement for us. With the current changes, multisig members have to wait for a transaction to go past threshold before they can move on to sign the next transaction. Just some further suggestions to improve the UX. As a multisig user, we wish to be able to sign all our multisig transactions at one go (in the happy scenario) instead of waiting in between. A suggestion I have to achieve this is to let the first signer of a multisig transactions determine its sequence number and for all future members to see the order of "to be signed" multisig transactions and to sign in the same order. I understand that this might be a complex feature to implement, but I believe it would greatly benefit users (being one myself and feeling the pain of only being able to sign one tx at a time). I'm open to any solution that can achieve this goal. Any improvement in this area would be greatly appreciated. |
I missed this message @freeelancer , thank you for flagging. |
Currently the sequence used for signing multisig is taken directly from the chain. This means that if there are multiple transactions to sign, they would all be signed with the same sequence and only one can be broadcasted. By having a local sequence management, all transactions can be signed and broadcasted together.
The text was updated successfully, but these errors were encountered: