Transaction disappeared in the void...

6 messages BitcoinTalk Brre, Quantumplation, knightmb, Gavin Andresen, Satoshi Nakamoto July 29, 2010 — July 30, 2010
Brre July 29, 2010 11:20 UTC Source ·

I did a transaction about 2 hours ago and it is staying at 0/unconfirmed, the recipient has no credit showing or even an unconfirmed line… The coins seems to disapeared in the void… Should I wait is this just a transaction that is going to take exceptionally long?

Quantumplation July 29, 2010 14:20 UTC Source ·

Brre: Your client will relentlessly broadcast that transaction into infinity until it’s accepted. It’s VERY persistent.

A block just probably hasn’t been solved in two hours. The difficulty’s up there, I know that.

knightmb July 29, 2010 15:20 UTC Source ·

Yeah, a block is being solved every 10 minutes or less, it shouldn’t take 2 hours unless the client has somehow lost connection to the rest of the network.

Gavin Andresen July 29, 2010 16:28 UTC Source ·
Quote from: Brre on July 29, 2010, 2:20:33 AM UTC

I did a transaction about 2 hours ago and it is staying at 0/unconfirmed, the recipient has no credit showing or even an unconfirmed line… The coins seems to disapeared in the void… Should I wait is this just a transaction that is going to take exceptionally long?

Are you still downloading the block chain? If you don’t already have all 70,000+ blocks in the block chain, then you transaction won’t show up as confirmed until you catch up.

Satoshi Nakamoto July 29, 2010 22:08 UTC Source ·

If the transaction didn’t go out immediately at first, like if you weren’t connected at the time, it may take up to 2 hours to resend it.  Long term, it does keep relentlessly sending it.

I’ll shorten that length of time in a future version.

You do need to have downloaded the complete block chain (currently 71040 blocks) before you’ll see any confirms.  Same with the recipient.

Brre July 30, 2010 11:28 UTC Source ·

The transaction started confirming about 4 hours afterwards after a couple of restarts… my block chain was updated, what was alarming was that previous transactions keep ticking up, for some reason my client was unable to broadcast that transaction, but was receiving everything OK..

I am on a slow 128k connection though…