1
I have a transaction which doesn't confirms for last 3 days and is not most likely going to confirm at all in near future due to a recent situation in mempool.
Will it be working if I'll do the following? Are there any risks to loose my bitcoins forever, or even to get banned by system for double-spend?
- Dump that transaction with 'getrawtransaction'
- Decrease one of it's outputs by X in my hex editor, so that X will be added up to transaction fee
- Sign that transaction with 'signrawtransaction' and send it
Did your original transaction opt-in to RBF? – MeshCollider – 2017-08-24T09:02:33.073
How could I know that? – vdudouyt – 2017-08-24T09:09:01.693
Check if any of the sequence numbers on your transaction are less than 0xffffffff - 1 – MeshCollider – 2017-08-24T09:10:25.500
All are equal to 0xffffffff - 1 (0xfffffffe). This means that I don't have RBF, I guess? – vdudouyt – 2017-08-24T09:17:00.330
Correct. So this is the answer you need: https://bitcoin.stackexchange.com/questions/9046/why-is-my-transaction-not-getting-confirmed-and-what-can-i-do-about-it
– MeshCollider – 2017-08-24T10:04:44.670Thanks, I have taken a look at that article - they are saying to run bitcoin-core with special options and re-send bitcoins. But can I use sendrawtransaction exactly as described above in order to do that? I want to ensure that I will use exactly the same inputs for resending transaction, and no new inputs will be tainted during transaction re-sending. – vdudouyt – 2017-08-24T10:11:10.437