-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Improve signing with multisig proxy #11433
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
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.
Looks great just resolve the comment I left and I can approve
|
Hi - Iβm still experiencing this issue when trying to send funds from a Pure account using a multisig. |
You mean pure proxy account? |
|
Yes, correct.
β¦On Fri, 28 Mar 2025 at 13:51, Arjun Porwal ***@***.***> wrote:
Hi - Iβm still experiencing this issue when trying to send funds from a
Pure account using a multisig.
You mean pure proxy account?
β
Reply to this email directly, view it on GitHub
<#11433 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AX2EJHCAXOB55K7NUH3HTH32WVHU7AVCNFSM6AAAAABZ7HMDCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRRGQZDOMJXGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
[image: ap211unitech]*ap211unitech* left a comment
(polkadot-js/apps#11433)
<#11433 (comment)>
Hi - Iβm still experiencing this issue when trying to send funds from a
Pure account using a multisig.
You mean pure proxy account?
β
Reply to this email directly, view it on GitHub
<#11433 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AX2EJHCAXOB55K7NUH3HTH32WVHU7AVCNFSM6AAAAABZ7HMDCWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONRRGQZDOMJXGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
*Dave Sedacca*
Parity Technologies
+1(845) 494-5277
--
Parity Technologies is a limited company registered in England and Wales
with registered number 09760015 and registered office at c/o Ignition Law,
1 Sans Walk, London, England, EC1R 0LT. This message is intended solely for
the addressee(s) and may contain confidential information. If you have
received this message in error, please notify us, and immediately and
permanently delete it. Do not use, copy or disclose the information
contained in this message or in any attachment. For information about how
we process data and monitor communications please see our Privacy policy
(https://www.parity.io/privacy/ <https://www.parity.io/privacy/>) and for
terms of use please see our Terms of Use policy
(https://www.parity.io/terms/ <https://www.parity.io/terms/>).
|
|
It's working fine for me. https://assethub-paseo.subscan.io/extrinsic/1595329-2Screen.Recording.2025-03-28.at.22.03.39.mov@dsedacca Can you check if you are getting any errors in browser console? |
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.
Looks great
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
π Description
A multisig account cannot sign transactions as an "any" proxy for its associated proxied account, resulting in an endless loop in the UI. The issue does not occur when the proxy account is a standard account instead of a multisig account.
π₯ Testing
Screen.Recording.2025-03-28.at.16.19.47.mov