The downloads are linked at the end of this entry. If you are unsure which file to download, read the handy "Which download?" section.

Release notes

• This is released to deal with the broken server issues.
• Various packages ElectrumSV depends on may have been updated, but this was not the intention of the release and was unfortunately unavoidable.

Which download?

WARNING: It is recommended you use ElectrumSV 1.3.16 unless you are having server connection problems. The Windows releases should be signed and not require clicking through warnings when running them, but the MacOS release is unsigned and cannot be run without assistance.

• MacOS:
  • You want the .dmg file.
• Windows:
  • Most users want the .exe file. This stores new wallet files and data in your user directory, and will look there for existing wallet files.
  • The -portable.exe is mostly used by advanced users. This stores new wallet files and data in the same directory as the downloaded executable, so it is up to the user to keep track of them and be aware of this.

The downloads are linked at the end of this entry. If you are unsure which file to download, read the handy "Which download?" section just above the links.

Release notes

• Release guide: https://electrumsv.io/articles/2023/electrumsv-1_3_16.html
• Security: Due to the packages we depend on, we bundle the root certificates that are used
  to verify that when we connect to a web site it is the legitimate web site. One of these
  certificates was revoked, and we need to do a release to provide a version of the wallet
  that does not contain that revoked certificate. The version of the certifi package we
  include has been updated.
• User interface: There seems to be a bug where restoring a wallet would leave the history
  tab list of transactions not correctly updated. Specifically, the dates would still show
  "Unknown" despite the transaction having been verified as in a block with the merkle proof.
  It should have been updated with the date of the block. A workaround was added to force
  an update, but the whole model seems to need a rewrite however the current focus is on the
  1.4 release.
• User friendliness: We do not include all the past blockchain headers with the wallet, and
  before the wallet can work properly it used to download all the headers. Nowadays we have
  built-in checkpointing so that we can fetch the headers we need on demand, and not require
  that long startup time. In order to make this release more user-friendly, we have updated
  the mainnet and testnet header checkpoints.
• Reliability: There is an occasional bug where the file headers are stored in does not get
  written correctly. This mainly happens on Windows, but has been observed on Linux. We have
  included a fix that flushes and closes the file storage on exit, and should hopefully fix
  this rare but continuing problem.
• Documentation: The documentation covering how to verify your download with our PGP signatures
  referred to a different file suffix ".sig" for the file signatures rather than ".asc" which
  the tooling appears to have switched to, causing user confusion. This has now been aligned
  with the tooling, and uses ".asc".
• Exchange rates: Removed Bitfinex as source of exchange rates.
• Servers: Updated the hard-coded servers list. There were a lot of stale servers that no longer
  exist. satoshi.vision.cash appears to be pruned and does not have the transactions for wallet
  restoration.
• Python: Update build version of Python to 3.9.16. On MacOS we had to upgrade to 3.9.16 for
  builds to ensure that we include the latest fixes that allow builds made on later versions of
  MacOS (13.3+) to run on earlier versions (11.1+). Most users should be running a build, so
  this should only affect those running from source. However the last version of 3.9 suitable
  for local development on Windows due to installers being available is 3.9.13, so this is the
  enforced minimum version.

Which download?

• MacOS:
  • You want the .dmg file.
• Windows:
  • Most users want the .exe file. This stores new wallet files and data in your user directory, and will look there for existing wallet files.
  • The -portable.exe is mostly used by advanced users. This stores new wallet files and data in the same directory as the downloaded executable, so it is up to the user to keep track of them and be aware of this.

This release formally fixes an exploit we inherited from Electrum Core where the user copies a URL to pay to. It is advised you update to this release, we do not guaranteed support for previous releases. Download our applications from https://electrumsv.io, it is your responsibility to check that you are getting a legitimate download and not malware. Please verify your download for MacOS and Windows. Linux users are expected to be able to work this out for themselves.

Post-release Github releases entry.

Post-release Github releases entry.

