Some GnosisSafeWithoutProxy deployment txes can't be fetched

[bbenligiray]

GnosisSafeWithoutProxy is deployed non-deterministically on some chains and their default RPCs don't support fetching the deployment transaction

[bbenligiray]

The easy solution here is to deploy GnosisSafeWithoutProxy deterministically on these chains and then transfer all funds and the OwnableCallForwarder ownership from the old deployment to the new deployment.

[bbenligiray]

The list of chains on which GnosisSafeWithoutProxy is deployed non-deterministically is below. This list is not expected to grow, as the current deployment script deploys GnosisSafeWithoutProxy deterministically.

apechain-arbitrum-sepolia-testnet
arbitrum
arbitrum-sepolia-testnet
astar
astar-sepolia-testnet
avalanche
avalanche-testnet
base
base-sepolia-testnet
berachain-testnet
bitlayer
bitlayer-testnet
blast
blast-sepolia-testnet
bob
bob-sepolia-testnet
bsc
bsc-testnet
bsquared (see below)
camp-sepolia-testnet
conflux
conflux-testnet
core
core-testnet
ethereum
ethereum-holesky-testnet
ethereum-sepolia-testnet
fantom
fantom-testnet
fraxtal
fraxtal-holesky-testnet
gnosis
gnosis-testnet
immutable-sepolia-testnet
inevm
inevm-testnet
kava
kava-testnet
kroma
kroma-sepolia-testnet
lightlink
lightlink-sepolia-testnet
linea
linea-sepolia-testnet
lukso
lukso-testnet
lumia
lumia-sepolia-testnet
manta
manta-sepolia-testnet
mantle
mantle-sepolia-testnet
merlin
merlin-testnet
metal
metis
metis-sepolia-testnet
milkomeda-c1 (see below)
mode
mode-sepolia-testnet
moonbeam
moonbeam-testnet
moonriver
neon-evm (see below)
neon-evm-testnet (see below)
odyssey-sepolia-testnet
oev-network
opbnb
opbnb-testnet
optimism
optimism-sepolia-testnet
polygon
polygon-sepolia-testnet
polygon-zkevm
polygon-zkevm-sepolia-testnet
rari
rari-arbitrum-sepolia-testnet
rsk (see below)
scroll
scroll-sepolia-testnet
sei
sei-testnet
soneium-sepolia-testnet
taiko
taiko-holesky-testnet
unichain-sepolia-testnet
x-layer
x-layer-sepolia-testnet
zircuit
zircuit-sepolia-testnet
zksync (see below)

Among these, the following is only in chainsSupportedByManagerMultisig, which means that we can simply remove them from chainsSupportedByManagerMultisig and not replace with deterministic deployments. Note that this will also remove the OwnableCallForwarder. If we need the OwnableCallForwarder deployment file in the future (because we want to integrate in the future) we can refer to an old commit. As a separate note, the multisigs on these chains do not have any funds in them.

bsquared
milkomeda-c1
neon-evm
neon-evm-testnet
rsk
zksync

Edit: As a note, I realized that the on-chain owners on neon-evm-testnet has fallen out of date and its validation fails (iirc this is not our fault), which is all the more reason to officially retract multisig support

[bbenligiray]

So the course of action that I suggest is:

1. Deterministically deploy GnosisSafeWithoutProxy on the following chains, do a major release, then quickly execute the manager multisig transactions to
   • Transfer funds from the old GnosisSafeWithoutProxy contracts to the new ones
   • Transfer OwnableCallForwarder ownerships from the old GnosisSafeWithoutProxy contracts to the new ones

apechain-arbitrum-sepolia-testnet
arbitrum-sepolia-testnet
astar-sepolia-testnet
avalanche-testnet
base-sepolia-testnet
berachain-testnet
bitlayer-testnet
blast-sepolia-testnet
bob-sepolia-testnet
bsc-testnet
camp-sepolia-testnet
conflux-testnet
core-testnet
ethereum-holesky-testnet
ethereum-sepolia-testnet
fantom-testnet
fraxtal-holesky-testnet
gnosis-testnet
immutable-sepolia-testnet
inevm-testnet
kava-testnet
kroma-sepolia-testnet
lightlink-sepolia-testnet
linea-sepolia-testnet
lukso-testnet
lumia-sepolia-testnet
manta-sepolia-testnet
mantle-sepolia-testnet
merlin-testnet
metis-sepolia-testnet
mode-sepolia-testnet
moonbeam-testnet
odyssey-sepolia-testnet
opbnb-testnet
optimism-sepolia-testnet
polygon-sepolia-testnet
polygon-zkevm-sepolia-testnet
rari-arbitrum-sepolia-testnet
scroll-sepolia-testnet
sei-testnet
soneium-sepolia-testnet
taiko-holesky-testnet
unichain-sepolia-testnet
x-layer-sepolia-testnet
zircuit-sepolia-testnet

2. Wait a while and confirm that everything (mostly checklists) still work
3. Deterministically deploy GnosisSafeWithoutProxy on the following chains

arbitrum
astar
avalanche
base
bitlayer
blast
bob
bsc
conflux
core
ethereum
fantom
fraxtal
gnosis
inevm
kava
kroma
lightlink
linea
lukso
lumia
manta
mantle
merlin
metal
metis
mode
moonbeam
moonriver
oev-network
opbnb
optimism
polygon
polygon-zkevm
rari
scroll
sei
taiko
x-layer
zircuit

and remove the following chains from chainsSupportedByManagerMultisig

bsquared
milkomeda-c1
neon-evm
neon-evm-testnet
rsk
zksync

followed by a major release and the same manager multisig transactions.

[bbenligiray]

@hiletmis Can you open a PR that does step 1 (delete and redeploy GnosisSafeWithoutProxy contracts for those chains)? Then we can prepare the manager multisig script that creates the respective transactions, and release @api3/contracts once we're in a position to be able to do the transition swiftly.

[hiletmis]

Going for step 1

[bbenligiray]

Step 1 is done, will observe for a while before moving on with step 2