0
Here is what I have estimates on: There exists hardware capable of 60 gigahashes per second. Over the next few months, X amount of these will be mining bitcoins.
Difficulty is recalculated every 2016 blocks. X * 60,000 megahashes = Y terahashes to total mining.
At current difficulty it will take a machine calculating at 60 gigahashes about 3.6 days to solve 1 block. With just 700 of these machines each solving 1 block every 3.6 days, difficulty will be at Z within a week, where difficulty is then recalculated to even out the time period of solving blocks (if I understand correctly).
The variable I have is about what the implications are of the algorithm for difficulty. Is it intended for there to only be a finite number of blocks solved in a certain timeframe?
Okay, so I believe
516355284882773000000.00will be the difficulty once 600 new machines processing at 60 gigahashes/sec come online. Does this look correct to you? I simply added it to an existing hashrate of 3.6134E+13 and it doens't take into account a drop in participants – CQM – 2013-03-13T02:22:10.0501@CQM - I do not see how you are getting that result. Doing (600(34Thash+36Thash))/2^32, I get 9,778,887. 34Thash is the current rate and 36Thash is 60Ghash600. It's somewhat more than double the current difficulty (4,367,876), which is what one would expect from somewhat more than doubling of the network hashing rate. – Compro01 – 2013-03-13T14:26:09.183