From 51ebd8e0dfb9daae021e539d59d30feac31f9e3a Mon Sep 17 00:00:00 2001 From: Eva <1017762+eshon@users.noreply.github.com> Date: Thu, 19 Dec 2024 13:33:37 +0100 Subject: [PATCH] Adding extra info about Safe migrations --- smart-contracts/advanced/multisig.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/smart-contracts/advanced/multisig.md b/smart-contracts/advanced/multisig.md index 18a17d052..e34a0591c 100644 --- a/smart-contracts/advanced/multisig.md +++ b/smart-contracts/advanced/multisig.md @@ -51,8 +51,8 @@ A web UI for the Safe multisig on Filecoin is available at: - **Safe addresses from other networks** can sometimes be used but require additional technical steps. - In some cases the same Safe address and owner structure is not possible, learn more in [this article](https://help.safe.global/en/articles/40812-i-sent-assets-to-a-safe-address-on-the-wrong-network-any-chance-to-recover). - Confirm complete creation (not just as a Placeholder) of the Safe multisig as an EVM contract on Filecoin prior to sending major funds. - - Instructions for deploying a Safe at the same address on another chain are [available in this video](https://share.zight.com/z8uBKZYr). - - If the previous address and chain use the L1 version of Safe Proxy, more complex technical migration steps will be required to map to the L2 version on Filecoin. Contact Safe-related support for more info. + - Instructions for deploying a Safe at the same address on another chain are available in [this video](https://share.zight.com/z8uBKZYr). Note that a compatible version of the Safe Proxy on the original chain must exist on Filecoin. Contact Safe-related support for help. + - If the previous address and chain use the L1 implementation of Safe Proxy, more complex technical migration steps will be required to map to the L2 version on Filecoin. Contact Safe-related support for more info. - **Safe-related support** can be found in the "Need Help?" section of the Safe web UI. #### Safe Transaction Service