How to make a bitcoin transaction and pay less than 1 sat/vByte

[Pmalek]

You may have to add information to click the use SSL button, because I got an error when I didn't.

What kind of "information" did you need to add?

I've succeeded in changing after I clicked the Use SSL button.

I don't remember having to click on "Use SSL" when I tested this on my own setup back when I was writing this thread. Maybe it was already turned on from before or the software did it by itself after a restart. I also don't remember seeing error messages.

[nc50lc]

I don't remember having to click on "Use SSL" when I tested this on my own setup back when I was writing this thread. Maybe it was already turned on from before or the software did it by itself after a restart. I also don't remember seeing error messages.

I see what happened here:
He must have disabled that "Use SSL" switch beforehand (from his old settings or something else) that's why he had to enable it when he followed your instructions.

On the other hand (at your end);
You do not remember having to tick that settings and your test worked right away because it's switched-on by default.

Including a short note should prevent rare instances like this.

[Pmalek]

I see what happened here:
He must have disabled that "Use SSL" switch beforehand (from his old settings or something else) that's why he had to enable it when he followed your instructions.

On the other hand (at your end);
You do not remember having to tick that settings and your test worked right away because it's switched-on by default.

Including a short note should prevent rare instances like this.

Are you saying that I should mention something in my OP about the Use SSL option and how it should be ticked for network changes to be recorded properly? I could add that somewhere in the tutorial.
Or perhaps you were trying to say that it should have been noted by Blue Wallet in the network settings tab?

[nc50lc]

-snip-

Are you saying that I should mention something in my OP about the Use SSL option and how it should be ticked for network changes to be recorded properly? I could add that somewhere in the tutorial.
Or perhaps you were trying to say that it should have been noted by Blue Wallet in the network settings tab?

Something like: 'Make sure that "Use SSL" is ticked' in the OP about BlueWallet should be enough.
It's switched-on by default, but in cases like what happened to "@Not your key not your BTC", the note should prevent it.

[hosemary]

Pmalek, since version 4.6.2 of Electrum, you no longer need to use the wallet.relayfee=(lambda: 0) command, and all you need is to be connected to a server that accepts transactions with a fee rate of less than 1 sat/vbyte.
I noticed this after SeriouslyGiveaway shared a link to your topic in another thread thinking that it's difficult to make such transactions using Electrum.

You may want to consider editing the topic, so that it reflects the changes that have made it easier to make sub 1 sat/vbyte transactions in more recent versions of Electrum.


LoyceV
I mentiond your name here, as I didn't want to repeat the same thing in your thread.

[TheButterZone]

Pmalek, since version 4.6.2 of Electrum, you no longer need to use the wallet.relayfee=(lambda: 0) command, and all you need is to be connected to a server that accepts transactions with a fee rate of less than 1 sat/vbyte.
I noticed this after SeriouslyGiveaway shared a link to your topic in another thread thinking that it's difficult to make such transactions using Electrum.

You may want to consider editing the topic, so that it reflects the changes that have made it easier to make sub 1 sat/vbyte transactions in more recent versions of Electrum.


LoyceV
I mentiond your name here, as I didn't want to repeat the same thing in your thread.

That's great, if only the newer executable versions & even the Python sources install of Electrum didn't have minimum system requirements (PyQt6 binary wheel dependency on non-backward-compatible system frameworks and dynamic library symbols) above what some of us actually have.

I can only run Electrum 4.8.2 bypassing the GUI entirely and using TUI/text mode (-g text) or headless daemon commands, and I had to go through hell installing everything that should have been, but wasn't, done automatically by the first or second command after downloading the .tar.gz Python sources file.

Now, I don't want to get off on a rant here, but...

[Charles-Tim]

Pmalek, since version 4.6.2 of Electrum, you no longer need to use the wallet.relayfee=(lambda: 0) command, and all you need is to be connected to a server that accepts transactions with a fee rate of less than 1 sat/vbyte.
I noticed this after SeriouslyGiveaway shared a link to your topic in another thread thinking that it's difficult to make such transactions using Electrum.

It is because you are using desktop Electrum for transactions will be the reason you did not know early. It was also not possible on mobile Electrum before, but version 4.7.0 supported it, the time it also supported fee customization. So far you connected to the node that is supporting it, the transaction will be sent.

[hosemary]

It is because you are using desktop Electrum for transactions will be the reason you did not know early.

I feel like you didn't get my point, or maybe I didn't get yours. I already knew about making sub 1 sat/vbyte transactions in Electrum.

Before Electrum 4.6.2, you needed to do two things to make a transaction with a fee rate of less than 1 sat/vbytes. One was to use the wallet.relayfee=(lambda: 0) command, and the other was to connect to a server that accepts sub 1 sat/vbytes transactions.

Now, it's much easier.
You no longer need to use the console, and all you need is to be connected to a server that accepts such transactions. Currently, even if Electrum connects to a server automatically or you choose a random server, there's a good chance that the server will broadcast your transaction.

I suggested editing the topic, so that someone without much technical knowledge who reads the guide doesn't get the impression that it's difficult to make a sub 1 sat/vbyte transaction in Electrum.
As I said, the suggestion came to my mind after reading this post in another thread.

[nc50lc]

It is because you are using desktop Electrum for transactions will be the reason you did not know early.

I feel like you didn't get my point, or maybe I didn't get yours. I already knew about making sub 1 sat/vbyte transactions in Electrum.

I think he's just adding a note about when it's implement on the Android version of Electrum
but somehow made his post look like going against yours due to the words that he's used, specially that first part.

[Pmalek]

Pmalek, since version 4.6.2 of Electrum, you no longer need to use the wallet.relayfee=(lambda: 0) command, and all you need is to be connected to a server that accepts transactions with a fee rate of less than 1 sat/vbyte.
I noticed this after SeriouslyGiveaway shared a link to your topic in another thread thinking that it's difficult to make such transactions using Electrum.

You may want to consider editing the topic, so that it reflects the changes that have made it easier to make sub 1 sat/vbyte transactions in more recent versions of Electrum.

That's great to know and thanks for pointing it out. I didn't know Electrum made that change and simplified the sending of sub 1 sat/vByte transactions. I will edit my OP and mention it. Charles-Tim's post isn't clear. Do you know if sub 1 sat/vByte transactions are supported on Electrum's mobile app or not?

[hosemary]

Do you know if sub 1 sat/vByte transactions are supported on Electrum's mobile app or not?

Yes, it allows you to set the fee rate manually and make sub 1 sat/vbytes transactions since the version 4.7.0. Now like the desktop version, all you need for making such transactions is to be connected to a server that accepts them.

From Electrum's Release notes:

  - new: allow manual editing of fee/feerate (#10371)
          This also allows sending sub-1 sat/b transactions on Android.