You can drop the second commit. This is automatically done by a script.

Agree with Marco, and it sounds a little weird, I'd prefer something like Allow transaction to be replaced by one with a higher fee later on (BIP 125)

Also, in your PR it's better to write Fixes #11344 rather than see, because then GitHub automatically closes the issue and links to this PR

Please squash commits

The tooltip already explains the checkbox purpose. Request Replace-By-Fee sounds good to me.

Can I squash the commits via the Github GUI? I did not find how one could do that. If that is only possible with git commands, unfortunatley that's too complicated for me.

Just noticed the tooltip as well. Agree with @promag that the displayed text does not need clarification. Maybe you could mention BIP 125 in the tooltip?

@wodry not sure if its possible with the GUI, but I doubt it. There are instructions on how to do it here: https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits

I have seen the tooltip also only when working on this PR, not when doing the transaction as user. The tooltip text is good, but there is a problem with the Tooltip because users and even developers do not see it, as proven here.
In any case, the button text at the first step should be clearer, in my opinion.
One could also argue the other way round: If the tooltip explains fine, the first text suggestion "Allow increasing transaction fee later on" is really clear to the user, that's what the user effectively get's from this button, and technical details like BIP, and that it is a replacement technique, are to be found in the tooltip text. Clear user feedback from me: "Request Replace-By-Fee" says nothing to a user.

@promag @MarcoFalke "Request Replace-By-Fee" may be an accurate technical description if you know the underlying implementation, but nothing a casual user can decipher. It's a bit like labelling a hyperlink "perform an HTTP GET request against URI" instead of "go to this page". IMHO the initially visible text should give an indication of what it does in a way the user can relate to (and what it does is it allows you to use "bump fee" later on, right?). The technical details (like BIP number and technical acronyms) should go to the tooltip, since it's a "would you like to know more?" type of thing

Screenshot before/after please?

I tried to squash the six commits according to

https://help.github.com/articles/fork-a-repo/

https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits

git rebase -i HEAD~6

did nothing. Now it seems, that I messed it up. Sorry. If anyone could give me some commands for git console to fix it, I would be thankful.

Here is the screenshot of current 0.15.0.1 GUI send transaction page. Have no screenshot of the window after this change, have no capacitiy to build and run it.

I prefer to wording in master, though I agree ">Request< Replace-By-Fee" is maybe not ideal from the users perspective.

Here's the after screenshot:

I agree that "Replace-By-Fee" is not clear enough. "Allow increasing transaction fee later" (without "on") is more clear. The footnote mentions the technical terms, which helps users google it.

Although there's plenty of space in the UI now, a shorter alternative check-box text is: "Allow Fee Increase"

Alternative footnote: 'If the transaction takes a long time to confirm, this allows you to increase the fee later ("Replace-By-Fee", BIP 125). This uses a lower fee by default.'

@wodry tip for your next PR: use a different branch than master. E.g. git checkout -b my-cool-feature.

• Thanks @Sjors, for the screenshot and Your input.
• I am fine with Your and also @laanwj's suggestion to remove the "on" in the button text, and I am fine with the footnote suggestion, too, only "This uses a lower fee by default." I do not understand, so it should be clearer what You mean by that.
• Since I feel unable to cope with the git handling, I would be happy if You or someone else, who is able to do flexible and clean rebasing, would open a new PR for the relating issue Better text for sending transaction option "Request Replace-By-Fee" #11344 as a replacement for this PR.

Best Regards

@Sjors "This uses a lower fee by default." does it really though? I mean at least in the case of custom fee, I would expect it to use the fee you entered. Or do you mean "it allows you to use a lower fee and then increase it later on"? Otherwise I like your alternative text better than the current version

@wodry I can make a new PR if it simplifies handling (but I think you should be fine, using master is only inconvenient if you plan on making other changes while this one is still in flight)

@flack see v0.15 release notes:

Lower fee estimates for RBF users: previously it was difficult to change the fee of unconfirmed transactions after broadcasting them, so Bitcoin Core suggested fees higher than normally needed. As described later in this post, Bitcoin Core now provides tools for increasing the fee of already-sent unconfirmed transactions, so we give lower fee estimates to users of those tools since they can always increase their fee later if necessary.

@wodry:

• this could be a good opportunity to learn more about Git!
• if "This uses a lower fee by default." is confusing to you, then we should find a better phrase...

More generally, it would be nice to have some sort of way to test different wordings, maybe put some A/B testing in the client :-)

As @wodry is not going to maintain this anymore, I'm closing the issue, if anyone still wants to change this label feel free to pick it up.

I'll make a PR.

I made a fresh PR #11556, wording based on my own suggestion above.