0

I have several wallets that need to be accessed with the interface that was live on https://gnosis-safe.binance.org. When it changed to https://gnosis-safe.io/app/bnb I transferred several funds but forgot other multi-sig wallets with serious funds on them. Just to be clear: isn't about the second and current, new interface (gnosis-safe.io/app/bnb and app.safe.global/bnb).

All the Gnosis multi-sig wallets are deployed with pragma solidity >=0.5.0 <0.7.0.

Is there still an interface like gnosis-safe.binance.org available, so that I can access the wallets? I have all the sign-owner wallets still. I can't access the wallets of course via BscScan > proxy-write page of the Gnosis wallet contract, because the contract deployer wallet is one of the standard deployer wallets of Gnosis itself, that deployed the contract when I requested it with the then-new sign-owner wallet.

Now I found previous versions of Gnosis Safe from 2021 on Github. Am I right, that I can use this to access my Gnosis multi-sig wallets, by uploading the website files to GitHub and connecting app.fleek.co with my GitHub repository? Am I able to access it in this way?

This is one of the previous versions of 2021, released in August. I made several Gnosis multi-sig wallets around March and later on in 2021.

The link to version v3.12.0: https://github.com/safe-global/safe-react/releases/tag/v3.12.0

I hope that some skilled developer can help me to solve this issue! Much appreciated.

When I want to deploy the site on app.fleek.co, I need to choose for the right Framework; I think it is 'Other'; or is it 'Create React App'?

These are the fields that I have to fill in. In the following screenshot you can see what I have added.

Docker image Name: 'Gnosis-safe' (name Repository in GitHub); Build command: 'npm install && npm run build'; and by Public directory 'build' (or does it need to be 'public'?

Improve this question
8
  • Have you tried connecting your safe address to the new interface gnosis-safe.io/app/load ? If I'm the safe's owner, I will try that first. and the thing I'm concern is which release of the contract code that I used github.com/safe-global/safe-contracts/releases . I think it will likely be backward compatible.
    – minhhn2910
    Dec 29, 2022 at 9:18
  • Thanks for your fast answer! I've tried this already, and it says: "Address given is not a valid Safe address". For example this gnosis multisig: 0x8e567a6346c1AC50e9466c20C1b6454027c9442D. I've uploaded the Gnosis Safe v3.12.0 version, but that's an outdated release (but compatible with the gnosis contracts that I need to access), but when I want to deploy it at geek it says that it can't find /workspace package.json, but this .json file is uploaded. If the deployment succeeds then I should be able to use the interface in order to connect with my old multisigs? Or is there also an easier way?
    – Amos ProDeo_Crypto
    Dec 29, 2022 at 15:59
  • @minhhn2910 How do I have to fix it? Because I can't access the backend of the wallet via the proxy write tab on BscScan. And because geek specifies that it can't find /workspace package.json I can't deploy the frontend and therefore also not access the wallets.
    – Amos ProDeo_Crypto
    Dec 30, 2022 at 13:05
  • The code is ok to to run in local environment. And what is the problem you faced when you use "Write contract as Proxy" ? like this : bscscan.com/address/…
    – minhhn2910
    Dec 30, 2022 at 14:40
  • If you just want to withdraw once and don't use the Safe anymore. I would recommend using Remix or BSCscan. However the transaction data is a bit complex to novice user.
    – minhhn2910
    Dec 30, 2022 at 14:41

1 Answer 1

Reset to default
0

The main question here is how to deploy safe-react/releases/tag/v3.12.0 on app.fleek.co and it's up to the service's user guide and instruction on how to fill those fields. Since the op says it's ok to post an alternate solution to run react locally, I will post it here. The safe-react repo using yarn for building. Step by step:

  1. First you need to install nodejs. Here https://nodejs.org/en/download/
  2. Use npm to install yarn: npm install --global yarn. Read more here
  3. Use yarn to build or run the project:
    • yarn install
    • yarn start
    • it will automatically open your browser at the default address http://localhost:3000/

Result: enter image description here

More information is on the README file in the repo

Improve this answer
1
  • Hey @minhhn2910! Thanks for your super answer. I installed odejs; then I've installed via npm command in Terminal yarn. But when I want to call npm install --yarn install then it gives an error message...
    – Amos ProDeo_Crypto
    Jan 1 at 13:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.