Basic amount of features (good enough for our needs)
We already use this in testing frameworks
User stages from UI:
To make user flow closer to existing flows in web2.0 we want to move away from multiple stages of web3.0 and present users with familiar login flow.
Current stages of user:
User without web3 support
User with web3 support but not logged in
User with web3 support but not connected to proper network
User with web3 support and logged in
New stages of user:
Not logged in
To backup seed phrase from burner wallet we can notify user after he finishes action/gets something of value to wallet.
In current integration we have loading script that loads default web3 without wallet and then upgrades to web3 with Metamask wallet if available
In branch (https://github.com/oceanprotocol/commons/tree/feature/wallets) is upgraded integration where loading script loads default web3 and after that user can then select BurnerWallet or Metamask to login. Web3 with loaded wallet is then used for Ocean. Logging Metamask example Logging with Burner wallet example
Current loading script can be replaced by https://github.com/NoahZinsmeister/web3-react package which does exactly the same and has support for more wallets (trezor, ledger). Replacing loading system would require some refactoring. This package is already updated to latest Web3 version we would have to bump versions on squid-js. Prototype create-reac-tapp burnerwallet2.zip