signEngine.metadata is final, but I want unique redirects for each Sign session.

[bobwith2bees]

What I am trying to do:

Have my Dapp allow the user to connect to multiple wallets. I will have a tab in the UI for each wallet so the user can manage them separately as needed. When I sent a transaction to a specific wallet Sign session , I want the redirect URI to be unique so that my app hand handle the deep link and open the corresponding tab in the UI for that wallet.

I see the pairingInfo is marked final, and it managed at the Core level and not the Session level. I was hoping I could re-use the Web3App instance, just update the paringInfo metatdata for the redirect before each new Sign Session. There is no need to change the redirect once the Sign session has been established.

Protocol wise - I don't see the need to have a Web3 / Core instance per wallet (what the code can do today.) Looking for thoughts/guidance?

Priority - Low (for me) - Again I am just writing a class and this would have been nice to show off the capabilities. (Also assumes wallets actually pay attention to the peerMetadata redirect :-p)