Author

Topic: First-seen-safe replace-by-fee (FSS RBF) (Read 1950 times)

legendary
Activity: 1442
Merit: 1179
August 15, 2015, 06:11:59 PM
#3
Thanks, yea the only way I was able to fix it was by sending additional funds so I could increase the fee.
sr. member
Activity: 268
Merit: 256
August 15, 2015, 04:52:45 PM
#2
You probably could be able to send additional funds to that address so that you can increase the fee. Since the second transaction would be rejected by FSS RBF, it should be okay to send the address extra Bitcoin for the fee and still have the transaction be accepted as long as the outputs are in the same order with new ones (for change) are appended at the end of the list.

You could also do the standard fix of wait it out or CPFP.
legendary
Activity: 1442
Merit: 1179
August 14, 2015, 12:33:40 AM
#1
I'm playing around with first seen safe replace by fee (http://bitcoin-development.narkive.com/NgSiQBmM/bitcoin-development-first-seen-safe-replace-by-fee)

My first go around I had no issues and I was able to do this successfully because the address I used had multiple unspent outputs available.

So then I tried again but this time with only 1 input and zero fee so that the entire input gets sent to the recipient. Since I only had 1 input available and I sent it all to the recipient I'm unable to do a RBF since the amount to the recipient cannot be changed per the policy.

With this node policy is the only way to fix a transaction like the above is just wait it out, or by sending additional funds to the address so I can add a fee? Or is there a way to send less to the recipient and put it towards a mining fee?
Jump to: