video1.0<iframe src="https://www.loom.com/embed/ca34aabcd62747fb9fb89bd463b4c741" frameborder="0" width="1152" height="864" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>8641152Loomhttps://www.loom.com8641152https://cdn.loom.com/sessions/thumbnails/ca34aabcd62747fb9fb89bd463b4c741-00001.gif183Chainlist: https://chainlist.org/ Proxyfactory deployments: https://github.com/gnosis/safe-deployments/blob/main/src/assets/v1.3.0/proxy_factory.json IMPORTANT! If your safe was 1.1.1 at the time of the creation, transactions could be replayed across chains unless you upgrade to 1.3.0. IMPORTANT! It will create the Safe with the same ownership structure as at the creation. So it means if you initially created a Safe with owners A and B and then changed owners to C and D, it will deploy the Safe with owners A and B on the other network. !!! IMPORTANT !!! It must be noted that Safes with the same addresses on L2 and sidechains work out of the box with the Web and desktop UI. However, existing Safe addresses on Eth mainnet re-created on L2/sidechains (and vice versa) do not load up within our UI. This is because they use different singleton contracts. Therefore, users would need to load these newly created Safes via another UI, e.g. through our command line interface: https://github.com/gnosis/safe-cli.