Hi, In ethereum for upgradable contracts using openzeppelin plugins we use Gnosis safe multisig for transfer our controls of upgrades ,
but gnosis safe multisig does not support binance smart chain testnets (i am not sure about this statement if it wrong please correct it too…)
for binance which application we will use to transfer our control of upgrades thats my doubt.
1 Like
Hi @Prabhakaran,
It is recommended to transfer control of upgrades to something more secure than an Externally Owned Account (EOA) such as a multisig. See: https://docs.openzeppelin.com/learn/preparing-for-mainnet#set-admin
You could potentially look at the legacy Gnosis Multisig: https://github.com/gnosis/MultiSigWallet
You may want to reach out to the Gnosis team to see if they have any recommendations for the Binance chain: https://chat.gnosis.io/
Hi @abcoathup still i didn’t got idea about it …
My question is after deploying our upgrading contract we have to do some steps in gnosis safe multisig openzeppelin app for upgrading our contract,for that we will gave proxy contract address and new implementation address.but gnosis safe only support ethereum ,is there any other mutisig app that link with openzeppelin which supports binance…
1 Like
Hi @Prabhakaran,
You could potentially look at the legacy Gnosis Multisig: gnosis/MultiSigWallet.
Though you don’t get the UI of Gnosis Safe or the apps.
You would need to use the multisig to create the transaction to upgrade.
Hi @abcoathup ,
I will make a look at legacy of gnosis multisig,
and is there any other option is there we will use to create the transaction to upgrade…other than use of multisig…
1 Like
Hi @Prabhakaran,
Changing to a multisig is recommended. See: https://docs.openzeppelin.com/learn/preparing-for-mainnet#set-admin
I recommend reaching out to the Gnosis Safe team to see if supporting Binance smart chain is on their roadmap.
1 Like