Method to change the chain of the wallet

[pradel]

Is your feature request related to a problem? Please describe.
If you have a Stacks application on testnet / mainnet, signing a message depends on the current chain selected in the wallet. Let's say your wallet is on "mainnet" and your testnet app is requesting a message signature, the wallet (both leather and xverse) will show an error saying that the selected chain ID is not the one requested for the signature.
To fix that problem, there should be a method so that the client can request to change the selected chain in the wallet (which can be subject to user approval) similar to how it's done on Ethereum.

Describe the solution you'd like
The SDK should have a function to request a chain ID to be changed.

[kyranjamie]

Leather persists the network selected during connection/getAddresses and uses that network as default.

Should an app have permissions to call actions on multiple chains at any given time?

[pradel]

If the user allowed the app to switch the chain beforehand, imo it should be possible to call any chain for any action (but the app must request the chain change first so the user is aware of which network the action is called).

[kyranjamie]

Thanks @pradel, think we're on the same page, but to clarify below. If the latter option is the case, then changing network is effectively re-authing with getAddresses.

Scenario: User connects with no argument (uses default of mainnet). Then, app requests to change network to testnet.

Behaviour:

1. ^🎉 App can now make requests to both mainnet and testnet.
2. ^🚀 App can only make requests to testnet.

I'm in the camp that 2 should be the case, but if community pushes for more flexibility of option 1, then I'd like to know asap since this impacts our permission system.

[pradel]

Option 2 is good from a developer perspective I think (if later on subnets or smth similar is introduced, an app might be able to request multiple chainId but might not be necessary now).

then changing network is effectively re-authing with getAddresses

For this request I am talking about my experience in developing apps in the EVM ecosystem (L1, L2s, testnets). The wallet have a method so that an app can request to change the current chainId see https://wagmi.sh/core/api/actions/switchChain#chainid.
Then all methods called after can be done on the new chainId (this prompts the user to accept the chain change in the wallet).
I guess the behavior is different here as on EVM the address is the same for mainnet/testnet which makes things simpler as there is no need to request the new address corresponding to the network.