Transaction sent 5 days ago still nothing on blockchain.info? <resolved

[brubits]

I sent on:
Date: 4/25/2013 06:05
To: 1Ca5HB3FRPLePuikKD6gucT4J4DjGZj2jm
Debit: -0.23 BTC
Transaction fee: -0.027 BTC
Net amount: -0.257 BTC

via Bitcoin v0.8.1-beta :
A LARGE data transaction, (many little receives into one send) 13+ hours ago,
and no sign of it on Blockchain.info so far.  Wallet is out of sync and DL'n blocks...
where would it go?
where could it be?

https://blockchain.info/address/1Ca5HB3FRPLePuikKD6gucT4J4DjGZj2jm

[1715082618]

1715082618

[1715082618]

1715082618

[Stephen Gornick]

Wallet is out of sync and DL'n blocks...
where would it go?
where could it be?

The client will not broadcast a transaction until it syncs.

[brubits]

The client will not broadcast a transaction until it syncs.

Is that something different that in the version 0.7.2 ?

The prior transactions sent by the version 0.7.2 worked (just before I upgraded), can be seen on blockchain.info, but haven't been confirmed in the client.

[Stephen Gornick]

Is that something different that in the version 0.7.2 ?

No, that hasn't changed.

If you are claiming that v0.7.x broadcast a transaction without being in sync, I'm not sure why that would be.

But this is really a moot point.  Let the client sync and then your problem is resolved (or at least if there is still a problem, such as no connectivity, this can be properly diagnosed).

[brubits]

If you are claiming that v0.7.x broadcast a transaction without being in sync, I'm not sure why that would be.

But this is really a moot point.  Let the client sync and then your problem is resolved (or at least if there is still a problem, such as no connectivity, this can be properly diagnosed).

I sent two transactions via the out of sync v0.7.x, then I saw there was an update.
After updating, nothing but problems.

With ~15,400 blocks remaining / 92 days, it'll be a few weeks until it's close to being in sync.

[grue]

If you are claiming that v0.7.x broadcast a transaction without being in sync, I'm not sure why that would be.

But this is really a moot point.  Let the client sync and then your problem is resolved (or at least if there is still a problem, such as no connectivity, this can be properly diagnosed).

I sent two transactions via the out of sync v0.7.x, then I saw there was an update.
After updating, nothing but problems.

With ~15,400 blocks remaining / 92 days, it'll be a few weeks until it's close to being in sync.

stop using 0.7.2, use 0.8 (it has faster sync time). or use a lite client.

[brubits]

stop using 0.7.2, use 0.8 (it has faster sync time). or use a lite client.

I upgraded to 0.8 about 3 weeks ago, and my balance went to 0, as all of last years received transactions changed to unconfirmed and it started DL blocks from a year ago.  Finally enough blocks were DL'd that I had a balance and when I sent it, it went into the twilight-zone.

[brubits]

With ~15,400 blocks remaining / 92 days, it'll be a few weeks until it's close to being in sync.

Or only ~7500 blocks, it jumped up to the 15k number only for a little while today,

[brubits]

down to '51 days ago' for last received block... /making progress...

So my transaction was never broadcasted, or if/where it went it was ignored for some reason?

Is there no way to 'rebroadcast'?

[CIYAM]

If you are claiming that v0.7.x broadcast a transaction without being in sync, I'm not sure why that would be.

I regularly send tx's when out of sync (with all versions of the client I have used) - where did this idea that you need to be in sync to send a tx come from?

[grue]

down to '51 days ago' for last received block... /making progress...

So my transaction was never broadcasted, or if/where it went it was ignored for some reason?

Is there no way to 'rebroadcast'?

it rebroadcasts automatically if it's unconfirmed for long periods of time.

[brubits]

it rebroadcasts automatically if it's unconfirmed for long periods of time.

I see that it has in the log file, And it's showing up on blockinfo now.


I guess that's one reason to be sync before sending btc.

These:

ResendWalletTransactions()

started showing up in the .log after 5 days.

[Stephen Gornick]

I regularly send tx's when out of sync (with all versions of the client I have used) - where did this idea that you need to be in sync to send a tx come from?

Are you saying they are being broadcast to the network before it has reached sync?  If so, is this from the Bitcoin-Qt or sent via API with bitcoind?

[brubits]

Are you saying they are being broadcast to the network before it has reached sync?  If so, is this from the Bitcoin-Qt or sent via API with bitcoind?

My last 3 send btc transactions have yet to be confirmed in the Bitcoin-Qt because it's last received block was generated 37 days ago.

They can all be found on blockchain.info

[CIYAM]

Are you saying they are being broadcast to the network before it has reached sync?  If so, is this from the Bitcoin-Qt or sent via API with bitcoind?

Yes - and this can be done with bitcoin-qt as well. Assuming you don't have a copy of the wallet on another computer then there is no problem doing this as tx you make are stored in your wallet (so it won't try and spend the UTXOs again).

[Stephen Gornick]

Are you saying they are being broadcast to the network before it has reached sync?  If so, is this from the Bitcoin-Qt or sent via API with bitcoind?

Yes - and this can be done with bitcoin-qt as well. Assuming you don't have a copy of the wallet on another computer then there is no problem doing this as tx you make are stored in your wallet (so it won't try and spend the UTXOs again).

Ok, just so that there is no confusion here.

Obviously, if you copy your private keys from Bitcoin-Qt and broadcast a transaction from another client then that transaction will be seen in blockchain.info without the local Bitcoin-Qt being sync'd.

But what I'm asking about is if you have the Bitcoin-Qt client and it is not currently sync'd, but then create a new spend transaction.  Are you claiming that the transaction is then broadcast to the network immediately ... before sync is attained?   That's different behavior than I remember seeing before.    It should only take someone two minutes to observe the behavior, but at this moment I personally am using a system on which I cannot install Bitcoin-Qt/bitcoind so if someone could verify and pipe in that would help.

[Edit: I'm specifically referring to DEFAULT behavior of the Bitcoin-Qt client, and not a command line/API transaction.]

[CIYAM]

But what I'm asking about is if you have the Bitcoin-Qt client and it is not currently sync'd, but then create a new spend transaction.  Are you claiming that the transaction is then broadcast to the network immediately ... before sync is attained?

Yes - I do this *all* the time (as I don't normally run bitcoin so my client is *never* in sync when I start it). You have to wait until the GUI *appears* (so you can't do a tx *instantly*) but you certainly *do not* need to wait to be in sync.