Skip to content

Support injected web3 provider (e.g. MetaMask or Status) #5

Description

@Mischi

The Asure dApp comes with an integrated wallet. This makes it independent of external wallets such as MetaMask or Status and can also be used standalone in mobile browsers.

As a user of the Asure dApp and external wallets like MetaMask or Status, I would like to have the possibility to use the external wallet and to be able to do without the integrated Asure Wallet.

Implemenetation

When starting the Asure dApp it should be checked if an external Web3 provider is available (window.web3.currentProvider !== null). If it is, a new selection option should be created on the login screen. The user should be able to choose between internal or external wallet (e.g. window.web3.currentProvider AsureHdWalletProvider). The selection is then to be persisted in the Redux store.

Acceptance criteria

  • If window.web3.currentProvider is available, the user should be able to make a corresponding selection on the login screen.
  • The selection is stored in the Redux store for the duration of a user session and the window.web3.currentProvider is initialized with the AsureHdWalletProvider if the user has chosen the Asure dApp Wallet.
  • The current selection can be viewed in the settings.
  • All actions of Asure dApp work with MetaMask

How to start?

Your can find the dApp sources in packages/dapp

You could start by looking at the following files:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions