Bitcoin Forum

Bitcoin => Bitcoin Discussion => Topic started by: Anonymous on July 18, 2010, 12:20:04 AM



Title: adg
Post by: Anonymous on July 18, 2010, 12:20:04 AM
adgf


Title: Re: Did block generation crawl to a halt?
Post by: Anonymous on July 18, 2010, 01:48:21 AM
Say, the last 6 hours? They seem few and far between, maybe just a couple per hour? Confirmations are taking a long time. Did the super node take his computers offline?

http://nullvoid.org/bitcoin/statistix.php

That says the last block was found over 50 minutes ago.

Maybe he pushed the difficulty level so high it will take a bit for the remaining nodes to generate?Apparently his supernode was doing the majority of the generating at one point.I would be interested if he posts on the forum or someone gets in contact with him how his experiment went?

 :D


Title: Re: Did block generation crawl to a halt?
Post by: mtgox on July 18, 2010, 01:50:42 AM
How often does the difficulty get adjusted?


Title: Re: Did block generation crawl to a halt?
Post by: Quantumplation on July 18, 2010, 03:23:03 AM
The difficulty gets reevaluated and adjusted every 2016 blocks.


Title: Re: Did block generation crawl to a halt?
Post by: MacRohard on July 18, 2010, 03:24:28 AM
I created a realtime graph of the current block generation speed here;

http://titania.smutfairy.com/~rm/time.gif


Title: Re: Did block generation crawl to a halt?
Post by: mtgox on July 18, 2010, 03:12:06 PM
MacRohard: Cool graph. It would be nice if it should time on the x axis and number of blocks on the y


Title: Re: Did block generation crawl to a halt?
Post by: satoshi on July 18, 2010, 11:35:27 PM
Nice graph!  A moving average to smooth it out would be nice.

http://nullvoid.org/bitcoin/statistix.php says 212 blocks in the last 24 hours, or 8.8 per hour.


Title: Re: Did block generation crawl to a halt?
Post by: lachesis on July 19, 2010, 12:28:24 AM
Satoshi, why does difficulty adjust so rarely? It would seem to me that it would be better to adjust once every 50 blocks or so.


Title: Re: Did block generation crawl to a halt?
Post by: MacRohard on July 19, 2010, 03:13:04 PM
@satoshi, I've change it to plot the last 127 blocks and also it gives you the average of those 127.


Title: Re: Did block generation crawl to a halt?
Post by: ByteCoin on July 19, 2010, 04:07:23 PM
Thanks for the statistics.

Transactions in block 68477 took under 3 minutes to get confirmed but transactions in block 68780 took over two hours!

The fact that a merchant can't tell a customer accurately how long they have to wait to get their goods will be a major barrier to adoption of the current scheme.

I think this is the most persuasive reason for changing to a fixed block generation scheme as outlined in

http://bitcointalk.org/index.php?topic=425.0

ByteCoin


Title: Re: Did block generation crawl to a halt?
Post by: FreeMoney on July 19, 2010, 10:20:52 PM
It's not that big of a deal really. When you buy something it often ships the next day. For trading on the exchanges the coins have already cleared so that isn't a problem either. I guess it could be annoying if you had to wait to get a software code or something instead of it being instant.


Title: Re: Did block generation crawl to a halt?
Post by: mizerydearia on July 20, 2010, 09:11:49 PM
I updated http://nullvoid.org/bitcoin/statistix.php

I determined that using timestamps generated from computer upon noticing a new block as discovered was unreliable: http://bitcointalk.org/index.php?topic=464.0

Statistics now use data directly from the database file block0001.dat

The code for statistix.php is documented at http://bitcointalk.org/index.php?topic=402.msg3395#msg3395

Interestingly, I notice that some blocks discovered have a negative time to discovery.

example:
Code:
 -116 seconds to find block 67591


Title: Re: Did block generation crawl to a halt?
Post by: Some Mouse on July 20, 2010, 09:39:21 PM
-186 seconds to find block 69275

heh.


Title: Re: Did block generation crawl to a halt?
Post by: mizerydearia on July 21, 2010, 12:43:28 AM
So maybe even the internal timestamps aren't reliable?