This is another article roughly exploring different directions in how the UI in the ElectrumSV wallet application should work. If you want insight into this process and the thoughts I am considering, then you might consider reading these. Otherwise, perhaps not. You can consider this article like a public notebook…

This is another rough exploration of possible UI for the in development ElectrumSV 1.4 release. In this case we’re looking at how we can take the current multi-signature and take it up a level, which shouldn’t be hard given the low bar. Multisignature account creation Alice wants to create a group account. She…

If you’re looking for something solid to read about this is not it. This is a rough exploration about how to address the outstanding UI issues with the in development multi-account ElectrumSV 1.4 release. The process is I will try and envision how Bob will use the wallet and mock…

I’m not a Bitcoin expert. I don’t know if this is the right approach. But it is an initial one we can put into ElectrumSV with minimal work, given we have peer channel support and an until now unused system for adding contacts. Alice connects with Bob Alice gives her contact details to Bob…

As it had been a long time since I tested the pending 1.3.16 release, and as there were additional fixes made since it was originally started, I decided to retest everything. This is a small part of that ongoing ordeal. The months long delay It was originally intended to release 1.3.16 when we received…

I suspect there’s an experience we can define for the ElectrumSV user that we can achievably create, and level up from the existing complex “Bitcoin” experience ElectrumSV users get. Here’s one of perhaps a few quick articles dumping the ideas I have in mind. This is a P2P first experience. An overview of walllet activity …

Let’s think through the minimum changes that we can make to the in-development version 1.4.0 of ElectrumSV to allow users to support a P2P experience. Requirements: Identify any unnecessary complexity and reduce it to the minimum alternative. Do the simplest possible implementation so that we can switch out the protocols…

I’ve written a few articles recently questioning the technologies that still feature in Bitcoin SV like addresses and script hashes. This article questions the practice of applications declaring which transactions they created. Here we can see that 750,000 transactions were created by the most active application STUK.CO. Each of these…

As application developers and service providers should be moving away from addresses, so should they be moving away from script hashes. Bitcoin SV has dropped standard scripts. Addresses can now be seen as a low quality artifact of the standard script regime. We can also look at script hashes as…