Neither unconfirmed transaction (double spend) is being confirmed

gnome56

newbie

Activity: 39

Merit: 0

Quote from: achow101 on November 22, 2016, 02:11:11 PM

Not many miners run full RBF so it can take a little bit of time for the double spend transaction to confirm.

Alright. I'll give this all 72 hours to clear, but I still find it very strange it'd take that long since the last time I had to do this, it worked quite quickly.

achow101

staff

Activity: 3458

Merit: 6793

Just writing some code

Quote from: gnome56 on November 22, 2016, 01:56:38 PM

https://blockchain.info/tx/29e4e5076006223438d5abe8da3f1a8ba582163f1de1e47286c86f80cb984dd0

I re-preformed the transaction and it seems as if it's not cleared despite multiple blocks being found since it was sent. The transaction fee is exceptionally high, so I still can't seem to figure out what the problem is...

Not many miners run full RBF so it can take a little bit of time for the double spend transaction to confirm.

gnome56

newbie

Activity: 39

Merit: 0

https://blockchain.info/tx/29e4e5076006223438d5abe8da3f1a8ba582163f1de1e47286c86f80cb984dd0

I re-preformed the transaction and it seems as if it's not cleared despite multiple blocks being found since it was sent. The transaction fee is exceptionally high, so I still can't seem to figure out what the problem is...

gnome56

newbie

Activity: 39

Merit: 0

Quote from: Jhanzo on November 22, 2016, 12:39:30 PM

The higher fee transaction's fee isn't not really high. That's a 30 satoshi per byte and the recommended fee is 90 satoshi per byte.
Also the output addresses are different. I hope you're not trying to rip someone off.

I'll resend once more with 100 satoshi per byte. I don't see how I could rip someone off with an unconfirmed transaction haha. They'd have to be exceptionally stupid to do any business simply based on an unconfirmed transaction. Though, the addresses are different because I'm sending the money to my circle.com account, which regenerates each time I reload the page. I simply copied the address from there, not from the old transaction.

Thanks for your advice, will report back once I've re-performed the transaction.

Jhanzo

hero member

Activity: 798

Merit: 506

Thank satoshi

The higher fee transaction's fee isn't not really high. That's a 30 satoshi per byte and the recommended fee is 90 satoshi per byte.
Also the output addresses are different. I hope you're not trying to rip someone off.

gnome56

newbie

Activity: 39

Merit: 0

Hi,

I sent two transactions. One with a very low fee, by mistake, and then another was a double spend to a different address, but with a higher fee.

I had trouble running abandontx in my client, or crafting an entirely new transaction online and broadcasting it. Abandoning it led to "Transaction is not eligible for abandonment" with error code -5, and broadcasting a transaction crafted on coinb.in led to errors regarding the memorypool (said that a conflicting transaction was already in mempool).

Eventually, after running -zaptx (or whatever the correct arg is to remove all transactions from my bitcoin core wallet and rebuild based on the block index), I was able to broadcast a new transaction from the same inputs to a different address with a higher fee. The problem is, neither transaction is being confirmed at all.

I don't mind waiting, but the last time that I did this, I had none of these issues and the "new" higher fee transaction sent without a hitch, and confirmed within two blocks. Did I do something wrong this time around? Here are the two transactions:

https://blockchain.info/tx-index/191609028 (low fee)
https://blockchain.info/tx/2969ceb1f7f5856ba1057986073de72a08f405aad948d0bf624f3f3f7ebf7052 (higher fee)

Thanks for any help, in advance, and hopefully I'm not duplicating anything other people have asked... but I have googled these issues at length!

Topic: Neither unconfirmed transaction (double spend) is being confirmed (Read 440 times)