Closed chinitadelrey closed 3 years ago
This might be something that @limonadev has fixed? Or maybe he broke it?
@schancel This is the line that is probably causing the issue, but I think it's correct, the wifKey
should have 32 bytes or 64 hex characters. Before my PR, it only was converted to base58 and the result could have less hex characters. That's what I fixed.
This error was caused by a bug in the electrum client regarding the responses to pings. Unrelated to key encodings.
Have gotten this error multiple times over the last week and in the new build... the issue seems to be in the encoding/decoding ? of the private key from file.
Copying and pasting the same phrase from save seed into import seed would remove this error.
But afterwards we get another issue with the jsonrpc requests, #104.
Notice the private key starts with a 2 not a K or L, which is what I think is breaking it:
full trace: