Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Custom RPC return wrong chainId.

See original GitHub issue

Trying to connect to custom RPC returns wrong chainId. I am calling the following method:

const provider = new WalletConnectProvider({
      bridge,
      qrcode,
      infuraId,
      rpc,
      chainId,
      qrcodeModalOptions
    });

with params:

bridge: "https://bridge.walletconnect.org"
chainId: 43113
infuraId: "INFURA_ID"
qrcode: true
qrcodeModalOptions: undefined
rpc: {43113: "https://api.avax-test.network/ext/bc/C/rpc"}

and the returned chainId in the provider is 1 (Mainnet). Any suggestions how to connect? This is not happening with other networks, just the Avalanche.

Issue Analytics

State:
Created 2 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

5reactions

avadexcommented, Jun 12, 2021

any news on this?

can confirm. happens on android wallet. with metamask, alphawallet, tokenpocket

2reactions

ochikovcommented, Jul 1, 2021

Wallets always control the chainId. The RPC map only exists to route requests that are not for signing. Please prompt users to change the chain on their wallet

If they change it, again the chainId written in the provider is wrong and no kind of transactions can be made.