ElectrumSV 1.3.0b3-multisig

This is a cut-down release of ElectrumSV, with additional bug fixes, that allows people to switch their existing P2SH multi-signature wallets over to “bare” multi-signature, allowing them to continue receiving and spending coins in those wallets.

Image for post
Image for post
The splash screen for ElectrumSV 1.3.0b3.

Readers unfamiliar with these releases, should first read the article about the original ElectrumSV 1.3.0b1-multisig release. That article will help them both understand why this release is being made, and how to make use of it.

Again, this is a cut-down release. It lacks UI support for several things, and requires more polishing before a formal full release can be made. While it does allow you to try out some changes we have made, it is only intended to allow users of existing multi-signature wallets in ElectrumSV 1.2.5 to import and continue using them.

Bug fixes in 1.3.0b3

Non multi-signature polish

While these releases are not intended for people to create new wallets with, some people do, and kindly report the errors they encounter. This has resulted in some fixes to a few things that were a bit further along the roadmap, in order to stop these things from being reported any more! Thanks to our kind users who vigilantly submit bugs through the automated error reporter.

Lowered default transaction fee to 500 satoshis/kB

Users of other wallets are paying 500 satoshis/kB, which is half the old ElectrumSV default fee of 1000 satoshis/kB. These lower fee transactions still get mined, so I think there’s a good argument that ElectrumSV users should be paying that fee too. Read a short article about it.

Image for post
Image for post
No custom fee rate means the wallet is paying the default fee rate.

Fixed fee calculation when not paying to an address

When creating a transaction, the change from the spent coins is distributed between a variable range of change outputs. How many change outputs affects the cost of making the transaction in terms of fee, due to the eventual size of the transaction.

Previously our fee calculation in this area hard-coded an output size of 34 bytes, which is the standard pay to address output size. This meant that transactions with change outputs that are not paying to an address would have an incorrect and lower fee.

The only output type we currently use that does not pay to an address, is bare multi-signature. But as we now generate the output and use it’s direct final size, all future output types should be factored in resulting in correct fees.

Automatic error reporting

The system used to give users the option to report errors they encounter as bugs on Github, was broken in some circumstances. This has been fixed and all such errors are now able to be reported.

Image for post
Image for post
Oops, an error has occurred. Please consider reporting it.

Block explorers and address-less payments

Now that the Genesis upgrade has removed the false limit that transactions must be “standard”, there is no guarantee that a payment will be made to an address. WhatsOnChain and satoshi.io have added support for viewing transactions that use specific scripts, which allows these address-less payments to be viewed.

This is generally a feature that more advanced users will make use of, as the Keys tab is not really meant for regular users.

Image for post
Image for post
Viewing the use of a wallet’s key on a block explorer.

Long-standing errors for proxy users

I don’t use a proxy, but some people do, and they encountered errors going all the way back to ElectrumSV 1.2.1. These errors were related to trying to edit their proxy settings after they had configured and saved those settings already, enabling the use of a proxy. Reported by much appreciated error reporter users.

Image for post
Image for post
A networking feature you and I likely never use.

A new REST-based API

The old JSON-RPC API has been removed and replaced with a new asynchronous REST-based API. This provides a much more stable, responsive base for our future APIs. An example application is provided to show people how they can run their own wallet application based on ElectrumSV. Developed by Kiwi AustEcon.

Bug fixes in 1.3.0b2

Change and privacy

When making a transaction the selection logic which decides which coins to spend would combine all the available coins into one. This is not ideal from a privacy perspective, and the fix restores the behaviour to how it has historically worked — Fix provided by Kiwi AustEcon.


Web site and downloads

Official ElectrumSV web site: electrumsv.io
Official ElectrumSV web site downloads: electrumsv.io/download.html


If you need some assistance with something, please submit an issue at the following link. But please, fill out a template otherwise we will not have the information we need and you will have to wait longer for assistance.

Report an issue: github.com/electrumsv/electrumsv/issues

We do not provide support over Twitter, and will request you submit an issue. Support over twitter is much more difficult, and we prefer to avoid it completely.


You can reach us for discussion in one of two possible locations.

Written by

ElectrumSV developer

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store