Martín Triay

This error is due to [a change in gnosis safe's API](https://github.com/gnosis/safe-apps-sdk/commit/44318ec22ceba297fee01c602c45ca8819ad9a9d#diff-de9a4dcd9a544c19ca4e702d8676839ca1af09f515e050ad230309148d9e8b54L46) after which it doesn't provide a network name anymore. That name is eventually [used to initialize an ethers.js provider](https://github.com/OpenZeppelin/upgrades-safe-app/blob/master/src/ethereum/EthereumBridge.ts#L28),...

If that's the case I suggest you [use Defender](https://docs.openzeppelin.com/defender/guide-upgrades) (it's free!) to upgrade your contracts with your multisig until we release a fix.

what you mean by the API? i wasn't able to use openAI's API to build this

hey there @enitrat thanks for bringing this up! our overall feeling regarding this is to leave stuff as it is. A few thoughts supporting this idea are: * we want...

No bug at all! This works as intended _and documented_, and it will start working properly whenever the feature is implemented onchain. We've designed our contracts to be ready and...

Thanks! Will look into it after we finish the current release.

@TAdev0 thanks for asking! But this is being addressed already in #866, but since the PR wasn't properly linked this issue appeared in the "good to tackle" list. Fixed it...

e.g. https://github.com/OpenZeppelin/cairo-contracts/pull/896#discussion_r1488779465

Maybe it's worth considering having a 2step mechanism anyway, since in the current design the flow requires a bit of coordination between old and new owner: 1. new owner signs...

Bear in mind this hasn't been developed yet on the Cairo side, we should hold this until we do.