Bitcoin Forum
May 22, 2024, 06:11:51 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Theoretically, what would happen if....?  (Read 868 times)
gravityz3r0 (OP)
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 10, 2014, 09:06:59 AM
 #1

There's only one block remains before next difficulty and suddenly everybody stop mining and wait for the 14 days to lapse. Let the next difficulty to readjust lower, then everybody start mining again the next 2016 blocks without an increase in difficulty. Rinse and repeat. Of course, not possible in practical..but what if?  Roll Eyes

14 days is the time taken by bitcoin system during an 'ideal' condition for all 2016 blocks to be mined out. Anything less, difficulty will be readjusted to match the global hashrate to bring it back to 14 days cycle. Anything more, difficulty will be lowered accordingly. Unless my understanding is wrong :S
ning
Full Member
***
Offline Offline

Activity: 173
Merit: 100



View Profile
January 10, 2014, 09:36:33 AM
 #2

Ever seen the movie Jurassic Park? "Life will find its way out." Wink
FenixRD
Sr. Member
****
Offline Offline

Activity: 364
Merit: 250


I am Citizenfive.


View Profile
January 10, 2014, 09:40:53 AM
 #3

There's only one block remains before next difficulty and suddenly everybody stop mining and wait for the 14 days to lapse. Let the next difficulty to readjust lower, then everybody start mining again the next 2016 blocks without an increase in difficulty. Rinse and repeat. Of course, not possible in practical..but what if?  Roll Eyes

14 days is the time taken by bitcoin system during an 'ideal' condition for all 2016 blocks to be mined out. Anything less, difficulty will be readjusted to match the global hashrate to bring it back to 14 days cycle. Anything more, difficulty will be lowered accordingly. Unless my understanding is wrong :S

The 14 days IS the 2016 blocks. There is no time ticking by (other than for timestamps). If you stopped at 2015th block, it wouldn't readjust until the 2016th. Then it would take the average time of all 2016, and set the new difficulty so that the *average hashrate* of the previous 2016, results in 10 minute (avg.) blocks.

There's nothing to be gained. Either the average increased, or decreased, or stayed the same, but it makes no difference if it's 10 TH/s that works full time or 100 TH/s working 10% of the time. The difficulty will be the same.

Uberlurker. Been here since the Finney transaction. Please consider this before replying; there is a good chance I've heard it before.

-Citizenfive
gravityz3r0 (OP)
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
January 10, 2014, 09:59:33 AM
 #4

There's only one block remains before next difficulty and suddenly everybody stop mining and wait for the 14 days to lapse. Let the next difficulty to readjust lower, then everybody start mining again the next 2016 blocks without an increase in difficulty. Rinse and repeat. Of course, not possible in practical..but what if?  Roll Eyes

14 days is the time taken by bitcoin system during an 'ideal' condition for all 2016 blocks to be mined out. Anything less, difficulty will be readjusted to match the global hashrate to bring it back to 14 days cycle. Anything more, difficulty will be lowered accordingly. Unless my understanding is wrong :S

The 14 days IS the 2016 blocks. There is no time ticking by (other than for timestamps). If you stopped at 2015th block, it wouldn't readjust until the 2016th. Then it would take the average time of all 2016, and set the new difficulty so that the *average hashrate* of the previous 2016, results in 10 minute (avg.) blocks.

There's nothing to be gained. Either the average increased, or decreased, or stayed the same, but it makes no difference if it's 10 TH/s that works full time or 100 TH/s working 10% of the time. The difficulty will be the same.

Answered clear as crystal, thank you sir!
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!