Great work on the walletconnect integration. I am trying to make use of this over BSC and am unsure how to specify the chainId. Web3 works great on metamask as the chain is set in the wallet, but for a wallet like trust wallet it isn’t. I think therefore we need to have a way to specify the chain, either in the instantiation of the walletconnect web3 object or on subsequent contract calls.
At the moment if I connect using walletconnect it assumes at ethereum connection and eth as the platform token. I’m looking for someway to default this to BSC and have the signing flow match that required for BSC and its Amino implementation. (https://docs.binance.org/guides/concepts/walletconnect.html).