-
Notifications
You must be signed in to change notification settings - Fork 960
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
Technical background for onlyNonceZero
in SafeToL2Migration
?
#720
Comments
onlyNonceZero
?onlyNonceZero
in SafeToL2Migration
?
I have found #685 and it is stated:
... but when there have not been any configuration changes, it should be allowed to exchange the singleton, IMHO. |
tagging @Uxio0 |
There's no way for the indexer to know if there have been configuration changes or not as Safes cannot be indexed without events, that's the reasoning. We are very strict in the correctness on the data that we index and give the users, and that's why we cannot fall into asumptions. |
Ah got it - thanks. In my case, I hacked me through the safe tool-chain in order to fix my L2 safe with a nonce other than 0 (made one ERC20 transfer before). Here's my journey (PSA: do not try this at home without knowing what you do) I had to manipulate both the |
We cannot guarantee them that your Safe will work propertly with our services/UI, but it's good as long as you understand that being an advanced user 😉 |
I'd like to understand the background why a migration cannot be done for Safes that have a nonce other than zero. Is it really necessary?
https://github.com/safe-global/safe-contracts/blob/f03dfae65fd1d085224b00a10755c509a4eaacfe/contracts/libraries/SafeToL2Migration.sol#L74-L78
The text was updated successfully, but these errors were encountered: