da2ce7 (OP)
Legendary
Offline
Activity: 1222
Merit: 1012
Live and Let Live


November 07, 2010, 05:27:31 AM 

How does one calculate the average block generation time at any given difficulty factor?
Thanks in advanced.

One off NPHard.





"If you don't want people to know you're a scumbag then don't be a scumbag."  margaritahuyan



Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.


ShadowOfHarbringer
Legendary
Offline
Activity: 1470
Merit: 1004
Bringing Legendary Har® to you since 1952


November 07, 2010, 01:00:46 PM 





tcatm


November 07, 2010, 01:09:18 PM 

Average Time = difficulty * 2^32 * hour / (3600 * hashrate)




da2ce7 (OP)
Legendary
Offline
Activity: 1222
Merit: 1012
Live and Let Live


November 08, 2010, 09:55:39 AM 


One off NPHard.



Transisto
Donator
Legendary
Offline
Activity: 1731
Merit: 1001


March 09, 2011, 07:34:53 PM 

Average Time = difficulty * 2^32 * hour / (3600 * hashrate)
Average Time (in hours) = difficulty * 2^32 *hour / (3600 * hash per second)





Kinnardian
Newbie
Offline
Activity: 38
Merit: 0


November 28, 2012, 09:57:11 PM 

Hi, Where does the 2^32 come from?




Sparxy
Newbie
Offline
Activity: 8
Merit: 0


November 29, 2012, 12:47:29 AM 

Hi, Where does the 2^32 come from?
The nonce for the block "candidate" is a 32bit integer, meaning it can be anything from 0 to 2^32. While mining, you'll iterate through every single possibility before beginning on a new block "candidate".




CrazyGuy
Legendary
Offline
Activity: 1973
Merit: 1006


November 30, 2012, 06:30:14 PM 

I didn't know you could create widgets with wolfram, that's really neat. So if 250 th worth of ASICs were released today , it would take about 40h to chomp through 2000 blocks.

ASICPuppy.net ASIC Mining Hardware and Accessories  Compac F in stock!



PaperClip
Newbie
Offline
Activity: 56
Merit: 0


June 26, 2013, 09:06:42 PM 

I have question raised from different topic  Solo mining, no change in total network hash rate, 20 hours a day for 62 days, then you have what percentage of finding a block??
According to this: https://en.bitcoin.it/wiki/Difficultytime required to find a block = difficulty * 2^48 / 65535 / hashrate difficulty = 19339258.272387 hashrate = 7.75 GH/s = 7 750 000 000 hash/s time required to find a block = 19 339 258.272 387 * 2^48 / 65 535 / 7 750 000 000 = 10 717 774 s 20 hours a day for 62 days equals to 4 464 000 seconds result is 4 464 000 / 10 717 774 = 41.65%But I have some concerns: Actually, result percentage should be bigger. 10717774s is maximal time to check all possible hashes. In reality miner does not check them all, it stops as soon as correct hash was found. Its like if somebody has number between 1 and 9 in his mind, and you will guess it by trying all numbers 1,2,3,.. sequently. You do not need to make 9 guesses every time. It will be from 1 to 9; 5 guesses in average. Soo, in this case result percentage should be 2 times bigger  83.3%. Am I correct? I want to understand logic behind this. Can anybody help? Correct result is 41.65% or 83.3%?




farlack
Legendary
Offline
Activity: 1311
Merit: 1000


June 26, 2013, 09:32:36 PM 

Anyone else notice the block times you will get 2 in 2 minutes, then none for 30 minutes, its really annoying.




cp1


June 26, 2013, 09:33:42 PM 

Average block time = time for last n blocks / n




jackjack
Legendary
Offline
Activity: 1176
Merit: 1185
May Bitcoin be touched by his Noodly Appendage


June 26, 2013, 09:37:34 PM 

Anyone else notice the block times you will get 2 in 2 minutes, then none for 30 minutes, its really annoying.
Fucking maths, how do they work?

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.



PaperClip
Newbie
Offline
Activity: 56
Merit: 0


June 26, 2013, 09:49:53 PM 

Average block time = time for last n blocks / n
True But question was related to device that probobaly will take months to generate at least one block So there is no "time for last n blocks" in this case




cp1


June 26, 2013, 10:18:34 PM 

But question was related to device that probobaly will take months to generate at least one block So there is no "time for last n blocks" in this case I didn't realize the thread was from so long ago either.




AnonyMint


November 12, 2013, 12:39:15 AM 

Hi, Where does the 2^32 come from?
The nonce for the block "candidate" is a 32bit integer, meaning it can be anything from 0 to 2^32. While mining, you'll iterate through every single possibility before beginning on a new block "candidate". Incorrect. The maximum target* is 0x00000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF, which has 8 zeros at 4 bits each (each hexadecimal digit has pow(2,4) = 2^4 = 16 possibilities: 0  9, A, B, C, D, E, and F). 8 x 4 = 32 bits. The probability of finding a hash which is 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF divided by 0x00000000FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF = 1/pow(2,32) = 1 / (2^32). Since the difficulty is the maximum target divided by current target, each hash calculated has 1 / (2^32) probability of being the block solution when the difficulty is 1. This choice of the maximum target for Bitcoin just so happens to match the number of possible values for the block nonce. * Note the maximum target is rounded down to 0x00000000FFFF0000000000000000000000000000000000000000000000000000, so all the math presented in this thread is only an approximation.




lcharles123
Legendary
Offline
Activity: 1693
Merit: 1064


December 25, 2013, 10:28:10 PM 





