Closed cuvialabs closed 1 year ago
Any comment on this?
Any comment on this?
@cuvialabs Please see my comment on #753, I believe I've resolved the issue
Replied to #753, same result. Its defaulting to the active key, when I'm logged in with the owner.
Sorry to be a pain on this, but its blocking our workflow. Any update? Did you push the new version with the fix?
Describe the bug A clear and concise description of what the bug is. Telos Explorer will not allow me to sign an msig updateauth proposal with an owner key. It defaults the key back to active which results in an assertion error.
To Reproduce Steps to reproduce the behavior:
Anyhow, this is not something that we can repair on our end, so i would suggest reaching out to the Telos support team for their block explorer and see what they recommend as a solution, We'll be reaching out as well, but the more people bring up the issue, the more they are likely to fix it. If there's anything else we can help you with, please let us know."
Expected behavior A clear and concise description of what you expected to happen. I log in as owner to approve a msig, I need to be able to sign as owner.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context We're hardening our treasury security with Ledger wallets. We need to be able to add and remove owner keys to our system accounts. We are using a similar account structure to Telos's eosio account. Can you suggest a work around for this that will allow us to still use HW wallets? How do you handle this on the eosio account?