Am I a complete idiot?

[1dullgeek]

So I suspect that what I'm going to describe below is pretty stupid. I’m just hopeful that there is some way that you can help me.  Here’s what I did.
 
I make a regular donation to a charity. In May I decided I was going to put this donation into bitcoin and then around Christmas time give the charity whatever amount that turned into. Well it’s December and I need to convert this bitcoin into USD so that I can give it to them. I did ask if they took bitcoin directly but they did not have any way to handle that. So my only option was to convert to USD.
 
I stored the bitcoin in one of the accounts in my KeepKey accounts and I generally access my KeepKey using Mycelium on my android phone. I got an address from GDAX and then created a TX to send. I chose a low miner fee of 47 sats/byte thinking that this would confirm in a few hours.
 
Well 6 hours later it hadn’t confirmed and I was getting impatient. So I tried to create a CPFP transaction w/Mycelium to push it through. But I didn’t have enough funds remaining in the account.
 
And this is the part where the stupidity starts to overflow.
 
I decided that since the TX hadn’t confirmed yet, I could just delete it from the wallet, get a new address from GDAX, create a new TX with a higher fee and send it. Which is exactly what I did. This time choosing 158 sats/byte. But the 2nd transaction never showed up on blockchain.info. And when I checked on different block explorers only one showed the transaction: blockcypher. And it showed it as being a double spend.
 
My guess is that the 2nd transaction hasn’t been propagated to the rest of the network.
 
So now I’m stuck. I’ve got one transaction out there that's been unconfirmed for about 20 hours, and a second transaction that's not propagated to the network. And, interestingly, when I plug my KeepKey into the "official" KeepKey wallet, it sees the first unconfirmed TX. But Mycelium sees the 2nd one.

What options do I have? Do I just wait? Will the 1st TX eventually confirm? Or are minor's rejecting it b/c they see a double spend attempt?

Here's the first TX that's visible just about everywhere:
https://blockchain.info/tx/bf81a31b15c1679a0057f0c285c7c0cd0b9eb6f749dd75063bce9f7913a5bc6a

Here's the 2nd TX that's only visible on blockcypher:
https://live.blockcypher.com/btc/tx/4fea38ab032d7d2ae11940952b518628e7fe6bf530855bc15a46027385a6e634/

[1714108659]

1714108659

[1714108659]

1714108659

[1714108659]

1714108659

[1714108659]

1714108659

[1714108659]

1714108659

[1714108659]

1714108659

[kcsunshine]

I took a look at the first transaction listed, and you are not even at 50 satoshis per byte. As I write this, network congestion is at 221,700 unconfirmed transactions.

Transactions fees are going up everyday. Take a look at the chart in the link below to see how fees are skyrocketing everyday. The current required fee to get confirmed in the next block is 433 satoshis per byte. I suggest you try an accelerator such as viabtc or confirmtx. I am not sure if they will accept your transaction. I just went through this myself, with success, thanks to help from this forum.

I don't even see your second transaction on the blockchain. I am sure someone with more experience than me will chime in. Good luck, because that is over 2 btc you have in limbo there.


https://bitcoinfees.info/

[1dullgeek]

Re: 2BTC, I know!

Re: the size of the fees, true, but here's the most recent transaction I sent prior to this and had no difficulty. And it's at 54 sats/byte.

https://blockchain.info/tx/eb479741b1ef7fcd6a434698c3d507ee67269b24b8e363d2d13a12538c64ee7e

That one got confirmed in about 5 mins. That's why I chose the size I did.  Clearly this was a mistake.

The question is this: is there anything I can do about this?  I tried confirmtx and viabtc. The former accepted it but I expected it to ask me for money since the size of the TX >400b, but it never did. I assume that means that confirmtx didn't actually queue the transaction. ViaBTC keeps saying "Submissions are beyond limit" which I presume means that they've taken their 100 submissions for the hour and I have to wait.

Do I have any other options?

[equator]

Your both transaction are low transaction fees and even they are double spent , so below i will give you the link which can help you in transaction acceleration. This service they are doing for free so dont pay anything for it.

https://bitcointalk.org/index.php?topic=2400745.0

https://bitcointalk.org/index.php?topic=2204426.0

Both of them are accelerating the transaction which are paid low transaction fees also. Hope your problem get solved.

[1dullgeek]

What is the impact of the double spend? Will minors ignore both transactions because of the double spend? Or will they (eventually) include one of them in a block?

I've submitted my tx to the first thread. Thanks for the links.

[DannyHamilton]

What is the impact of the double spend?

Most nodes will ignore the second transaction while the first transaction still exists in their memory pool.  Therefore, they will not relay it, and most miners will never hear about it.  The majority of miners have probably ONLY seen the first transaction, and the majority of those that have seen the second transaction have simply ignored that transaction and are therefore still only aware of the first.

Will minors   miners ignore both transactions because of the double spend?

A minor is someone that is not yet consider to be an adult.
A miner is someone that mines.


In general, miners will not care that it is a double spend.  If they still have the first transaction in their mempool, then most of them will simply ignore the second transaction.  If they have dropped the first transaction from their mempool, then they will accept the second.

