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
When forking a chain and serving it, ideally it would possible to configure an overridden Common such that the chain ID is different.
This is useful because a same chain ID will confuse legacy wallets like Metamask, where they will insist that a chain returning chain ID X be added as an alternative RPC to an entry already using that chain ID, rather than allowing you to add a new chain with the same ID but different RPC.
This is a problem because interacting with the fork will change the nonce and force the user to have to clear the activity of an address when going back to interact with the "real" chain that was previously forked.
The text was updated successfully, but these errors were encountered:
When forking a chain and serving it, ideally it would possible to configure an overridden Common such that the chain ID is different.
This is useful because a same chain ID will confuse legacy wallets like Metamask, where they will insist that a chain returning chain ID X be added as an alternative RPC to an entry already using that chain ID, rather than allowing you to add a new chain with the same ID but different RPC.
This is a problem because interacting with the fork will change the nonce and force the user to have to clear the activity of an address when going back to interact with the "real" chain that was previously forked.
The text was updated successfully, but these errors were encountered: