Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better text for sending transaction option "Request Replace-By-Fee" #11344

Closed
ghost opened this issue Sep 15, 2017 · 6 comments · Fixed by #11556
Closed

Better text for sending transaction option "Request Replace-By-Fee" #11344

ghost opened this issue Sep 15, 2017 · 6 comments · Fixed by #11556

Comments

@ghost
Copy link

ghost commented Sep 15, 2017

Howto replace a stuck transaction with another with higher fee ?

bitcoind 0.15.0

The marking option "Request Replace-By-Fee" in the sending transaction GUI page should have a better understandable text.

The sender does not "request" anything when creating the transaction. This is just a tag for a later possibility, as I understand as a rather normal user.

I would suggest something like

"Let me increase the fee of this transaction later, if it should not get confirmed in expected time ('Replace-By-Fee' feature)"

@fanquake fanquake added the GUI label Sep 16, 2017
@ghost
Copy link
Author

ghost commented Sep 16, 2017

I have just read https://bitcointechtalk.com/whats-new-in-bitcoin-core-v0-15-part-3-50c42125625e
about "Replace By Fee (RBF)" and I am unsure, if one needs to tag the initial transaction as "Request Replace-By-Fee" or if one should do that only for the second transaction (which has a higher fee) to replace the first one. This is really unclear to me.

@sipa
Copy link
Member

sipa commented Sep 16, 2017

@wodry The replace by fee policy is described in BIP125. It's the initial transaction that needs be marked as replacable.

@ghost
Copy link
Author

ghost commented Sep 16, 2017

@sipa Sure, one could also look into the source code to figure it out. This is intended as a feedback on GUI usability :-)

@flack
Copy link
Contributor

flack commented Sep 16, 2017

How about something like "Allow increasing transaction fee later on"?

@ghost
Copy link
Author

ghost commented Oct 1, 2017

Issue is solved with PR #11428

@ghost ghost closed this as completed Oct 1, 2017
@meshcollider
Copy link
Contributor

Please don't close the issue until the corresponding PR is merged, that will be done automatically when the PR gets merged.

@ghost ghost reopened this Oct 2, 2017
jonasschnelli added a commit that referenced this issue Dec 5, 2017
db0b737 [Qt] Improved copy: RBF checkbox, tooltip and confirmation screen (Sjors Provoost)

Pull request description:

  Fixes #11344 and replaces #11428.

  **Before**:
  <img width="588" alt="before" src="https://user-images.githubusercontent.com/10217/31984211-3299e81a-b993-11e7-94e9-bf63d2fed4bd.png">

  **After**:
  <img width="578" alt="after" src="https://user-images.githubusercontent.com/10217/31984404-11f839da-b994-11e7-86ad-4c17a7d44b86.png">

Tree-SHA512: 04876b2f2eab53c8d4fd4279e8384fd4869af7e15de7648b2689092f800b6ae9c890c01c26c2f7deffe79a1d70c6440d702cbe420e44fe3ded25c5b83d44ecfa
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
5 participants