When Bitcoin Cash split from Bitcoin SV to become some strange variation on what Bitcoin used to be, we were left with a problem. Transactions made for either blockchain were valid for the other blockchain. This meant that if a user sent unsplit Bitcoin SV, it would also move the Bitcoin Cash to the same payment destinations. And vice versa, sending the Bitcoin Cash would send the Bitcoin SV.

This article is not intended for non-technical users. It is intended to define the current technical state of coin-splitting for my own reference, as of the date of writing. …


This article covers the release of ElectrumSV 1.3.11, and some of the more important changes that have been made since ElectrumSV 1.3.10. Skip to the “What has changed in this release?” section to see what has changed, if that is what you are here for.

We have a selected range of guides to common tasks that our users may want to do in our documentation, please check it out.

The only safe downloads are available on: electrumsv.io

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.


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.

We have a selected range of guides to common tasks that our users may want to do in our documentation, please check it out.

The only safe downloads are available on: electrumsv.io

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.


This article covers the release of ElectrumSV 1.3.9, and some of the more important changes that have been made since ElectrumSV 1.3.8. Skip to the “What has changed in this release?” section to see what has changed, if that is what you are here for.

We have a selected range of guides to common tasks that our users may want to do in our documentation, please check it out.

The only safe downloads are available on: electrumsv.io

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.


This article covers the release of ElectrumSV 1.3.8, and some of the more important changes that have been made since ElectrumSV 1.3.7. Skip to the “What has changed in this release?” section to see what has changed, if that is what you are here for.

We have a selected range of guides to common tasks that our users may want to do in our documentation, please check it out.

There is also a guide that illustrates some of the common uses of ElectrumSV. Especially if you are new to ElectrumSV, or coming from ElectrumSV 1.2.5 (or even earlier versions). …


A user has reported losing a lot of BSV because they changed the script type of their multi-signature wallet to “accumulator multi-signature”. Please stick with the default script types for all of your wallets unless you are willing to accept the risk.

There are a lot of ways to lose coins with ElectrumSV, it is an open source wallet and some call it the “swiss army knife” of wallets. Unfortunately, this means it is very possible to cut yourself.

Image for post
Image for post

Originally when we were preparing for the Genesis upgrade and the deprecation of P2SH payments, we needed to support other types of multi-signature. The code base underwent a large refactoring and part of this was preparing for the future by recording what keys were used with what script types. …


In the last day or so I changed how we do Trezor signing so that we provide the signing process with the transactions containing spent coins, and so that their latest firmware can work with ElectrumSV. I feel like I should write some notes about it and make sure I understand where things are with ElectrumSV and hardware wallet signing.

Trezor signing

The Trezor team does not provide Bitcoin SV support in their software. You have to use Trezor devices as if you were using Bitcoin Cash.

When ElectrumSV goes to sign a transaction, it detects it needs to provide the transactions that contain the inputs/coins being spent. These are gathered up, and passed with the incomplete transaction to the given account for signing, this passes down to the keystore and from there to the Trezor library and from there to the device. …


Overview

This document is intended to define the necessary work required to do our next refactoring pass, where we address problems with our wallet state management to help it better suit our needs into the future.

The previous refactoring project was to move to database storage of wallets and also to prepare for different forms of multi-signature transactions other than P2SH. It was not intended to fix all the things that need to be fixed in ElectrumSV. …


A transaction that is not valid yet, might be called partially signed or incomplete. ElectrumSV has a temporary way to structure these but it only serves the pre-existing needs we had. This article does not attempt to propose a solution but instead aims to gather some related thoughts together.

ElectrumSV’s temporary format

The incomplete transaction format that ESV inherited from Electrum Core was a binary variation on legitimate Bitcoin transactions. When parsing a Bitcoin transaction it was possible to identify whether it was complete or incomplete and extract any signing metadata if it was the latter.

When I released ElectrumSV 1.3.0 and added the ability to support non-P2SH forms of multi-signature, I needed to extend it. I didn’t want to have to deal with an extended format based on Electrum Core’s binary variation, so created a temporary JSON-based format until there was time to work out the larger needs. …


This article covers the release of ElectrumSV 1.3.7, and some of the more important changes that have been made since ElectrumSV 1.3.6.

We have a selected range of guides to common tasks that our users may want to do in our documentation, please check it out.

There is also a guide that illustrates some of the common uses of ElectrumSV. Especially if you are new to ElectrumSV, or coming from ElectrumSV 1.2.5 (or even earlier versions). This is partially replaced by the documentation guides, but still has some useful additional information.

The only safe downloads are available on: electrumsv.io

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!

About

Roger Taylor

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