• Release guide: https://roger-taylor.medium.com/electrumsv-1-3-11-6f09f2aaed94
• Ledger hardware devices: The latest Ledger software has been updated in a way that is not
  backwards compatible. This means that anyone who updates their device needs to get the changes
  in this release that update ElectrumSV to work with these latest Ledger updates.
• Hardware wallet accounts: The derivation path is now visible in the account information
  dialog.
• Account-less: Loading transactions in a wallet with no accounts no longer errors due to an
  unnecessary dependency on accounts in this functionality.
• Invoices: Importing invoices into an account would error displaying the open file dialog.

• Release guide: https://roger-taylor.medium.com/electrumsv-1-3-10-f0a60d031d81
• Trezor passphrases: Support for Trezor passphrase entry, which applies to all
  devices that have the passphrase setting enabled, was broken in 1.3.8.
• Trezor on device passphrase entry: The Trezor Model T device allows on device passphrase entry.
  Now ElectrumSV supports users opting to use this instead of entering the passphrase in
  ElectrumSV.
• Trezor/Keepkey passphrase confirmation: When creating an account for a Trezor
  or Keepkey hardware wallet, now it shows the proper confirmation dialog for
  passphrase entry, rather than the simple entry dialog.
• Coin-splitting UI: When a wallet was loaded and the window opened, where the user had hidden
  the coin-splitting tab, text would leak from the hidden tab and be shown over the "Add Account"
  button.

• Release guide: https://roger-taylor.medium.com/electrumsv-1-3-9-50c39bc7ef68
• MacOS compatibility: When used in conjunction, both PyQt5 and PyInstaller which are used to
  provide our user interface and builds respectively, do not work on MacOS Big Sur. This is
  something to do with versions of PyQt5 later than 5.13.1, and so we have rolled back our
  required version of PyQt5 to 5.13.1.
• Transaction export: The copy and save options in the transaction dialog, have been fixed and
  extended. There are now different options for both incomplete transactions and fully signed
  transactions, allowing export of transaction byte data, hex, and hex with proof data. At this
  time proof data is limited to parent transactions.
• Waiting dialog: This UI element shown when doing actions that may take some time, has been
  extended to optionally show a progress bar and remain open after the task has been completed
  for a given number of seconds unless the user manually dismisses it. This is used for
  transaction broadcast, transaction signing and copy/saving transactions with proof.

• Release guide: https://roger-taylor.medium.com/electrumsv-1-3-8-e07700fb9058
• Account script types: It is no longer possible to change the script type for an
  account, and only the safe default script type is usable for each kind of account.
  This prevents adventurous users from enabling advanced options.
• Trezor firmware: It should now be possible to sign transactions if a hardware wallet
  has been updated to the latest Trezor firmware. Trezor do not support Bitcoin SV,
  but we still want our users to be able to easily use them if they are already.
• Linux databases: There are limits built into our database solution SQLite that differ depending
  on the platform the database is running on. On Linux these are significantly higher, and the
  different database limits conflict with each other and caused errors when viewing transactions
  that spend more than 1000 coins. All limits has been hard-limited to 1000 for now to prevent
  this.
• Transactions tab: Due to the ordering of event processing, transactions that had been
  dispatched (broadcast to the network) might remain in the Transactions tab when they should
  not. Now ordering is correctly observed, and if they should be removed, they will be removed.
• QR codes: In some obscure situations QR code scanning was erroring, and would cause exceptions.

• Release guide: https://medium.com/@roger.taylor/electrumsv-1-3-7-8b3833343bd3
• Payment dangers: The place where users enter where their payment goes to allows
  freeform entry of Bitcoin script assembly language. There was the possibility that
  users could paste in malformed addresses and have their payment go to an unexpected
  location. This should now be prevented.
• Transaction dialog: Some small interactive changes have been made to the
  transaction dialog. This allows a user to more easily inspect their wallet data
  and relate what coins were spent in one transaction to those received in another.
• REST API: The example REST API has received some changes and extensions to
  hopefully help those who want to use ElectrumSV as an automated wallet
  do so.