--snip--
Transaction ID: 3bf2e0fdd4a9ad01b83c679f83c247d019ecfa6f18c4fd075978b2c47075200a
--snip--
Appologies for the lack of intel.
I am both sender (from MultibitHD) and receiver (to Kraken). I have learned so far that the problem is caused due to low fee per byte.
I do hope to settle this transaction within the next few days, any idea what I can do best in this situation? Would waiting a little longer cause a the transaction to be refunded or what would happen if it doesn't get confirmed in the next few days?
Thanks for any help!
Since the receiver is an exchange, this pretty much rules out CPFP, the tx isn't opt-in RBF so that's out of the question to...
Multibit HD is no longer supported, if you move away from multibit HD to electrum (tutorial can be found here:
https://multibit.org/blog/2017/07/26/multibit-shutdown.html), you SHOULD be able to follow my wizard on
http://www.mocacinno.com/page/feechecker to create, sign and broadcast a transaction double spending the inputs of the unconfirmed transaction using electrum
Already helped me a long way here, thanks again for that. You're doing great work!
I have switched to electrum succesfully. Now I want to do the double spending, but feel uncertain if I'm doing this absolutely correctly. So I will bother you one more time, to make sure not to make any mistakes.
If I understand correctly, I now have to create a new transaction from Electrum. I enter the same address in 'pay to' and the same amount. Then send the transaction and broadcast it? Is that all?