This article depicts the differences between the Gnosis Safe and the legacy Gnosis Safe mobile apps. Both leverage the same Gnosis Safe smart contracts, however their feature set differs and they are not directly compatible.

Gnosis Safe

The Gnosis Safe is available as a desktop app and as a web application at It provides for full control and flexible setup since it is targeted at groups managing crypto assets collectively. Users are able to configure all settings flexibly such as the number of owners and the number of required signatures to authorize transactions ("threshold").

Owners can choose from a variety of owner wallets, including Metamask, Ledger, Trezor or any WalletConnect enabled wallet. Gas prices are set via the owner wallet which is also responsible for paying transactions fees.

The interface supports ETH, ERC20 and ERC721 tokens natively. Arbitrary smart contract calls can be made as well. Users are able to interact with 3rd party dapps via Safe Apps. These are native integrations of a variety of dapps directly inside the Gnosis Safe web interface.

The Gnosis Safe will be our focus moving forward. We release a compatible mobile app and deprecated the legacy Safe mobile app described below. If you are interested.

Legacy Gnosis Safe mobile apps

The legacy Gnosis Safe mobile apps are available on the respective mobile app stores (iOS, Android). They are targeted at individual users managing crypto assets.

Users can set up their Gnosis Safe seamlessly and connect an optional second authentication factor (2FA). If enabled, all transactions have to be signed by the 2FA device. At this point, the only supported 2FA option is the Status Keycard.

All transactions of the mobile app are executed via the Gnosis Safe relay service. Transaction fees can be paid in ETH or a set of defined ERC20 tokens, including DAI or OWL. The interface supports ETH and ERC20 tokens natively. It is possible to interact with 3rd party dapps via WalletConnect.

On a technical level, when setting up a Gnosis Safe via the mobile app, a Safe smart contract is deployed with 3 or 4 owner addresses, respectively.

  • 2 owner addresses are derived from the recovery phrase that you get when setting up your Safe.

  • 1 owner address belongs to the Safe mobile app.

  • 1 owner address belongs to the 2FA device (optional)

The threshold is set to 4 when adding a 2FA device and 3 in case you are using the Safe without a 2FA device. That means a user would either need their recovery phrase or their Safe mobile app (+ 2FA device if enabled) to authorize transactions.

The legacy Gnosis Safe mobile app only works with the setup described above and hence is not directly compatible with the Gnosis Safe interfaces described in the section before.

We are deprecated this mobile apps in favor of a new mobile app which will be fully compatible with the Gnosis Safe web interface described above. Hence the “legacy” prefix. Learn more about the new mobile app here.

In case you still would like to use the Gnosis Safe web interface with the legacy Gnosis Safe mobile app, check out this help center article.

If you want to migrate your Safe from the legacy mobile app to the Gnosis Safe web interface, please refer to our migration guide.

Did this answer your question?