When upgrading from v3.0.6 to v3.1.1 to the desktop version there were no problems but when I upgraded the server I got some problems because I have some custom code in a separate file which updates the database with addresses and balances. Even though the Electrum upgrade went fine I had to downgrade and re-install v3.0.6. Once downgraded I executed the custom code and all is working properly to update the database again.
To clarify, the Electrum upgrades are great and work perfect from what I can see. I will continue to use v3.1.1 on my desktop and v3.0.6 on the server until I workout how to adjust my custom code to make it work alongside the upgrade.
Got to say Electrum is fantastic. The fact you can get a server running Electrum without the need to sync a massive blockchain makes life so much easier. Bitcoin but simplified. A special thanks go to Abdussamad for his advice and pointers in the run up to me downloading and testing it.
Topic: Electrum 3.1 is out! (Read 432 times)
Maybe better to stick with 3.0.6 for a few weeks or months which would allow for issues to be found and fixed in newer versions
If everyone did that no issues would be found and fixed!
Point taken. I will upgrade the desktop and server versions today.
Maybe better to stick with 3.0.6 for a few weeks or months which would allow for issues to be found and fixed in newer versions
If everyone did that no issues would be found and fixed!
Maybe better to stick with 3.0.6 for a few weeks or months which would allow for issues to be found and fixed in newer versions
Who could explain what the following means? Since nothing is supposed to leave the device in the first place.
It isn't that "nothing" leaves the hardware wallet... it's that PRIVATE KEYS never leave the hardware wallet...Quote
Watching-only wallets and hardware wallets can be encrypted.
When you use your HW (Trezor or Ledger Nano S etc) with Electrum, Electrum will read the "xpub" from the device and create a watching only wallet on your PC. Prior to this update, there was no way to password protect this wallet file (or ANY watching-only wallet). Thus anyone could copy your wallet file (or start Electrum on your PC) and, while they could not spend your coins, they could see the complete contents, addresses and transaction history etc.
Now, you can encrypt the entire wallet file on disk (like standard wallet files), so that it cannot be opened and viewed without the device connected. In my opinion, this is a handy feature!
Who could explain what the following means? Since nothing is supposed to leave the device in the first place.
It's probably about this:Quote
Watching-only wallets and hardware wallets can be encrypted.
"TREZOR wallets are stored in plaintext, with no option to encrypt. This means full public keys are exposed, along with address lists."
https://github.com/spesmilo/electrum/issues/2929
this version support new firmware of ledger nano?
i can' t open anymore electrum segwit with new firmware version 1.4 of ledger nano s
i can' t open anymore electrum segwit with new firmware version 1.4 of ledger nano s
Report the issue: github.com/spesmilo/electrum/issues/
this version support new firmware of ledger nano?
i can' t open anymore electrum segwit with new firmware version 1.4 of ledger nano s
i can' t open anymore electrum segwit with new firmware version 1.4 of ledger nano s
Who could explain what the following means? Since nothing is supposed to leave the device in the first place.
Quote
Watching-only wallets and hardware wallets can be encrypted.
OK, thank you very mutch
In the MAC Version i delete at first the old Version
and after i install the new Version, i hope thats right
In the MAC Version i delete at first the old Version
and after i install the new Version, i hope thats right
I have a MAC, is it recommended to update to 3.1.0.?
whenever there is a new version out, you can always go to the Release Note file on Electrum's github repository here: https://github.com/spesmilo/electrum/blob/master/RELEASE-NOTES and see what has been changed.
unless it is a serious buy/vulnerability fix (like 3.0.4 and 3.0.5) there is no rush in updating to the new version right away specially if you are not using Electrum to send bitcoin out every single day.
but remember that new versions are always improving the wallet software and most of them are fixing some small bugs which you may encounter if you stick to the older version still.
yes
I have a MAC, is it recommended to update to 3.1.0.?
The mempool fee estimation option is only available on certain servers. Try changing the server you are connected to.
I tried some different servers and still can't use the mempool fee estimation option.I'm told in #electrum that this is due to a bug which has been fixed in git master. The fix will be in the next release of electrum.
I tried this Portable electrum 3.1 latest version just now, but result fatal error in the first time and it creates a file with .pkg extension (I couldn't find the file where) but in the 2nd time I open it again and it works, but my kaspersky antivirus detected that this latest version is not safe. I know its false positive. However, safety must be first.
3.0.6 will be still the best version as of now for me. .
Why not stay with 3.0.6 version of electrum. and check if you can estimate the fee viewing your transaction before you hit send.
For me its working fine when checking the fee estimation by viewing the transaction before hitting send.
3.0.6 will be still the best version as of now for me. .
The mempool fee estimation option is only available on certain servers. Try changing the server you are connected to.
I tried some different servers and still can't use the mempool fee estimation option.For me its working fine when checking the fee estimation by viewing the transaction before hitting send.
Kaspersky is a malware from Russia Government and you shouldn't use that.
Btw use Linux instead of Windows for Bitcoins.
Remember what happened last few months about hacking electrum 3.0 that they can request RPC command to retrieve seed phrase or private keys.
I just wanted to keep my funds safe from time to time until they found suspicious in 3.0.6 version or if the 3.1 announced that its safe or until i found a good review then I'll be willing to upgrade to the latest version..
I tried this Portable electrum 3.1 latest version just now, but result fatal error in the first time and it creates a file with .pkg extension (I couldn't find the file where) but in the 2nd time I open it again and it works, but my kaspersky antivirus detected that this latest version is not safe. I know its false positive. However, safety must be first.
3.0.6 will be still the best version as of now for me. .
Why not stay with 3.0.6 version of electrum. and check if you can estimate the fee viewing your transaction before you hit send.
For me its working fine when checking the fee estimation by viewing the transaction before hitting send.
3.0.6 will be still the best version as of now for me. .
The mempool fee estimation option is only available on certain servers. Try changing the server you are connected to.
I tried some different servers and still can't use the mempool fee estimation option.For me its working fine when checking the fee estimation by viewing the transaction before hitting send.
Kaspersky is a malware from Russia Government and you shouldn't use that.
Btw use Linux instead of Windows for Bitcoins.
I tried this Portable electrum 3.1 latest version just now, but result fatal error in the first time and it creates a file with .pkg extension (I couldn't find the file where) but in the 2nd time I open it again and it works, but my kaspersky antivirus detected that this latest version is not safe. I know its false positive. However, safety must be first.
3.0.6 will be still the best version as of now for me. .
Why not stay with 3.0.6 version of electrum. and check if you can estimate the fee viewing your transaction before you hit send.
For me its working fine when checking the fee estimation by viewing the transaction before hitting send.
3.0.6 will be still the best version as of now for me. .
The mempool fee estimation option is only available on certain servers. Try changing the server you are connected to.
I tried some different servers and still can't use the mempool fee estimation option.For me its working fine when checking the fee estimation by viewing the transaction before hitting send.
The mempool fee estimation option is only available on certain servers. Try changing the server you are connected to.
I tried some different servers and still can't use the mempool fee estimation option.
The mempool fee estimation option is only available on certain servers. Try changing the server you are connected to.
Wow, awesome new update!
So much new stuff that would have made my life a lot easier had it come out a week ago, haha. Loving the QR code scanner for windows, sorting by column, being able to directly set sat/byte when sending, filtering, encrypting of offline and HW wallets... just wow!
Great job devs, thank you and please keep up the great work
So much new stuff that would have made my life a lot easier had it come out a week ago, haha. Loving the QR code scanner for windows, sorting by column, being able to directly set sat/byte when sending, filtering, encrypting of offline and HW wallets... just wow!
Great job devs, thank you and please keep up the great work
Looks like a great release, but I'll stick with 3.0.6 for now, in case there are some new vulnerabilities here, since it seems like a lot of things have changed, which means more surface for bugs.
I hope in the future Electrum will find a way to improve its privacy for users, since now it's probably the biggest issue, if fee estimations became accurate now.
I hope in the future Electrum will find a way to improve its privacy for users, since now it's probably the biggest issue, if fee estimations became accurate now.
Cannot use Memory-pool based fee estimation! I choose this option and close the settings window, after that I open the settings window again... and see ETA chosen instead of Memory-pool everytime! I cannot choose Memory-pool, Electrum doesn't remember my selection! My OS is Linux Debian 9.
Same with Linux here. 
Cannot use Memory-pool based fee estimation! I choose this option and close the settings window, after that I open the settings window again... and see ETA chosen instead of Memory-pool everytime! I cannot choose Memory-pool, Electrum doesn't remember my selection! My OS is Linux Debian 9.
Same with Windows7 using stand-alone executable. When Memory-pool is selected, it always return to ETA after opening the preferences.When the transaction fee estimation was set to Mempool, the scroll displays ETA?(1.0MB per tip).
When ETA was selected (from Static), the scroll displays Static (Within 5 Blocks).
Cannot use Memory-pool based fee estimation! I choose this option and close the settings window, after that I open the settings window again... and see ETA chosen instead of Memory-pool everytime! I cannot choose Memory-pool, Electrum doesn't remember my selection! My OS is Linux Debian 9.
Another great release from ThomasV, SomberNight and BauerJ: https://electrum.org/#download
Quote
# Release 3.1 - (March 5, 2018)
* Memory-pool based fee estimation. Dynamic fees can target a desired
depth in the memory pool. This feature is optional, and ETA-based
estimates from Bitcoin Core are still available. Note that miners
could exploit this feature, if they conspired and filled the memory
pool with expensive transactions that never get mined. However,
since the Electrum client already trusts an Electrum server with
fee estimates, activating this feature does not introduce any new
vulnerability. In addition, the client uses a hard threshold to
protect itself from servers sending excessive fee estimates. In
practice, ETA-based estimates have resulted in sticky fees, and
caused many users to overpay for transactions. Advanced users tend
to visit (and trust) websites that display memory-pool data in
order to set their fees.
* Capital gains: For each outgoing transaction, the difference
between the acquisition and liquidation prices of outgoing coins is
displayed in the wallet history. By default, historical exchange
rates are used to compute acquisition and liquidation prices. These
values can also be entered manually, in order to match the actual
price realized by the user. The order of liquidation of coins is
the natural order defined by the blockchain; this results in
capital gain values that are invariant to changes in the set of
addresses that are in the wallet. Any other ordering strategy (such
as FIFO, LIFO) would result in capital gain values that depend on
the presence of other addresses in the wallet.
* Local transactions: Transactions can be saved in the wallet without
being broadcast. The inputs of local transactions are considered as
spent, and their change outputs can be re-used in subsequent
transactions. This can be combined with cold storage, in order to
create several transactions before broadcasting them. Outgoing
transactions that have been removed from the memory pool are also
saved in the wallet, and can be broadcast again.
* Checkpoints: The initial download of a headers file was replaced
with hardcoded checkpoints. The wallet uses one checkpoint per
retargeting period. The headers for a retargeting period are
downloaded only if transactions need to be verified in this period.
* The 'privacy' and 'priority' coin selection policies have been
merged into one. Previously, the 'privacy' policy has been unusable
because it was was not prioritizing confirmed coins. The new policy
is similar to 'privacy', except that it de-prioritizes addresses
that have unconfirmed coins.
* The 'Send' tab of the Qt GUI displays how transaction fees are
computed from transaction size.
* The wallet history can be filtered by time interval.
* Replace-by-fee is enabled by default. Note that this might cause
some issues with wallets that do not display RBF transactions until
they are confirmed.
* Watching-only wallets and hardware wallets can be encrypted.
* Semi-automated crash reporting
* The SSL checkbox option was removed from the GUI.
* The Trezor T hardware wallet is now supported.
* BIP84: native segwit p2wpkh scripts for bip39 seeds and hardware
wallets can now be created when specifying a BIP84 derivation
path. This is usable with Trezor and Ledger.
* Windows: the binaries now include ZBar, and QR code scanning should work.
* The Wallet Import Format (WIF) for private keys that was extended in 3.0
is changed. Keys in the previous format can be imported, compatibility
is maintained. Newly exported keys will be serialized as
"script_type:original_wif_format_key".
* BIP32 master keys for testnet once again have different version bytes than
on mainnet. For the mainnet prefixes {x,y,Y,z,Z}|{pub,prv}, the
corresponding testnet prefixes are {t,u,U,v,V}|{pub,prv}.
More details and exact version bytes are specified at:
https://github.com/spesmilo/electrum-docs/blob/master/xpub_version_bytes.rst
Note that due to this change, testnet wallet files created with previous
versions of Electrum must be considered broken, and they need to be
recreated from seed words.
* A new version of the Electrum protocol is required by the client
(version 1.2). Servers using older versions of the protocol will
not be displayed in the GUI.
* Memory-pool based fee estimation. Dynamic fees can target a desired
depth in the memory pool. This feature is optional, and ETA-based
estimates from Bitcoin Core are still available. Note that miners
could exploit this feature, if they conspired and filled the memory
pool with expensive transactions that never get mined. However,
since the Electrum client already trusts an Electrum server with
fee estimates, activating this feature does not introduce any new
vulnerability. In addition, the client uses a hard threshold to
protect itself from servers sending excessive fee estimates. In
practice, ETA-based estimates have resulted in sticky fees, and
caused many users to overpay for transactions. Advanced users tend
to visit (and trust) websites that display memory-pool data in
order to set their fees.
* Capital gains: For each outgoing transaction, the difference
between the acquisition and liquidation prices of outgoing coins is
displayed in the wallet history. By default, historical exchange
rates are used to compute acquisition and liquidation prices. These
values can also be entered manually, in order to match the actual
price realized by the user. The order of liquidation of coins is
the natural order defined by the blockchain; this results in
capital gain values that are invariant to changes in the set of
addresses that are in the wallet. Any other ordering strategy (such
as FIFO, LIFO) would result in capital gain values that depend on
the presence of other addresses in the wallet.
* Local transactions: Transactions can be saved in the wallet without
being broadcast. The inputs of local transactions are considered as
spent, and their change outputs can be re-used in subsequent
transactions. This can be combined with cold storage, in order to
create several transactions before broadcasting them. Outgoing
transactions that have been removed from the memory pool are also
saved in the wallet, and can be broadcast again.
* Checkpoints: The initial download of a headers file was replaced
with hardcoded checkpoints. The wallet uses one checkpoint per
retargeting period. The headers for a retargeting period are
downloaded only if transactions need to be verified in this period.
* The 'privacy' and 'priority' coin selection policies have been
merged into one. Previously, the 'privacy' policy has been unusable
because it was was not prioritizing confirmed coins. The new policy
is similar to 'privacy', except that it de-prioritizes addresses
that have unconfirmed coins.
* The 'Send' tab of the Qt GUI displays how transaction fees are
computed from transaction size.
* The wallet history can be filtered by time interval.
* Replace-by-fee is enabled by default. Note that this might cause
some issues with wallets that do not display RBF transactions until
they are confirmed.
* Watching-only wallets and hardware wallets can be encrypted.
* Semi-automated crash reporting
* The SSL checkbox option was removed from the GUI.
* The Trezor T hardware wallet is now supported.
* BIP84: native segwit p2wpkh scripts for bip39 seeds and hardware
wallets can now be created when specifying a BIP84 derivation
path. This is usable with Trezor and Ledger.
* Windows: the binaries now include ZBar, and QR code scanning should work.
* The Wallet Import Format (WIF) for private keys that was extended in 3.0
is changed. Keys in the previous format can be imported, compatibility
is maintained. Newly exported keys will be serialized as
"script_type:original_wif_format_key".
* BIP32 master keys for testnet once again have different version bytes than
on mainnet. For the mainnet prefixes {x,y,Y,z,Z}|{pub,prv}, the
corresponding testnet prefixes are {t,u,U,v,V}|{pub,prv}.
More details and exact version bytes are specified at:
https://github.com/spesmilo/electrum-docs/blob/master/xpub_version_bytes.rst
Note that due to this change, testnet wallet files created with previous
versions of Electrum must be considered broken, and they need to be
recreated from seed words.
* A new version of the Electrum protocol is required by the client
(version 1.2). Servers using older versions of the protocol will
not be displayed in the GUI.
Jump to: