Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Creating Safe Account on Local Chain Setup: "Error creating the Safe Account. Please try again later" #158

Open
candostyavuz opened this issue Sep 6, 2024 · 2 comments

Comments

@candostyavuz
Copy link

candostyavuz commented Sep 6, 2024

Hi, we are currently trying to deploy Safe infrastructure locally into our EVM compatible Cosmos SDK chain: Neura.
We are following the steps described in this guide: (https://github.com/safe-global/safe-infrastructure/blob/main/docs/running_locally.md

The Issue

After following the local setup steps , the frontend throws an error when creating a new Safe account on the local Neura chain.

  1. Able to connect MetaMask to the Neura Network.
  2. "Error creating the Safe Account. Please try again later." upon pressing "Create" in the UI.
  3. The setup is using a local Neura chain (RPC: http://192.168.1.22:8545/, Chain ID: 268).

Environment Details

  • Docker-compose setup using safe-infrastructure repository
  • Neura local chain (EVM compatible)
  • RPC endpoint: http://192.168.1.22:8545/
  • Chain ID: 268
  • .env file contents:
REVERSE_PROXY_PORT=8000
CFG_VERSION=latest
CGW_VERSION=latest
TXS_VERSION=latest
UI_VERSION=latest
EVENTS_VERSION=latest
RPC_NODE_URL=http://192.168.1.22:8545
  • In cfg.env we also tried adding this line for webhooks as suggested here:
    CGW_FLUSH_TOKEN=your_privileged_endpoints_token . It made no difference fixing our issue.

Steps Taken

  1. Ran sh run_locally.sh to set up the Safe infrastructure.
  2. Saved ChainInfo for Neura Network in the Config Service admin panel.
  3. Confirmed that Neura Network has MasterCopies and ProxyFactories deployed and registered in the Transaction Service admin panel.
  4. L2 is selected
  5. Verified connection to the Neura node from the Transaction Service container.
  6. Configured webhooks in the admin panel according to the local deployment guide.

Contract Deployment

We are currently aiming for setting up and using the Safe multisig wallet locally as a Proof of Concept for future mainnet deployment.

  • Since our chain is still in development phase, it has no registry in https://chainlist.org/
  • No PRs were sent for contract deployment or chain registration into the official Safe registry.

Contracts were copied from the safe-smart-accounts repository and deployed manually on the local Neura chain.
There are no singleton addresses as typically used in the official Safe deployments.

Debugging Steps Performed

  • Checked Transaction Service and Client Gateway logs for errors (none found).
  • Verified Ethereum node connection (successful, current block: 0x1edb).
  • Verified account balance (sufficient: 0xc1ba640c82f64108).

No visible errors in Transaction Service or Client Gateway logs. Successful communication between Safe services and the Neura node.

Requested Assistance

We notice that similar error is observed in relevant issues: #152
We simply need guidance about the root cause of the "Error creating the Safe Account. Please try again later." issue and potential fixes.

Also an advice on any necessary configurations for using custom-deployed Safe contracts without singleton addresses would be really helpful.

Thanks in advance!

Attachement

  1. Issue
    Screenshot 2024-09-04 at 16 55 25

  2. Smart Contract Addresses on Chain Info

Screenshot 2024-09-06 at 15 22 49
@SurenFTN
Copy link

@candostyavuz do you solved this issue> I have the same problem

@candostyavuz
Copy link
Author

@SurenFTN Unfortunately no, I haven't got any answers or support yet. I think the backend infra of this repo heavily relies on the other Safe repos or external links (such as chainlist.org) and fetches the required info from those constant APIs. That's the reason of the strange errors most likely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants