-
Notifications
You must be signed in to change notification settings - Fork 400
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
Counterfactual Safe on Base ended up with unnofficial L1 contract #3812
Comments
I can reproduce this if I manually hard-code the chainId in So my guess is that this is the culprit but we need to figure out how it can happen that the chainId is not updated when activating an account. |
Pushed this back for now as its not clear how to arrive at this state. The way we handle it during safe creation is that we enforce that the users wallet needs to be on the same network as the safe they are about to create. That way we ensure to fetch the correct safe factory contract. |
Can't we use our readonly provider to fetch the contract? Also fetch from where, why? |
We have to call the |
Bug description
User reported that they counterfactually created Safe on Base. After deploying and receiving some ETH, they tried to transfer the ETH out and received the unsupported base contract error. Turns out the Safe got deployed with the L1 contract using the mainnet L1 contract deployment address instead of our official L1 Base contract deployment.
Safe: https://app.safe.global/home?safe=base:0x879D41d53c33F43B0CF31e909A2d3F1C2eb2cf80
Proxy: https://basescan.org/address/0x879D41d53c33F43B0CF31e909A2d3F1C2eb2cf80
Singleton: https://basescan.org/address/0xd9Db270c1B5E3Bd161E8c8503c55cEABeE709552
Environment
Steps to reproduce
need to find out
Expected result
L2 Safe following official deployments
Obtained result
Screenshots
The text was updated successfully, but these errors were encountered: