non-hex keys about send-tokens HOT 4 CLOSED

It seems in my case the key was already Hex-encoded 32-byte, and simply ommitted the "0x" characters at the beginning. In that case, it could be helpful to the user to automatically prepend the "0x" under the condition that it's 64 characters long and only uses characters 0-9 a-f. But this could be dangerous if there is a possibility that a key is not hex-encoded and just so happens to be in the right format to look like it is. I don't know much about etherium private keys, so I don't know if this "dangerous" scenario would happen or not.

from send-tokens.

So this leads to the question of whether we need to worry about non-32-byte keys. Do etherium private keys that are, for example, 64 bytes instead of 32 bytes exist?

from send-tokens.

Yeah, it's usually not a good idea to be too permissive in crypto as you really want the user to be very conscious of what they're doing.

If I may make a suggestion, and if you haven't done so already, you might consider displaying an "ethereum blockie" image for address fields as a visual check.

Private keys are always 32 bytes. Anything more or less shouldn't work.

from send-tokens.

Okay, that makes sense. Yes, I'll try to add in blockies. I'll try out

https://github.com/ethereum/blockies

unless you have one to recommend

from send-tokens.