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
Kevin assisted in adding a new signer to the allocator as detailed in this issue and modified the new JSON file accordingly here. However, upon connecting the ledger and proposing on allocator.tech, I received the following error message:
"Message execution failed: exit ErrForbidden(18), reason: message failed with backtrace: 00: f03019831 (method 2) -- f03236388 is not a signer (18) (RetCode=18)."
Could you please assist? Thank you!
The text was updated successfully, but these errors were encountered:
This means that the new address is not a signer in your multisig.
Adding to JSON is not enough (it's only there for documentation purposes) - it needs to be added onchain. Please reach out to the Governance Team again.
Hello,
Kevin assisted in adding a new signer to the allocator as detailed in this issue and modified the new JSON file accordingly here. However, upon connecting the ledger and proposing on allocator.tech, I received the following error message:
"Message execution failed: exit ErrForbidden(18), reason: message failed with backtrace: 00: f03019831 (method 2) -- f03236388 is not a signer (18) (RetCode=18)."
Could you please assist? Thank you!
The text was updated successfully, but these errors were encountered: