Append requisite 0x on private key entry from MEW format

[cryptolarity]

When generating an ETH private key from MEW it omits the '0x' and results in generating a different public address when inputting into the 'Send tx' portion of the GO wallet.

[jmank88]

This is likely as simple as checking for the 0x prefix before trimming the first two chars. These screenshots demonstrate that replacing the first chars yields the same account, so it seems like those first two chars are being trimmed no matter what they are. We should probably validate the length of the key too (are they fixed?), and the characters themselves. It accepts all sorts of random stuff, like just 0x12 for example: Or random non-hex chars:

[ralyodio]

What needs to be done on the UI here? Do I just search for 0x and remove it? or do I add it if its not there?

[treeder]

We want to make sure:

• they have the 0x in front, and if not, either error or add it automatically (and update the actual form field)
• check that it's a valid key. Not sure if there's a method in web3 that verifies it? More info here: https://ethereum.stackexchange.com/questions/1771/how-to-validate-a-private-key

[treeder]

Where is this one at?

[ralyodio]

I haven't started on this one yet.

[ralyodio]

I'm looking into this one now.