Configuring WalletConnect Ethereum Provider optional chains

[r3lays]

In the Wagmi documentation, it's mentioned that they wrap the WalletConnect Ethereum Provider. However, there's a lack of details on how to configure the options for this provider, particularly regarding the optionalChains and optionalNamespaces configurations.

Are we understanding this correctly? For our use case we must specify all of our chains as optional for WalletConnect because some wallets only work for specific chains and if a chainId is passed and the session is initialized, the wallet wont properly connect.

[glitch-txs]

Currently the WalletConnect connector requires at least one required chain, you can try to workaround it by passing the chainId to the connect function. currently some wallets won't support empty required namespaces, we'll update the connector once they do. Alternatively you can copy paste the connector on a ts file and modify it for the moment

[ElvisKrop]

Actually, you are a bit wrong. This is a comment from wallet connect repo about chains and optional chains - https://github.com/WalletConnect/walletconnect-monorepo/blob/v2.0/providers/ethereum-provider/src/EthereumProvider.ts#L190-L194
One of these arguments can be undefined. I have created an issue(#469) and opened a PR (#470) to fix this behaviour.

[ElvisKrop]

oh, you are talking about wagmi. yes, it requires at least one chain for initialization
Hopefully, my PR will be soon reviewed to improve this connector

[glitch-txs]

the PR looks good, also check that to the connect function is passed some chain params too so there might be need of some changes in that part as well. We're currently waiting for some wallets to support empty required namespaces (some of them currently break with this config).