ElectrumSV 1.3.10
This article covers the release of ElectrumSV 1.3.10, and some of the more important changes that have been made since ElectrumSV 1.3.9. Skip to the “What has changed in this release?” section to see what has changed, if that is what you are here for.
Do you need an introduction to how ElectrumSV works?
We have a selected range of guides to common tasks that our users may want to do in our documentation, please check it out.
Where can you download ElectrumSV?
The only safe downloads are available on: electrumsv.io
Where can you get help?
Find our issue tracker here where you can create a ticket. Fill out the issue template, please! Otherwise we have no idea what steps you took or any of the other details and then we have to spend time asking you them anyway and you get help much later. Fill out the template for your own sake, if not ours!
We do not provide support over Twitter or any other forms of social media. Not only is it not guaranteed we will see your comments, it is a very painful way to do support that we avoid. If you need support, submit an issue on our issue tracker. Or you can raise subjects of interest on Unwriter’s Slack, or the Metanet.ICU Slack.
If you are a MacOS user and cannot install/run our latest release, please read this article.
What has changed in this release?
The main changes in this release have been listed below. If you don’t want to know the details, just read the titles. If you want to find out about smaller fixes, you can check the release notes in the Github repository.
Trezor passphrase signing works again
The 1.3.8 release allowed Trezor hardware wallet owners to use Trezor’s latest firmware. However, in the latest Trezor firmware an API changed related to entering passphrases for your Trezor device. Specifically, the API now passed an extra flag into ElectrumSV which indicated if the device supported on device passphrase entry.
Passphrases are a hard to understand concept where you can extend the key securely stored in your hardware wallet device with some extra text. You specify this text every time you set up an account for the Trezor device in ElectrumSV. The theory is that this allows you to create secret stashes on demand for your hardware wallet, just by creating a new account and using a new passphrase.
Thanks to the many users whose names I do not remember who pointed out that this was not working any more.
Commits: #1
Trezor passphrase on device now supported
Normally when you enter your passphrase for your Trezor device you do it in ElectrumSV, which is of questionable security. But Trezor support an option to enter your passphrase using an old school mobile style keyboard (do people still use these?) on your Trezor Model T touch screen. I figured that while I was testing the passphrase code, I may as well implement support for this and test it at the same time.
The Trezor Model T (but not Trezor One) adds the extra shown “On Device” option, and when it is clicked the Trezor device then asks for the passphrase as shown below.
Commits: #1
Keepkey and Trezor passphrase confirming uses the correct dialog again
When you create a hardware wallet account, and your device is configured to use passphrases, ElectrumSV would ask you for one on it’s behalf. But the problem was it would use the above shown “Enter the passphrase to unlock this wallet” dialog, rather than the confirmation dialog shown below. This change restores the use of the shown confirmation dialog, which helpfully shows a warning about forgetting the passphrase.
Remember that Trezor caches the passphrase, so you will not be able to use the Trezor device to sign different accounts until you’ve disconnected it and reconnected it to reset it.
Other fixes
- #569: If a user had hidden the coin-splitting tab, text from the coin-splitting tab would leak out and be displayed over the “Add Account” button. This only happened on a fresh wallet load with the tab hidden.
What changed before this release?
You can read more details about previous bug fixes and changes, starting from the following article.
