[BUG] transaction builder on AVAX uses mainnet deployment of MultiSend not the AVAX deployment

[liliya-soroka]

@0xm3rlin commented on Fri Jan 14 2022

Description

On Avalanche, the transaction builder app should use the correct MultiSendCallOnly contract (https://snowtrace.io/address/0xA1dabEF33b3B82c7814B6D82A79e50F4AC44102B#code) instead of trying to use https://snowtrace.io/address/0x40A2aCCbd92BCA938b02010E17A5b8929b49130D.

Steps to reproduce

1. Try creating a multisend transaction on the AVAX deployment of Gnosis Safe

Expected result

Flawless multisend

Obtained result

Screenshots

---

@liliya-soroka commented on Mon Jan 17 2022

The issue appears if the network was switched after the networks with other safe contracts.
Steps to reproduce:

1. Open Rinkeby
2. Open transaction builder and create multisend transaction
3. switch network in the right corner to avalanche ( or any other network where the safe contracts have different from Rinkeby addresses - see safe-deployment for details for L2 networks) and switch network for the connected owner using switch network for wallets in safe app
4. open transaction builder and try to create a multisend tx ( send native coints to owner account a few times )
   Current result: The Multisend contract from Rinkeby is used
   The opposite situation is true : open avalanche first and switch to Rinkeby => the contract address from avalanche will be used on Rinkeby