You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Ran sh run_locally.sh to set up the Safe infrastructure.
Saved ChainInfo for Neura Network in the Config Service admin panel.
Confirmed that Neura Network has MasterCopies and ProxyFactories deployed and registered in the Transaction Service admin panel.
L2 is selected
Verified connection to the Neura node from the Transaction Service container.
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).
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
Issue
Smart Contract Addresses on Chain Info
The text was updated successfully, but these errors were encountered:
@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.
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.
Environment Details
.env
file contents: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
sh run_locally.sh
to set up the Safe infrastructure.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.
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
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
Issue
Smart Contract Addresses on Chain Info
The text was updated successfully, but these errors were encountered: