Metamask-extension: Detect when TestRPC changes & restart provider

Created on 15 Oct 2017 · 8Comments · Source: MetaMask/metamask-extension

Here at EthWaterloo, I just saw a pair of hackers get stuck to the point of desperation because:

They were getting wrong nonce errors
They couldn't track the tokens they had published.

Both of those problems were actually related to restarting their TestRPC server, and MetaMask now being in a "wrong" state.

We could solve this by doing some kind of provider detection, for when the provider server (even if just localhost:8545) suddenly changes to a different blockchain. This could be as simple as periodically (every 5 minutes) checking if the genesis block has the same hash. Or recognizing if an old block no longer exists. I don't know, this issue is for solving the problem, let the solution PR have the solution.

L23-devMode T01-enhancement

Source

danfinlay

👍7

Most helpful comment

I think this would be a great idea. It doesn't need to be an automatic/periodic check or anything; there could be a button somewhere that says "Reset network" or "Forget history" or something. Right now the only solution I've found is to uninstall/reinstall the extension.

I don't know how feasible any of this would be, but it would be appreciated!

bmmpxf on 21 Nov 2017

👍2

All 8 comments

I have this problem when using truffle develop testrpc. and it doesn't resolve when I switch network on metamask. I think this is probably a truffle issue though. it works fine with any other network, including with just running testrpc from node_modules manually at port 8545