Closed sirpy closed 2 years ago
The UI doesn’t support custom contract deployments, sorry.
@katspaugh ok, any insights on why the official safe contracts are deployed using two different methods which creates two different sets of addresses? why isnt the new deployment method used on all chains?
Probably better asked on discord, there’s a dev support channel: https://discord.gg/AjG7AQD9Qn Cheers
Description
In order to achieve same safe address on multiple networks i've deployed the safe contracts myself: safe, proxyfactory and fallback handler. I was able to create a safe with the address 0x84C10B45fE51bfB4f86c19A47Fdbc187d4572Fb8 on Fuse, Celo, Ethereum The UI for fuse+celo (safe.celo.org safe.fuse.io) are able to find this safe The UI on ethereum reports that the safe is not valid, looking at the dev console I see the API call to fetch the safe info returns "404 not found"
Environment
Steps to reproduce
Add safe 0x84C10B45fE51bfB4f86c19A47Fdbc187d4572Fb8
Expected result
Safe is found
Obtained result
Safe not found
Screenshots