Thank you for this… I didn't realize that this was called a "URL Handler". This will be very helpful.

Thank you for this information!

Seems like Blockchain is the culprit here. Damn Blockchain!! This is no better than dealing with a centralized bank, if Blockchain.info can singlehandedly prevent this transaction from dropping so I can resend it with a fee.

I tried this, and it didn't work… it sees the $1 transaction as "already spent", so I can't resend the transaction.

The actual error message on the page says: "Some funds are pending confirmation and cannot be spent yet (Value 0.00163899 BTC)".

So it seems like all of my problems have been caused by Blockchain.info never dropping the transaction, and the apps that I have been using have all been pulling their information from blockchain.info?

Thanks! I will try this!!!

I tried this with MultiBit and it wouldn't let me spend the coins again there, but maybe I should try it with a different wallet instead.

Thanks. I imported the keys into MultiBit, but MultiBit wouldn't let me do the "double spend" because MultiBit ALSO sees the transaction as still pending/unconfirmed. Perhaps MultiBit is pulling its information from the Blockchain.info site?

Very interesting!! What does this mean? This is making me hopeful!

1. The stuck transaction on the blockchain can be seen here: https://blockchain.info/tx/c238d939b330b682abe1c729300636600254c23c67e1eea4e8daa9abc26dd2c5

2. Sorry, I'm new to this. I don't know if I have other funds on the unspent output. How can I tell?

Thanks,
Scott

Unfortunately, BitWallet is not the app that is rebroadcasting the transaction. BitWallet only broadcasts the transaction once (according to the BitWallet developers). It is other nodes on the Bitcoin network that are continually rebroadcasting the transaction.

It seems like there is nothing I can do to rebroadcast this transaction with a fee, and that I have lost this $1 forever. At least it was only $1, though.

I don't see any options within my web browsers' preferences to set the default apps for links. I am looking at Safari, Chrome, and Firefox.

I have 2 Bitcoin wallet apps on my OS X desktop computer: Bitcoin-Qt and Multibit.

Does anybody know how I can tell OS X which one of these apps that I would like to be the default Bitcoin wallet app whenever I click on a "bitcoin:" URL?

Right now, Multibit launches every time I click on a bitcoin link, but for now, I'd like to have the Bitcoin-Qt app launch instead.

Thanks!

Thanks so much. I tried importing the private keys into another wallet app (MultiBit), but it wouldn't let me create a new transaction because it saw the "unconfirmed" transaction as a valid transaction. So, my "available to spend" BTC balance had already reflected the lower balance, as if the transaction had already gone through.

Hi there,

I have a feature request for Bitcoin Core. (I'm not a programmer, so I am unable to contribute technical skills to getting this implemented. I can just type up my feature request here. )

I recently lost $1 worth of BTC, because one of my transactions got permanently stuck in an "unconfirmed" state. This is because my iOS wallet app (BitWallet) didn't require me to include the required .0001 fee with it. As a result, my transaction never confirmed. To make matters worse, my app doesn't have the ability for me to cancel unconfirmed transactions so I can rebroadcast the transaction with a fee attached. Full details in this thread: https://bitcointalk.org/index.php?topic=722880.0 

So my transaction seems to be lost permanently.

It was pointed out to me on a Reddit thread (located at http://www.reddit.com/r/Bitcoin/comments/2ci5mb/bitcoin_is_not_the_answer_for_micro_transactions/) that the answer could be as simple as the Bitcoin Core app implementing Peter Todd's "Replace By Fee" tools, which he has uploaded onto GitHub here: https://github.com/petertodd/replace-by-fee-tools

I would like to express my support of seeing these "Replace By Fee" tools implemented into the Bitcoin Core app. This would help prevent users like myself from having their transactions lost permanently if they forget to attach a fee!

Thanks!

A-ha! This explains everything!! Thank you for catching me up to speed on how all of this works!

Thanks so much, everyone. This is extremely helpful to learn about this stuff. I think my $1 transaction may be lost forever because the app may try to continually push this transaction forever… but $1 is a small price to pay for an invaluable learning lesson like this!

Ah, interesting. So it seems like I created this problem by sending coins before my client was fully synchronized. Would you mind explaining how a reordering of transactions could potentially cause someone to miss transactions? I'm just trying to wrap my head around this, because this is all so new to me.

Also, if I imported my private keys into another app (such as MultiBit, for example), I assume that the other app would pull all the "correct timestamps" from one of the Bitcoin nodes on the network, because that other app would be starting completely from scratch?

Thanks!!

Hi there,

I believe that I have discovered a bug with timestamps in the Bitcoin-Qt client for OS X. I have attached a screenshot below, along with an explanation of the bug. (I am not a programmer, so I don't have the skills to fix this bug myself… I can only report it.)

I launched my Bitcoin-Qt client (version 0.9.2.1) on OS X 10.8.5 a few days ago, and the Bitcoin-Qt client started the process of synchronizing to the network and "catching up" to all the missed transactions since the last time I had launched Bitcoin-Qt.

However, BEFORE the synchronization finished getting completely up-to-date, I decided to send coins to someone's Bitcoin address (transaction ID 413452e88a2b3b5155c26b62c38e53e3924e6c4d41fb3a8ecaeda269e6f5e4b8-000). I did this at exactly 7/29/14 00:58. In other words, I sent these coins BEFORE the green checkmark icon appeared in the lower right corner of the Bitcoin-Qt client. I sent these coins while the "syncing icon" appeared in the lower right corner of the client.

The coins were sent successfully.

However, after these coins were successfully sent, my Bitcoin-Qt client still needed about 10 minutes to finish synchronizing to the Bitcoin network, so that it could "catch up" on all the missed transactions from the previous days.

Sure enough, a whole bunch of incoming "receive transactions" started showing up in my client. These were coins that had been sent to me from the previous days, and my Bitcoin-Qt client was displaying these transactions for the very first time to me.

BUT THIS IS WHERE THE BUG CROPS UP: All of these "receive transactions" came in with the same exact timestamp as my "send transaction" mentioned above. All of these receive transactions were ACTUALLY received by the Bitcoin network on 7/28/14 (or earlier), yet ALL of these transactions are showing up in my Bitcoin-Qt client with the same timestamp of 7/29/14 00:58… the same exact timestamp as my send transaction mentioned above.

If you take a look at the screenshot below, you'll see this bug in action. You'll notice that every single "receive transaction" has the exact same timestamp as the "send transaction", even though those timestamps aren't accurate. All of those receive transactions actually took place BEFORE the listed timestamp.

For example:
The top 0.002 BTC transaction is transaction ID c0257b7505d7a7f424593bc8f40c1352cb514c686fe6a9545790c200e12294c2.
The 0.0017 BTC transaction is transaction ID d50482a4c646454aff15c37cd5afdb5c3d30bcf92513c1e65c55d5286eebdef0.
The 0.0014385 BTC transaction is transaction ID e5086f06d1b3420eb020bc0c8b04a6d1c274a0f6c90c430d90207e0d4cb9f4e0.

You'll notice that all of those transactions were actually received BEFORE 7/29/14 00:58, but they are showing up in my client as 7/29/14 00:58.

Thanks!!