Or will they (eventually) include one of them in a block?

That's impossible to say.

If neither transaction confirms in the next few days, then most miners will have dropped both transactions from their mempool (meaning that they will have forgotten that either transaction exists).


Your best option right now is to just wait for a few days.  If one of the transactions confirms, then the other will become invalid and will disappear.  If neither confirms, then after a few days both will be dropped from the mempools of most nodes and miners. At that point in time, you can then re-broadcast the second transaction and most fo the network and miners will hear about it (since the competing transaction will no longer be in their mempool).

Here is the second transaction in its raw hex format:

Code:

0100000007889d454f727fea74ec77582594201d61054c33396ff2626669e87d3f0a97f2ff010000006a47304402203213a8f3de77ad9cb945e8632048580c4c73f75310290a0a51a4e068c9655c6702205621f4812f6f2f4a339d45c2d04d2af10d595acf740a56aca57c4026c9c9d957012102b2d29ec444a8db84b62e655359d30c56a6a72da696c392f08a684b4e5ca43349ffffffffcfe6934b268acca1db14be760379e1a5c37a07b14df79000a7d1e2ff47733622010000006b4830450221009a62158b15928565ac3506324c2497e5a4b23a7418ef89a8c11f8ac0de73c39002205e468da4c0daacea6b9cdaa31a45b6d0d7e71dea4dab1955829a29ac765b202e012102dec5d2505aab6a3d4b95aba9c8b8cf224fb679aafb702e0d332c1224868780f5ffffffff26182e2a02fb4c8cc224e0a73f00f129214a40a473785ecaa1fd3f0e087c8d99000000006b483045022100ac397e92685c0e05e732cc5358946cf4154a7a872aeb0f81af437046022a32fb022056e568fbdad17ce20966186187047a04b5617adad8b3fe3fcfb95a45e9135994012102963238def6e2f692fe3836dec100b11825f566077264737315fae58caa10ef34ffffffffe531fbf011b3db1102434846b0db8a7be2445b6492b754f44ae1fbee7a9588ad000000006a47304402204669b9a53ffe157847379e3073a8dca621b0706cdb428d7c4a3c81f5ae3dae07022026e0cf4690e28dfa9a3cbb0ba4c794d05033a9618c29a68097f420247294cc620121039d60fcf88737511c1b07e1141cafaed9b25c22e19b85d0a6584704fda3d8ae82ffffffff43d1f5ffa0f8ab2b400e8d10b3f1649924b010447d5d0416dcfaf3c6ec387ef3010000006a4730440220250e794e34fd2b6d8914fbcd30f13da2dfd5ae4d865255d7130ccabed5ae67d302200eb87d5e7f0feae0f68fbda066e54885504960bc597816152689206847491a3b0121039d60fcf88737511c1b07e1141cafaed9b25c22e19b85d0a6584704fda3d8ae82fffffffffc412ae5e8ac5b8a8c7a637d91c46556cf9f6bfeec9917a47a8306546eac197a000000006a4730440220108bdfc9176e58991d129d30292d75cfed20c8f3c522e3fe6bcf05481673017b0220409c48c509b052820cf719420888d8b12e87677bbdf46adb00220e790ac0e39e012103a90e20a0913130c4b4b5b79e872184c48211dfdabce8dbb2000bce4adb813e67ffffffff5a1fa424390c3e16b20e6fff112a91a139ebf62a97799db9572bd16e395d33c8010000006a47304402207d00e12bc7f29a869fcc15e8349051a719a16ec5b396f0992732ef3e98fc4cc202207a36883917b1a3501aed3ab359e9cf8d0f4d8f3754b1700c10280f257d40521901210208be1fcfbb10baa9f6f80a5431b20a5eb4e669ab40f805f14c073a0121924a57ffffffff0265ad0100000000001976a914b5ef3db1fa72472c6b4ab1752b3a41ff06cc103188ac7cd4d40f000000001976a91455bb645526609c3a991ab18c766a6b32d793623388ac00000000

You can copy and paste that transaction into the textbox at the following link to re-broadcast it in a few days:

https://blockchain.info/pushtx

[1dullgeek]

A minor is someone that is not yet consider to be an adult.
A miner is someone that mines.

LOL! Oops!

In general, miners will not care that it is a double spend.  If they still have the first transaction in their mempool, then most of them will simply ignore the second transaction.  If they have dropped the first transaction from their mempool, then they will accept the second.
...
Your best option right now is to just wait for a few days.  If one of the transactions confirms, then the other will become invalid and will disappear.  If neither confirms, then after a few days both will be dropped from the mempools of most nodes and miners. At that point in time, you can then re-broadcast the second transaction and most fo the network and miners will hear about it (since the competing transaction will no longer be in their mempool).

Ok. Thanks. That clears things up a lot.

Here is the second transaction in its raw hex format:
...
You can copy and paste that transaction into the textbox at the following link to re-broadcast it in a few days:

https://blockchain.info/pushtx

Ok.

Thank you so much for the knowledge!