You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 24, 2021. It is now read-only.
A friend of mine is having an issue with signing on our gnosis multisig
He is getting the error: gas required exceeds allowance (8562366) or always failing transaction
He is trying to sign with a ledger nano s
He has 3 different addresses on his ledger nano s. The address that is authorized to sign on the multisig is the 3rd address in his ledger nano s.
Any solutions to this? The other signer has also has issues with confirming transactions from his ledger nano s as well but is getting an error for 'internal error'
I have a feeling it is the way that the gnosis multisig is interacting with which ledger nano s address to use (and just using the first address available).
Is it possible to allow the user to choose which address he will be signing with while in the gnosis multisig wallet interface?
The text was updated successfully, but these errors were encountered:
A friend of mine is having an issue with signing on our gnosis multisig
He is getting the error:
gas required exceeds allowance (8562366) or always failing transaction
He is trying to sign with a ledger nano s
He has 3 different addresses on his ledger nano s. The address that is authorized to sign on the multisig is the 3rd address in his ledger nano s.
Any solutions to this? The other signer has also has issues with confirming transactions from his ledger nano s as well but is getting an error for 'internal error'
I have a feeling it is the way that the gnosis multisig is interacting with which ledger nano s address to use (and just using the first address available).
Is it possible to allow the user to choose which address he will be signing with while in the gnosis multisig wallet interface?
The text was updated successfully, but these errors were encountered: