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 the Safe Account for Sei Pacific Mainnet #152

Open
junkim012 opened this issue Jul 28, 2024 · 1 comment
Open

Error creating the Safe Account for Sei Pacific Mainnet #152

junkim012 opened this issue Jul 28, 2024 · 1 comment

Comments

@junkim012
Copy link

The Issue

After following the local setup steps, the frontend throws an error when creating a new Safe account on Sei Pacific Mainnet.

  • Able to connect metamask to Sei Network and Metamask picks up correct mainnet SEI balance in wallet.
  • Error creating the Safe Account. Please try again later. upon pressing "Create" in the UI. (Picture attached).
  • Notably the ui.env file was left empty. Infura does not support Sei Network. (and many other rollups unsupported by the official safe app UI that we want to deploy a safe multisig on).
    • Would appreciate guidance on how to set up the ui.env file in this case.
### ui.env
### Required variables ###
NEXT_PUBLIC_INFURA_TOKEN=
NEXT_PUBLIC_GATEWAY_URL_PRODUCTION=http://localhost:8000/cgw

# infura token used by Safe Apps
NEXT_PUBLIC_SAFE_APPS_INFURA_TOKEN=

# Transaction simulation
NEXT_PUBLIC_TENDERLY_SIMULATE_ENDPOINT_URL=
NEXT_PUBLIC_TENDERLY_PROJECT_NAME=
NEXT_PUBLIC_TENDERLY_ORG_NAME=

Screenshot 2024-07-28 at 11 17 44 PM
Screenshot 2024-07-28 at 11 18 46 PM

Steps Taken

  1. Ran sh run_locally.sh
  2. Saved ChainInfo for Sei Network
  3. Confirmed that Sei Pacific Network has MasterCopies and ProxyFactories deployed.
  • In the addresses.py file, confirm that both contracts are deployed on mainnet. The bytecode also exists when quried through cast code on sei pacific.
  • Screenshot 2024-07-28 at 11 09 07 PM
  • Screenshot 2024-07-28 at 11 09 57 PM
  1. Add webhooks
  • No changes to the cgw.env file AUTH_TOKEN=your_privileged_endpoints_token or the cfg.env file's CGW_URL or CGW_FLUSH_TOKEN.
  • The local setup docs in section "Step 5: Add your webhooks" says to "Leave chains field blank". Tried both with the chains field blank, and also adding a chain via the chainId 1329.

ChainInfo Form for Reference

Sei Network | chain_id=1329
Chain Id: 1329
Relevance: 100
Chain name: Sei Network
EIP-3770 short name: sei
Description:
L2: tried both checked and unchecked
Is testnet: unchecked 
Rpc authentication: No Authentication
Rpc uri: https://hardworking-multi-patron.sei-pacific.quiknode.pro/<token omitted>/
Safe apps rpc authentication: No Authentication
Safe apps rpc uri: https://hardworking-multi-patron.sei-pacific.quiknode.pro/<token omitted>/
Public rpc authentication:No Authentication
Public rpc uri: https://hardworking-multi-patron.sei-pacific.quiknode.pro/<token omitted>/
Block explorer uri address template: https://www.seiscan.app/pacific-1/accounts/{{address}}
Block explorer uri tx hash template: https://www.seiscan.app/pacific-1/txs/{{address}}
Block explorer uri api template: https://www.seiscan.app/pacific-1/txs/{{address}}
Currency name: sei
Currency symbol: SEI
Currency decimals: 18
Transaction service uri: http://nginx:8000/txs
Vpc transaction service uri: http://nginx:8000/txs
Theme text color: #ffffff
Theme background color: #000000
Ens registry address: [empty]
Recommended master copy version: 1.3.0
Prices provider native coin: [empty]
Prices provider chain name: [empty]
Balances provider chain name: [empty]
Balances provider enabled: [unchecked]
Hidden: [unchecked]
![Screenshot 2024-07-28 at 11 01 40 PM](https://github.com/user-attachments/assets/b419cd8c-1fc2-469b-8fc3-642a459b35d0)
@candostyavuz
Copy link

Hi @junkim012 , have you found any solution to this "Error creating the Safe Account. Please try again later" error?
We have also taken the same steps as you described above and we also encounter this same issue - which gives no clue about what is wrong with the setup.
If you can share the solution that would be really helpful for us and future integrators! Thanks in advance!

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