Author

Topic: RBF adjust fee, choose adjusted output? (Read 90 times)

legendary
Activity: 3388
Merit: 4615
March 18, 2023, 06:59:35 PM
#7
- snip -
I think you should be able to broadcast a new transaction with desired fee rate.
- snip -

Makes sense.  So the suggestion is to just delete the original transaction and create a brand new transaction that uses the exact same inputs but which pays the higher fee.

I'll give that a try, seems like it should work.  Thanks.  I'll come back here to update and lock this thread if that takes care of the issue.

---------------  EDIT, added below ---------------

That did it.  Thanks. Locking thread.
legendary
Activity: 2380
Merit: 5213
March 18, 2023, 06:41:25 PM
#6
So, the node you have connected to doesn't have your transaction in its mempool.
I think you should be able to broadcast a new transaction with desired fee rate. If the fee rate is higher than the fee rate used for the previous transaction, those nodes that have your previous transaction in their mempool should replace that with the new transaction.
legendary
Activity: 3388
Merit: 4615
March 18, 2023, 06:34:51 PM
#5
I did not disable the RBF,  you can see it here on the "Pay..." selection from the "Send tab:




My transaction doesn't show up on the "History tab".  It only shows up on the "Send" tab.

Oh, I just remembered a contributing factor to my problem. When I tried to send the transaction a few days ago, I got this message:


I didn't want to pay the fee, so I copied the raw transaction using the Export->Copy to Clipboard option:


Then I pasted the exported raw transaction into a few transaction broadcasting locations to get it out on to the network.

So, the transaction HAS been sent (I can see it in mempool.space), but apparently, my Electrum doesn't know that?  How can I convince it to refresh it's list of transactions in the transaction History tab from a node that has it in the mempool?
legendary
Activity: 1512
Merit: 4795
March 18, 2023, 06:19:12 PM
#4
I used testnet for it, never mind the poor image quality too.

Hope you did not disable RBF, Electrum support RBF by default. You can see that in 'preference'.

On the history tab, you will right click on the transaction:



You will be able to click on increase fee.

Then click on show advanced settings:



Then click on decrease payment

legendary
Activity: 3388
Merit: 4615
March 18, 2023, 05:55:17 PM
#3
Right click on the transaction, click on: increase fee -> show advanced settings -> decrease payment.

I'm not seeing that option.

When I look in "Send":


I see a single transaction with a status of "Unpaid":


Right-click on this transaction doesn't have an "increase fee" option. Instead, it provides me with a menu of "Copy Column", "Copy Address", "Details", "Pay...", and "Delete":


If I click on "Pay...", then I'm able to adjust the fee, but unfortunately, it seems to extract the fee from the change and I don't see a way to tell it to extract the fee by decreasing the payment.

legendary
Activity: 1512
Merit: 4795
March 18, 2023, 05:35:10 PM
#2
Right click on the transaction, click on: increase fee -> show advanced settings -> decrease payment.
legendary
Activity: 3388
Merit: 4615
March 18, 2023, 04:58:34 PM
#1
I created a RBF transaction recently that has a single input and two outputs.
Output A sends to somewhere that I'd like to transfer some funds.
Output B is the change back to my Electrum wallet.

However, I was feeling patient (and greedy), so I adjusted the fee to be especially low.

Now that some time has passed without confirmation yet, I'm becoming impatient and have decided I don't want to wait quite so long anymore. I want to increase the fee paid on the transaction.

However, if possible, I don't want to add any additional inputs to the transaction, nor do I want to alter the amount in Output B being sent to the change address.  Instead, I'd like to reduce the value of Output A, so that the additional fees come from the funds that are being transferred.

Is this possible?  And if it is, what are the steps in Electrum 4.3.4 to accomplish this?
Jump to: