xDai compatibility

[lukasschor]

_Deadline: October 19. If we don't make this deadline, please reach out on Slack. _

What is this feature about? (1 sentence)

This makes the Gnosis Safe Multisig available on xDai via https://xdai.gnosis-safe.io/app.

Why is it needed? What is the value? For whom do we build it?

• We want to make the Safe Multisig web interface also compatible with the Gnosis Safe contracts / backend services on xDAI.
• This is important for Gnosis since we commited to leverage xDai as L2 more. cf. blog post
• Also on L2, high value assets can be managed. So the same security requirements apply like on mainnet.
• The contract controlling the bridge between xDai and mainnet is supposed to be a Gnosis Safe soon.

High-level overview of the feature

• The xDai Safe (contracts and interfaces) should be completely separate to mainnet (and Rinkeby). At this point, there should not be a "bridging" feature or something similar between mainnet and xDai.

• Please note: ETH is not the native currency to pay gas costs on xDai, but rather xDai.

• The web app should be available at https://xdai.gnosis-safe.io/app

  • Probably requires involvement by Devops for deployment
  • https://xdai.gnosis-safe.io should automatically forward to https://xdai.gnosis-safe.io/app

• No need for a desktop app for xDAI at this point.

• Only the 1.1.1 Safe contracts are deployed on xDai. They have the the same addresses like on mainnet, i.e. e.g. 1.1.1 mastercopy at 0x34CfAC646f301356fAa8B21e94227e3583Fe3F5F

• Transaction-service on xDai: https://safe-transaction.xdai.gnosis.io/

• Some wording changes (should be kept to a minimum for the first version)

  • Network label ("xDai")
  • We have this notification about "Rinkeby - don't send mainnet funds". This one should not be shown for xDAI.
  • Please adapt the popup "You Must Change Networks" accordingly.

• Instead of ETH, on xDai, the native currency is xDai, so ETH should be hidden/not show up in the assets overview.

• Use UA-83220550-22 for Google Analytics tracking

Misc

• Please note: We are planning to add support for 2 more networks(EWC & Volta compatibility #1253) quite soon. Please keep that in mind, when deciding whether to hardcode or make this more generic.

Updates

• Sep 30, Tobi: Add Google Analytics tracking code

[tschubotz]

We are now adding support for 3 new networks (xDai, EWC and Volta). We use different URL and we have the network label but besides that, there is no differences. This could be a problem.
@dasanra had the idea to change some main/background/header css color respective to the used network. What do you think about this @posthnikova? Would this be possible?

[posthnikova]

@tschubotz Do you mean change the color in dropdown https://prnt.sc/up5vvy where it says Mainnet or everywhere in the interface? By the way in the dropdown the color doesn't change for Rinkeby.

This could be a problem.

You can't use the interface when you owner wallet is on wrong network, there is a 'Wrong network' popup which blocks everything. Would it also work this way for xDai, EWC and Volta?

[tschubotz]

@tschubotz Do you mean change the color in dropdown https://prnt.sc/up5vvy where it says Mainnet or everywhere in the interface?

What we had in mind was a more drastic UI hint, such as e.g. the entire header row:

Dani said, they did something similar in the DutchX admin interface and it helped. That's how this came up.

You can't use the interface when you owner wallet is on wrong network, there is a 'Wrong network' popup which blocks everything. Would it also work this way for xDai, EWC and Volta?

That's right. It would also work this way for xDai, EWC and Volta. So a UI change would be in addition to that, to make it even more clear that these are different apps.

On the other side, I'm only aware of 1 report so far where someone sent mainnet funds to a Rinkeby Safe address.

[posthnikova]

I would maybe rework the tag in header so it changes color.

I'm not sure about changing the color of header. It would draw too much attention.

[tschubotz]

It would draw too much attention.

That would be the purpose of it though ;) i.e. to know that this is a different env.

[posthnikova]

The purposes of indicating network are:

1. to connect a wallet that is on the right network
2. to prevent sending mainnet funds to testnet addresses

1 we have more or less covered, you can't use the interface when it's blocked.
2 is not really covered. We have a network tag in the header and a notification 'Rinkeby version - don't send mainnet assets to this Safe'. Mistakes could happen when the user copies Safe address. But we don't warn when the users copy Safe address on testnets and there is no indication in Receive popup. So maybe we should add these?

[tschubotz]

2 is not really covered. We have a network tag in the header and a notification 'Rinkeby version - don't send mainnet assets to this Safe'. Mistakes could happen when the user copies Safe address. But we don't warn when the users copy Safe address on testnets and there is no indication in Receive popup. So maybe we should add these?

Not only fore testnet <> mainnet: xDai and EWC are not testnets and users should not assume that a Safe on 1 network exists on the other network as well.

Hence we thought it would help making it visually clear that the apps are not interchangeable would help.

[posthnikova]

I'm sure it should be somewhere near the Safe address and in Receive popup.