Bitcoin Forum
November 08, 2024, 06:09:56 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: QUESTION: Block Time Vs Difficulty - Pardon My Ignorance On the Subject  (Read 5229 times)
thekidcoin (OP)
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250

FlutterCoin Developer


View Profile
June 07, 2013, 01:52:47 PM
 #1

So we have seen coins with 1 minute or less block times with orphans.

Whats not clicking for me is this: at 15 difficulty  for example and a 1 second block time (just an example, could be 10, 20, 30 whatever), blocks won't be mined every second unless the hash rate if super high right?  Or am I mistaken?

Also what does mining difficulty do to the speed of transactions?  Or is the speed of transactions based solely upon nodes confirmation of the transaction? 

So you have shiny new your orphanfest 1 second block time coin, difficulty is 15, and the hashrate is around 30 mH/s, and if the above is true that blocks aren't mined every second anymore, does that mean your blazing fast 6 second confirmation is out the window?



1MYL967PR52xiNtqSP9WphRvPzKZDjBdxn
Rannasha
Hero Member
*****
Offline Offline

Activity: 728
Merit: 500


View Profile
June 07, 2013, 03:25:49 PM
 #2

The difficulty determines how fast blocks are mined and therefore how many orphans there are. Low diff = easy to find blocks = large chance of orphans.

The target block time is the desired average time between blocks. The difficulty has to be readjusted periodically to ensure that the actual time between blocks matches the target time. Network hashrate goes up -> difficulty goes up at the next readjustment.

In a stable situation (constant hashrate), a coin with a 5 second target block time will have a difficulty 60 times lower than a coin with a 5 minute target block time if both coins have the same network hashrate. Superfast coins will always have orphans, because they are designed to have blocks generated very quickly.

If the difficulty does not match the target block time, the time for transactions to confirm will also change. A coin that requires 6 confirms and has a 1 min target block time should normally confirm in ~6 minutes. If the network hashrate now drops by 50%, blocks will trickle in at half the pace, so getting those 6 confirms will take ~12 minutes on average. That is, until the next difficulty readjustment. Here also lies the problem with slowly adjusting coins: If the network hashrate drops a lot (which is common for altcoins as the large miners switch to the newest coin), it can take a very long time before the difficulty is adjusted downward, since readjustment-periods are typically specified in block-counts rather than in time-periods.
thekidcoin (OP)
Sr. Member
****
Offline Offline

Activity: 308
Merit: 250

FlutterCoin Developer


View Profile
June 07, 2013, 03:34:45 PM
 #3

Ahh cool thanks I got it now...  The difficulty algo always try to match the difficulty and hashrate so the desired time of x minutes/seconds block time is hit.


1MYL967PR52xiNtqSP9WphRvPzKZDjBdxn
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!