fixed here:
https://github.com/spesmilo/electrum/commit/5514d3bd74ab079beb0293d527e08dffd3105729
Topic: Bug Report: Private key not Yielding Correct Public Key (Read 617 times)
thanks for the report. it looks like a recent regression in git master.
1.8.x versions are not affected.
1.8.x versions are not affected.
This is a bug in the development version 1.9. It may, or may not be, a problem with the current release version.
Here's a private key that I'll no longer use:
5JN4PgPLhRskjUDhytEJ8tTDsUKJ9bBuEWwhdCSGFGhXbx6ofPt
In every other wallet, it will generate this public key hash:
1BbJHQStkpMcoqJ3ysZRV6HNpe3bGooiUK
In Electrum, it generates this public key hash:
1P2knF5HfFyYcdCrqxd2Ur3Z1UeGTv2dXx
This is not an isolated case. I saw this yesterday with another private key, but I want to keep that private key and do not want to disclose it. I did, however, test a specific case:
1) I ran 'importprivkey('')' from the command line of the Electrum Wallet.
2) I noticed that the public key hash was incorrect.
3) I sent funds to the incorrect public key.
4) I then tried to use the public key in the Electrum wallet by setting it to 'Prioritize', and then using it to send funds. The transaction failed completely with an error. I am not sure, but I believe the error was 'None Type', or something similar.
Here's a private key that I'll no longer use:
5JN4PgPLhRskjUDhytEJ8tTDsUKJ9bBuEWwhdCSGFGhXbx6ofPt
In every other wallet, it will generate this public key hash:
1BbJHQStkpMcoqJ3ysZRV6HNpe3bGooiUK
In Electrum, it generates this public key hash:
1P2knF5HfFyYcdCrqxd2Ur3Z1UeGTv2dXx
This is not an isolated case. I saw this yesterday with another private key, but I want to keep that private key and do not want to disclose it. I did, however, test a specific case:
1) I ran 'importprivkey('
2) I noticed that the public key hash was incorrect.
3) I sent funds to the incorrect public key.
4) I then tried to use the public key in the Electrum wallet by setting it to 'Prioritize', and then using it to send funds. The transaction failed completely with an error. I am not sure, but I believe the error was 'None Type', or something similar.
Jump to: