Allow to add Safes where connected wallet is an owner

What is this feature about? (1 sentence)

This feature allows users to more easily load Safes which they are an owner of.

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

• Currently, users need to always paste (or scan) the address of a Safe in order to add it.
• We have heard that users know their owner wallets, but don’t always have their Safe address handy.
• This helps keeping an overview of one’s Safes.

High-level overview of the feature

• There is already a backend endpoint the Safes can be queried where a given address is owner of (https://safe-transaction.gnosis.io/api/v1/owners/0x0e329fa8d6Fcd1ba0Cda495431F1f7CA24F442C2/)
• tbd

Idea 1:

• As a simple first version, just check after a wallet is connected if there are Safes associated with this wallet that are not in the Safelist and add them (maybe in a seperate / expandable section of the safelist. The Safes can be given names such as “Safe 0x1234…abcd” (“Safe abbreviated address”)

Idea 2: When loading a Safe, instead of asking the user to paste the Safe address, they could choose from a list of Safes where the connected wallet is an owner of and which haven’t been added, yet. Thereby they would have to add each Safe one by one and could provide a name.

[posthnikova]

If there is no Safe loaded, after hitting “Load x Safes”, which Safe the user will be directed to?

@fernandomg The list is alphabetical so the first one in the list.

Shall we add an option to set the “default” Safe?

We agreed to remove ‘default’ Safe https://app.zenhub.com/workspaces/safe-multisig---web-5ce554debb310a35b2f8b6f8/issues/gnosis/safe-react/1256

[Uxio0]

Yes @fernandomg https://safe-transaction.rinkeby.gnosis.io/api/v1/owners/<owner-address-checksummed>/

@lukasschor Having the automatic load of Safes when your owner is detected would be awesome too, I don’t know if there’s already a ticket for that