Using both the dApp and wallet components in an app

[rkreutzer]

I am developing an app that currently uses the v1 web3-provider component to connect a user's web3 wallet to the app for creating a master encryption key, etc. I now want the app to be able to function as a wallet and scan a Sign-in With Ethereum (SIWE) QR Code and supply a newly generated eth address for each login request (to avoid correlation amongst the websites or back to the main eth address).

When I create a new WalletConnect object for the SIWE, the connector contains the original data. killSession doesn't appear to work for this, nor do I want to kill the main session. WalletConnect v2 seems like it will work better for this, but how would I support both v1 and v2 while many wallets and SIWE sites are using v1?

Thought and suggestions please. Has anyone implemented an app that is both a WalletConnect dApp and a wallet?

[rkreutzer]

My current thinking is to only use WalletConnect for the SIWE part, and use ethers to create or import an ethereum account for purposes of the master encryption key, etc.