Interact with a legacy safe on BSC with a hardware wallet (Ledger)

Question

Context:

1. I own a Safe on 1.1.1 version deployed on Ethereum mainnet at address https://etherscan.io/address/0x65ef7d005f854a4cc0128b5b40edd5c4854c28af

2. I was the only Signer for this safe at the creation time, and I use a Ledger hardware wallet.

3. Someone sent funds to the Safe address on BSC

4. I've tried to replay the transaction to deploy a safe on BSC with the same address. The process looks successful (to be confirmed) as the address now appears to be a contract. https://bscscan.com/address/0x65ef7d005f854a4cc0128b5b40edd5c4854c28af

Problem:

I want to interact with the BSC Safe to transfer the funds but I cannot load it using the production UI. I understand that I could potentially use safe-cli instead to operate the Safe.

1. I did not manage to load the Safe using safe-cli (receiving an error, as if the Safe was non-existent)
2. Even if it was loading, I would prefer a different solution since I do not want to compromise my Ledger.

Question:

1. Is the Safe on BSC successfully deployed?
2. If yes, what could be the reason why I cannot load it with safe-cli?
3. Is there a workaround to safe-cli with a native Ledger integration? Like setting up locally an older version of the Safe UI? If yes, which version?
4. I've stumbled upon this script: https://github.com/virendrapatidar/multisig-delegator (specifically the Ledger version). If I understand well, I could use it to delegate the Safe to a dedicated hot wallet (instead of my Ledger), and then use safe-cli with the new delegate, without compromising my primary Ledger wallet. Could it be a solution?

Thank you so much in advance :)

Answer 1

Yes, the Safe on BSC has been successfully deployed, as it appears as a contract on BSCScan.

The reason why you cannot load the Safe using safe-cli might be due to a mismatch of network IDs or a lack of configuration in safe-cli.

Using a older version of the Safe UI might not work as the integration with Ledger hardware wallet has been updated in recent versions.

Yes, This Repository could be a solution for you as it allows delegation to a hot wallet without compromising your primary Ledger wallet. By delegating the Safe, you can interact with it using safe-cli without compromising the security of your Ledger hardware wallet.

Answer 2

If yes, what could be the reason why I cannot load it with safe-cli?

That depends on a lot of things. What is the error message you received? What OS are you running? What version of the CLI are you running? etc.

I've stumbled upon this script: https://github.com/virendrapatidar/multisig-delegator... I could use it to delegate the Safe to a dedicated hot wallet, and then use safe-cli with the new delegate. Could it be a solution?

Yes. In fact, I have a potential solution to both of your questions. It's something I've been experimenting with recently. You could run the safe-cli in a cloud environemnt. I made a notebook that allows you to run the safe-cli in a cloud server that way you don't have to worry about OS specific issues that occur when you install a package locally.

You can use it by just adding your desired address and node url operations. Works easily for read only operations like seeing your Safe balance.

The caveat is that if you want to write/execute a transaction, it requires you to enter your private key. Although it uses getpass to offer some degree of obfuscation, it's not perfect.

If you are worried about security of entering private key in a cloud server, here's my suggestion:

1. Create a "temporary/disposable" signing account.
2. Give it delegate permissions to do whatever you need. You could use multisig-delegator for this.
3. Use that signing account in the cloud server to execute transactions
4. Remove the signing account when finished.