4hrs (now 24+) and still unconfirmed?

[deepceleron]

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.

[marvinmartian]

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.

[Remember remember the 5th of November]

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

[marvinmartian]

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?

[Kermee]

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

[proudhon]

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?

[indio007]

Is there anyway to choose which block to solve?

[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?

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

[Kermee]

Looks like [Tycho] fixed the issue with at least DB payouts.  He forgot to 'Save Settings' on bitcoind restarts on his pool during the last maintenance.

Cheers,
Kermee

[Remember remember the 5th of November]

Is there anyway to choose which block to solve?

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

[jackjack]

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?

Maybe you should look at the link in my sig