Bitcoin Forum

"Got paid" from Deepbit this morning (10:00am EDT) and my bitcoin client is showing the transaction as still 0/unconfirmed.  It's now 2pm EDT.  I've never seen this before.  Similarly, nothing showing in block explorer.

My client has 24 connections and is currently on block 139476.

;-(

chill and wait. it is going though, some time in the future. 

Really?  I've NEVER seen it take this long.  I'm up to 5 hours now and still 0/unconfirmed.

really.

There are 558 unconfirmed transactions (185936 bytes):

There are 484 low priority transactions.

-- You're somewhere in there...

Cheers,
Kermee

Did you try to restart the bitcoin client?

That won't help until the TX is 'posted' into a block, which hasn't happened yet.

It seems that most pools solving blocks basically ignore most low-priority TX's (i.e. no-fee transactions) at this point.  Which is why there's so many unconfirmed transactions lately.

Cheers,
Kermee

Yes, whenever I suspect something is fishy I restart, rescan if it seems necessary, then even force various -addnodes to finally see if I can get confirmations and blocks to update in a more "rational" manner.  None of this had any effect today, hence I hit the boards here.

is there a way to have Deepbit pay 0.01 BTC transaction fee when auto-payment triggers?  I'm fine paying that especially if it helps alleviate this horrible lag spike in my daily quota / payment.  My little payment is now stuck way down the low priority queue.  ;-(

the low priority queue will be gone tomorrow. :) just chill and wait

A payment FROM Deepbit is unconfirmed?
As they put payments in the blocks they find, it's kinda weird...

https://en.bitcoin.it/wiki/Transaction_fees

On the other hand, nobody mining new bitcoins necessarily needs to accept the transactions and include them in the new block being created. The transaction fee is therefore an incentive on the part of the bitcoin user to make sure that a particular transaction will get included into the next block which is generated.

Basically, it's up to the people/pools in determining which TX's are accepted and put into the new blocks as they are found.  As you've noticed, those people/pools have been ignoring the low-priority/no-fee ones lately.

http://blockexplorer.com/

Check the 'Transactions' column.

Cheers,
Kermee

Yup, and still unconfirmed.  Going on 6 1/2 hours now.  Guess I'll have to wait until tomorrow (as per post above).

Deepbit is a pool. Is it really smart to refuse its own tx's?

Did you check your transaction in blockexplorer? The link is the date column in the Deepbit payments page
You have all the 139497 blocks? If so, you should contact them

I'm not seeing anything sent in blockexplorer to my address.  On bitcoincharts I was able to see it a while back under "low priority" the site is down for maintenance apparently atm.

I've sent Tycho a PM about another issue (on the db forum sticky) I guess I should add this too.

You're assuming DB uses the same bitcoind as the bitcoind that [Tycho] issues payments.  I highly doubt they are the same and if it is, that's a huge security risk as far as setting up pools and issuing payments to pool members.  [Tycho] has already confirmed (https://bitcointalk.org/index.php?topic=3889.msg410414#msg410414) that he only keeps a 'minimal' amount of BTC's on-hand for payments so I'm sure he's running at least a few different wallets/bitcoind's.


For the OP, it won't show up in Blockexplorer yet.  OP verified it's still an unconfirmed transaction (TX) via http://bitcoincharts.com/bitcoin/ (which is down right now).  He has all the blocks on his client I believe.

Cheers,
Kermee

I never thought about it that way
But it's still strange, he could use a modified bitcoind that accepts all tx's from his node processing payments
There's a reason he doesn't do that, I must forget something

Sorry I didn't read post#8 carefully

I have 2 transactions stuck in 0/unconfirmed.

1 receiving, and 1 sending.  I see both of them in "Low Priority" at bitcoincharts.

I've never had this happen before, not for several hours like this.  Did all the pools, just today, stop accepting TX's with no fee?

OK, 5 seconds after I post this, I get 1 confirm on each.


Never fails   ;D

Not me, still unconfirmed, and my client is fully updated to (currently block 139537 now).  Here's the transaction, btw:

http://bitcoincharts.com/bitcoin/#4af75cff1604f0de8abf07c2ab90be0f64403a2801e59778fd53006b297404a9

i happen to have the same problem with a deepbit transfer with now more than 12 hours.
i'm on block #139544 .

Maybe you should complain to pools that are raking in the BTC in pool fees but paying 0 transaction fees when sending out payments to users.

I sent an email of course.

Thankfully, sometime during the wee hours of the morning, my payment from yesterday got confirmed.  But it took something like 20 hours.

My daily payment for "today" seems to be doing the same thing.  I think something strange is going on over at Deepbit wrt. to daily payments.  I don't think they're intentionally withholding.  I think it's some kind of odd bug somewhere in the hash between transactions, blocks, and clients. 

My hunch is that if you get paid and your client isn't up and running when the payment occurs, you get cast into the void of payments that take forever.

Happened to me too, seems Tycho doesnt want to pay fees.

Or, it could be that transactions that get fired off after a block has been completed get cast "into the void" and not part of deepbits own block solution?  Something like that?

There's a patch to include your own non-fee blocks for bitcoind I was just told about.

That would probably make more sense for Tycho vs. upping the limit of non-fee blocks since that opens up someone to abuse/spam non-fee transactions.

Probably need to talk to Tycho about implementing/patching on his pool.

Cheers,
Kermee

This is nothing, I have a transaction from fucking June 25th that's still "0/unconfirmed".  The address I sent it to is a correct address of somebody I know.  Seriously, WTF?

Is there anyway to choose which block to solve?

That might be a Bitcoin client issue... Make sure your blocks are up to date (at 139758 at time of this reply) or else check the transaction on Blockexplorer with either your sending or receiving address.

Cheers,
Kermee

Looks like [Tycho] fixed the issue (https://bitcointalk.org/index.php?topic=3889.msg431082#msg431082) with at least DB payouts.  He forgot to 'Save Settings' on bitcoind restarts on his pool during the last maintenance. ;)

Cheers,
Kermee

Nope, the whole networks works on the same block until it's found, then we move on the next one.

Maybe you should look at the link in my sig