Electrum 1.9 released

[Mitchell]

Why would I need a reason to say hi? Hi! See, that is a "hi" without a reason
Well, not really, because you made me say hi, but mark my words, I will say "hi" in this topic without a reason!

[Daily Anarchist]

Is version 1.9 going to make it into debian 8 stable? Or is it stuck at 1.8?

[Gryph]

Can't seem to get offline transactions to work.

I create the transaction in the online computer using a watch-only wallet made with the public master key, transfer the transaction input file to a USB key, connect it to my offline computer and load it into the real wallet there made from the seed. The window that pops up says the Status is unsigned and that the transaction is unrelated to my wallet. It also displays (correctly) the inputs and outputs. I click Sign and enter my password. but nothing seems to happen, it sends me back to the transaction window. I save the file to the USB key but its identical to the input file, the transaction wasn't signed.

I'm using electrum 1.9.5 portable on both computers

[btcven]

Can't seem to get offline transactions to work.

I create the transaction in the online computer using a watch-only wallet made with the public master key, transfer the transaction input file to a USB key, connect it to my offline computer and load it into the real wallet there made from the seed. The window that pops up says the Status is unsigned and that the transaction is unrelated to my wallet. It also displays (correctly) the inputs and outputs. I click Sign and enter my password. but nothing seems to happen, it sends me back to the transaction window. I save the file to the USB key but its identical to the input file, the transaction wasn't signed.

I'm using electrum 1.9.5 portable on both computers

This should be fixed in git head

https://github.com/spesmilo/electrum/commit/1004fbd8f89523facae934f9ee5885a66663fac2

https://github.com/spesmilo/electrum/commit/8b4410d86a9868a12a35c81e7be01659628e63c5

[SebastianJu]

When will version 1.9.6 portable come out? And will the save settings problem be fixed then?

[adamas]

I tried to make an offline tx using the 1.9.5 portable build with the on/offline wallet method. The deseed command (console) doesn't work!
Then I tried the recover the (watch only) wallet with the MPK method: Not possible to use a previously imported key, the imported address has disappeared.

Now I wonder: Is this only a portable build issue? Is the "deseed" command not working anymore?

[opentoe]

After I installed 1.9.5 all my receive addresses changed. How do I get my original receive addresses back?

Also, was that bug fixed when sending coin it wouldn't send and come back with some weird error? I posted this a while ago and will dig up the old post if needed.

UPDATE: this is not a bug. Stupidity on my part. I never clicked on the little tick mark that opened up my old/used addresses.

[ThomasV]

version 1.9.6 is released.

Changes:
 - During wallet creation, does not write seed to disk until it is encrypted.
 - Shows a confirmation dialog if the transaction fee is higher than 1mBTC.
 - fixes for various bugs reported recently.

Linux packages for now. Binaries for Win and Mac will follow.

[Mitchell]

- Shows a confirmation dialog if the transaction fee is higher than 1mBTC.

I see what you did there, haha. And hello! (I told you I would come back to say hi!)

[adamas]

version 1.9.6 is released.

 The "deseed" command still gives the message:

>> deseed
Traceback (most recent call last):
NameError: name 'deseed' is not defined

Changes:
 - During wallet creation, does not write seed to disk until it is encrypted.

  What does that mean in practice?

[ThomasV]

version 1.9.6 is released.

 The "deseed" command still gives the message:

>> deseed
Traceback (most recent call last):
NameError: name 'deseed' is not defined

"deseed" is not available in the python console. it is only available in the terminal.

Changes:
 - During wallet creation, does not write seed to disk until it is encrypted.

  What does that mean in practice?

it improves security. previous versions used to write the unencrypted seed first.
however, there is no guarantee that the encrypted wallet will be written on the same disk sector.

[adamas]

The "deseed" command still gives the message:

>> deseed
Traceback (most recent call last):
NameError: name 'deseed' is not defined

"deseed" is not available in the python console. it is only available in the terminal.

--> How do I use the deseed command with a windows build?

it improves security. previous versions used to write the unencrypted seed first.
however, there is no guarantee that the encrypted wallet will be written on the same disk sector.

Thanks.

[Abdussamad]

The "deseed" command still gives the message:

>> deseed
Traceback (most recent call last):
NameError: name 'deseed' is not defined

"deseed" is not available in the python console. it is only available in the terminal.

--> How do I use the deseed command with a windows build?

Use the command line of course.

http://windows.microsoft.com/en-us/windows-vista/open-a-command-prompt-window

Bring up the command prompt and run

electrum --help

for more information.

[adamas]

"deseed" is not available in the python console. it is only available in the terminal.

--> How do I use the deseed command with a windows build?

Use the command line of course.

Bring up the command prompt and run

electrum --help

for more information.

 Sorry, but it doesn't work that way!
 It would be nice if ThomasV could give a hint on this.

[ThomasV]

"deseed" is not available in the python console. it is only available in the terminal.

--> How do I use the deseed command with a windows build?

Use the command line of course.

Bring up the command prompt and run

electrum --help

for more information.

 Sorry, but it doesn't work that way!
 It would be nice if ThomasV could give a hint on this.

in a terminal:

Code:

electrum -w /path/to/your/wallet deseed

if you cannot use a terminal, use the 'restore' menu to create a watching only wallet

[adamas]

in a terminal:

Code:

electrum -w /path/to/your/wallet deseed

Terminal:
  electrum -w /electrum_data/wallets/default_wallet - starts the client!
  electrum -w /electrum_data/wallets/default_wallet deseed - nothing!

  It seems that the "deseed" command isn't working.

Note: The 1.7.4 build works fine (deseed!)

[prof7bit]

ThomasV, could you please have a quick look at this thread (its a bit old already, are you aware of this, is it fixed already or is it meant to be that way intentionally? What does the corresponding BIP say about it?)
https://bitcointalk.org/index.php?topic=329354.0

[btcven]

in a terminal:

Code:

electrum -w /path/to/your/wallet deseed

Terminal:
  electrum -w /electrum_data/wallets/default_wallet - starts the client!
  electrum -w /electrum_data/wallets/default_wallet deseed - nothing!

  It seems that the "deseed" command isn't working.

Note: The 1.7.4 build works fine (deseed!)

Working in 1.9.6

[supert]

1.9.6 mac fails to connect to network (red light in lower right) and nothing happens when network button or menu item is clicked/chosen. 1.9.4 works fine.

[btcven]

1.9.6 mac fails to connect to network (red light in lower right) and nothing happens when network button or menu item is clicked/chosen. 1.9.4 works fine.

OS version? <-- could this be mandatory on any comment?