Bitcoin Forum
December 03, 2016, 07:46:44 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 [2]  All
  Print  
Author Topic: 4hrs (now 24+) and still unconfirmed?  (Read 1814 times)
deepceleron
Legendary
*
Offline Offline

Activity: 1470



View Profile WWW
August 04, 2011, 11:10:14 AM
 #21

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.

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480794404
Hero Member
*
Offline Offline

Posts: 1480794404

View Profile Personal Message (Offline)

Ignore
1480794404
Reply with quote  #2

1480794404
Report to moderator
1480794404
Hero Member
*
Offline Offline

Posts: 1480794404

View Profile Personal Message (Offline)

Ignore
1480794404
Reply with quote  #2

1480794404
Report to moderator
1480794404
Hero Member
*
Offline Offline

Posts: 1480794404

View Profile Personal Message (Offline)

Ignore
1480794404
Reply with quote  #2

1480794404
Report to moderator
marvinmartian
Full Member
***
Offline Offline

Activity: 224



View Profile
August 04, 2011, 03:30:47 PM
 #22

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.

"... and the geeks shall inherit the earth."
Remember remember the 5th of November
Legendary
*
Offline Offline

Activity: 1526

Reverse engineer from time to time


View Profile
August 04, 2011, 06:33:22 PM
 #23

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

BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
marvinmartian
Full Member
***
Offline Offline

Activity: 224



View Profile
August 04, 2011, 08:56:24 PM
 #24

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?

"... and the geeks shall inherit the earth."
Kermee
Full Member
***
Offline Offline

Activity: 140



View Profile
August 04, 2011, 11:20:34 PM
 #25

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
Legendary
*
Offline Offline

Activity: 1148



View Profile
August 05, 2011, 06:05:34 PM
 #26

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
Full Member
***
Offline Offline

Activity: 210


View Profile
August 05, 2011, 06:14:07 PM
 #27

Is there anyway to choose which block to solve?
Kermee
Full Member
***
Offline Offline

Activity: 140



View Profile
August 05, 2011, 08:15:17 PM
 #28

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
Full Member
***
Offline Offline

Activity: 140



View Profile
August 05, 2011, 08:17:55 PM
 #29

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. Wink

Cheers,
Kermee

Remember remember the 5th of November
Legendary
*
Offline Offline

Activity: 1526

Reverse engineer from time to time


View Profile
August 05, 2011, 08:21:20 PM
 #30

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.

BTC:1AiCRMxgf1ptVQwx6hDuKMu4f7F27QmJC2
jackjack
Hero Member
*****
Offline Offline

Activity: 868


May Bitcoin be touched by his Noodly Appendage


View Profile
August 05, 2011, 09:09:10 PM
 #31

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

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!