Skip to content

Conversation

jonasschnelli
Copy link
Contributor

1) Adds an option to set the opt-in-RBF flag when creating a transaction
bildschirmfoto 2016-06-09 um 11 14 44

2) Adds a fee bump option to the context menu.
The option is only enabled if the transaction isFromMe and signaling RBF.

bildschirmfoto 2016-06-09 um 11 12 06

bildschirmfoto 2016-06-09 um 11 10 58

For the full "RBF experience" we also should consider:
#7817 (attribute replaceable (RBF) transactions)
#7826 (show conflicts of unconfirmed transactions in the UI)

This will allow to add flags for RBF and other features
On RPC level, we show possible mempool conflicts already via detecting them over the CWallet::GetConflicts() function.
Currently, the GUI shows only conflicts with transaction in a block.

This results in displaying replaced transaction (RBF) wrong.

This PR will mark unconfirmed transactions that are _not_ in our mempool and have conflicts as conflicted.
@laanwj laanwj added this to the 0.13.0 milestone Jun 9, 2016
<string>Signal Replaceability</string>
</property>
<property name="toolTip">
<string>Signals that this transaction can be replaced with a transation paying higher fees (as long as the transaction is NOT confirmed).</string>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

transation -> transaction

@luke-jr
Copy link
Member

luke-jr commented Jun 16, 2016

"signals replaceability" doesn't really seem useful terminology for users. Maybe "Allow increasing fee later" or something would make more sense.

IMO there should be some way for the user to actually control what the fee is bumped to.

@laanwj
Copy link
Member

laanwj commented Jun 20, 2016

Unfortunately this missed the 0.13 feature merge window. We should merge it soon after 0.13 is branched off.
(even if not perfect, even if some texts could still be improved, this is a strict improvement)

@laanwj laanwj removed this from the 0.13.0 milestone Jun 20, 2016
@btcdrak
Copy link
Contributor

btcdrak commented Aug 19, 2016

needs rebase

@rebroad
Copy link
Contributor

rebroad commented Sep 15, 2016

is anyone working on rebasing this or shall I?

@jonasschnelli
Copy link
Contributor Author

I'm currently not working on this and I have no near future plans to work on this.
We should first review and merge #8456.

@jonasschnelli
Copy link
Contributor Author

Closing. We need RPC support first.

@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.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants