You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an app with two chains: Sepolia and Base Sepolia, and I’ve deployed a contract to both chains. I can interact with the contract on both chains through my MetaMask wallet. I also added support for using a burner wallet, but it isn’t working for Base Sepolia. Here’s the error message I’m encountering:
The current chain of the connector (id: 11155111) does not match the connection's chain (id: 84532).
Current Chain ID: 11155111
Expected Chain ID: 84532
Version: @wagmi/core@2.15.2
If I only include Base Sepolia in the targetNetworks, the functionality works as expected. The issue seems to be with supporting both chains simultaneously when using burner wallets.
Expected Behavior
I expect the burner wallet to work on both chains, but please let me know if this behavior is expected.
Is there an existing issue for this?
Which method was used to setup Scaffold-ETH 2 ?
npx create-eth@latest
Current Behavior
I have an app with two chains: Sepolia and Base Sepolia, and I’ve deployed a contract to both chains. I can interact with the contract on both chains through my MetaMask wallet. I also added support for using a burner wallet, but it isn’t working for Base Sepolia. Here’s the error message I’m encountering:
If I only include Base Sepolia in the targetNetworks, the functionality works as expected. The issue seems to be with supporting both chains simultaneously when using burner wallets.
Expected Behavior
I expect the burner wallet to work on both chains, but please let me know if this behavior is expected.
Steps To Reproduce
Here is the repo: https://github.com/AzimovS/test-two-chains-with-burnerwallet
Anything else?
No response
The text was updated successfully, but these errors were encountered: