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
Gnosis updated their sdk from safe-core-sdk to protocol-kit. In IMA upgrade script we still use old SDK, which causes problems with upgrade procedure via multisig. We should update dependencies to use protocol-kit instead of deprecated safe-core-sdk.
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:
Owner is a contract
Using Gnosis Safe
Error: Can't get safe-transaction url at network with chainId = 11155111
at getSafeTransactionUrl (/root/Workspace/IMA/proxy/node_modules/@skalenetwork/upgrade-tools/dist/src/gnosis-safe.js:109:15)
at /root/Workspace/IMA/proxy/node_modules/@skalenetwork/upgrade-tools/dist/src/gnosis-safe.js:98:27
at Generator.next (<anonymous>)
at fulfilled (/root/Workspace/IMA/proxy/node_modules/@skalenetwork/upgrade-tools/dist/src/gnosis-safe.js:5:58)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
Solution:
Add networks and api urls to gnosis-safe.js/gnosis-safe.ts like this (example for Sepolia network):
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/
Gnosis updated their sdk from
safe-core-sdk
toprotocol-kit
. In IMA upgrade script we still use old SDK, which causes problems with upgrade procedure via multisig. We should update dependencies to useprotocol-kit
instead of deprecatedsafe-core-sdk
.https://www.npmjs.com/package/@gnosis.pm/safe-core-sdk
The text was updated successfully, but these errors were encountered: