Configuration of Chain IDSee original GitHub issue
Describe the bug I am attempting to use safe contracts I have deployed on a private subnet on the avalanche network. I am able to successfully create a safe and send funds to it. However when I am attempting to interact with the safe (eg. add owner) I am getting the following error.
web3.exceptions.ValidationError: The transaction declared chain ID -1, but the connected node is on 335
There may be an obvious way to configure the chainID on the CLI that I am not seeing in the documentation, or something else is going on.
To Reproduce Steps to reproduce the behavior:
- Connect to a safe on subnet
- Load CLI Owner
- run add_owner [address]
Expected behavior I expected the transaction to be sent to the RPC
Additional context Our chain ID 335 is not a supported gnosis safe chain yet.
- Created 10 months ago
- Comments:11 (6 by maintainers)
Top GitHub Comments
Yep just generated a new wallet for this and provided 1 JEWEL. (ETH)
Wallet Address: 0xF28576408412a1f0bAbE1BFbC8afC51F9b650B07 Safe Address: 0xEc358bd2e7d1Bfffd5B56d94eb5b506560cFc629 Private Key: 4b94863054d2e492f50795c16c4406ddba8c07d83d47de6bab2af5940812a3f7