-
Notifications
You must be signed in to change notification settings - Fork 2
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
Signers are getting "Invalid owner provided" error #91
Comments
Hey @joanpan , is the transaction in the queue the problematic one? https://app.safe.global/eth:0xb270FE91e8E4b80452fBF1b4704208792A350f53/transactions/queue I can (successfully simulate) execute it. The problem is only with the owners not being the first one who signed? Normally this error can happen with a wrong order in the signatures or with incorrect information signed |
Hi @yagopv, We have 3 other users experiencing the same issue.
|
so they are all in 1.1.1 right? |
That is correct. |
For user 3 with safe address https://app.safe.global/eth:0xAEe07CFaeA5eaaB0487968AFdcFFceEaCa48851E/transactions/queue, this is the signer address used 0x2aC29585a7A1371A83e1C0818F4c45A92DDf8Db2 when error came up. Tenderly - https://dashboard.tenderly.co/public/safe/safe-apps/simulator/713435ea-e699-4cf6-9cc1-3e0d7c72b2c4 |
The transactions with one missing signer i guess they tried to sign and execute right? For scoping the error to the execution |
That is correct. 5th owner was a typo, I meant to say 6th signer. |
Opened a ticket in the web-core repo (new UI) |
Hi! The fix for this ticket was included on our last release of the web interface so I will go ahead and close it. Cheers! (and sorry for the spam today, going through every ticket on the repo) |
Issue Category
Transaction execution issue
What happened?
Multiple signers are getting "Invalid owner provided" error. First signer who initiated the transaction did not get the error.
https://dashboard.tenderly.co/public/safe/safe-apps/simulator/30a2ad33-9362-4c3b-94d4-ed224f53a928?trace=0.0.1.2
Transaction was created in the new UI. Tested in the old UI and it seems to working fine. Issue is only in the new UI.
Safe address:
eth:0xb270FE91e8E4b80452fBF1b4704208792A350f53
Date and time this happened or you first noticed this issue
09-12-2022
Network
Ethereum Mainnet
Safe Address
0xb270FE91e8E4b80452fBF1b4704208792A350f53
Token Address
No response
Token Type
None
Transactions
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: