-
Notifications
You must be signed in to change notification settings - Fork 17
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
Can't update IMA due to gnosis safe api url change #1542
Comments
IMA: 2.0.0-beta.8 |
Gnosis updated their sdk from |
@DmytroNazarenko Triage |
Moved to 2.4 as 2.3 does not contain IMA mainnet contracts changes |
ima: 2.1.0-beta.2 |
Contracts update via multisig still not working "out of the box" for modern testnets e.g. Sepolia and Holesky IMA: 2.1.0-beta.2 Error log:
Solution:
For the holesky we should consider using 3rd party api url, as gnosis-safe do not provide their own api for this network, maybe we can use this project: https://holesky-safe.protofire.io/ |
Tasks
The text was updated successfully, but these errors were encountered: