Topic: [ANNOUNCE] Electrum - Lightweight Bitcoin Client - page 71. (Read 274537 times)

There you go:


python electrum mktx -f 0.001 19mP9FKrXqL46Si58pHdhGKow88SUPy1V8 0.002
Password:
Traceback (most recent call last):
  File "electrum", line 416, in
    fee = options.tx_fee, change_addr = change_addr, from_addr = from_addr )
  File "%AppData%\Electrum-P\R049\C_\ElectrumPY\electrum\wallet.py", line 782, in mktx
    s_inputs = self.sign_inputs( inputs, outputs, password )
  File "%AppData%\Electrum-P\R049\C_\ElectrumPY\electrum\wallet.py", line 679, in sign_inputs
    private_key = ecdsa.SigningKey.from_string( self.get_private_key(addr, password), curve = SECP256k1 )
  File "%AppData%\Electrum-P\R049\C_\ElectrumPY\electrum\wallet.py", line 384, in get_private_key
    b = self.pw_decode( self.imported_keys[address], password )
  File "%AppData%\Electrum-P\R049\C_\ElectrumPY\electrum\wallet.py", line 698, in pw_decode
    d = DecodeAES(secret, s)
  File "%AppData%\Electrum-P\R049\C_\ElectrumPY\electrum\wallet.py", line 153, in
    DecodeAES = lambda secret, e: aes.decryptData(secret, base64.b64decode(e))
  File "%AppData%\Electrum-P\R049\C_\Python27\lib\base64.py", line 76, in b64decode
    raise TypeError(msg)
TypeError: Incorrect padding
None

FFLY_VM>

ok, use the command line, and generate the same transaction with mktx.
there will be a traceback. post it here.

Yes, I do have one imported key. In my tests, problems usually don't begin right after the import, more like a few hours (or transactions, not sure) afterwards.

are there imported keys in your wallet?
(I am asking this because you reported that the bug does not occur right after you regenerate the wallet)

Hi Thomas,
thanks for that new release.
Indeed, I am able to get a readable error message now.

(The test address in the below screenshot is the ECDSA node, copy-pasted)

I released a bugfix version, 0.49a
it should display the error message properly. let me know.

it is failing to display an error message.
this message might be caused by an invalid destination address, or an insufficient balance.
can you try to send to an invalid address and tell me if you get the same error?

Hi,

I've had the below issue several times the last few days, when trying to make a payment.
When I get this error, the payment doesn't go through.  Strangely, the only thing I have found
to be effective when this happens is rebuilding the wallet file! It doesn't seem to be related to
a specific release - I've tried the last 4 and all give me the same problem.

The only thing that has changed for me in the last few days is a slightly larger
wallet balance, but I'm not sure if this has anything to do with it. Any ideas?

Connected to ecdsa.org:50001
Traceback (most recent call last):
  File "%AppData%\Electrum-P\R048b\C_\ElectrumPY\lib\gui_qt.py", line 463, in do_send
    self.show_message(e.message)
  File "%AppData%\Electrum-P\R048b\C_\ElectrumPY\lib\gui_qt.py", line 828, in show_message
    QMessageBox.information(self, 'Message', msg, 'OK')
TypeError: arguments did not match any overloaded call:
  QMessageBox.information(QWidget, QString, QString, QMessageBox.StandardButtons
 buttons=QMessageBox.Ok, QMessageBox.StandardButton defaultButton=QMessageBox.No
Button): argument 3 has unexpected type 'Error'
  QMessageBox.information(QWidget, QString, QString, int, int button1=0, int button2=0): argument 3 has unexpected type 'Error'
  QMessageBox.information(QWidget, QString, QString, QString, QString button1Text=QString(), QString button2Text=QString(), int defaultButtonNumber=0, int escapeButtonNumber=-1): argument 3 has unexpected type 'Error'

this is because you restored with the -o option
it will create the addresses when you go online

Having trouble restoring a wallet.. it's not populating my addresses:

Ok, now that I know what pip is, I got it to work. Apparently the ecdsa part of the current electrum package is broken, but if I install it separately with pip then everything works.

Good to know, thanks.

WHEW!! also confirmed.  keys change when you reseed the .dat again.   

no, the keys that are displayed in that case are derived from the empty seed.
they are not the private keys of your wallet.
this is indeed a display bug; a deseeded wallet should not show keys at all.

confirmed.

How the heck is it doing that? I don't see anything in the .dat file that could be used to provide that information - unless it's coming from master_public_key... which would be bad.

"electrum deseed" followed by "electrum addresses -k" still displays secret keys.
Doesn't this mean that a deseeded wallet can still send bitcoins from the addresses it contains?
That kinda defeats the purpose of an offline wallet.

Hi,

Only mnemonic code is copied when clicking on "Copy to clipboard" button (inside seed window). Please add normal seed code too.

the 2 columns are just 2 ways to represent the same information.
if it has to be consistent with 'electrum seed', I guess it is better to change 'electrum seed' instead
For example, we could add an option to print the seed as hexadecimal, and the default would be mnemonic (or the reverse)


yes, I think it could be an option


but this is already how 'reseed' works: it appends '.seed' to the wallet name (whether specified with -w or default).
or did I miss something?


thanks for the donation, btw.

no idea.. how did that happen?

no, there is no simpler way.
of course, you lose the benefit of a deterministic wallet if you import keys.