Why am I getting different chains when sending a contract call to different wallets

Moralis General
#1

IMG-20220807-WA0005
IMG-20220807-WA0005486×1080 19.9 KB

IMG-20220807-WA0004
IMG-20220807-WA0004486×1080 21.9 KB

Please what could be causing it?

#2

What do you mean with different chains? What do you do?

#3

I was expecting to be charged in eth cuz I sent out a usdt contract call, but trust wallet is charging bnb same has infinity wallet but metamask charges eth from the call, please why?

#4

You could try it first on desktop with MetaMask. If you are using walletconnect then you have to specify the chain at connection time

#5

Please how can I specify the chain at connection time?

#6

there is a chain id parameter to enableWeb3 or for authenticate

#7

I added that already, chainId: 56

#8

But where I’m having trouble is on my contract call button, not signing in

#9

You need to change the active chain in the wallet to the one you want (Ethereum or BSC). The default chainId set in your WalletConnect authenticate won’t actually change the wallet in say MetaMask, the user has to do this.

#10

So sorry for the late reply,I have tried changing it in trust wallet, but it’s still showing bnb… please do you know how I could change the chain on trust wallet?