You've already forked nakamoto-archive
Create 56.md
This commit is contained in:
@@ -0,0 +1,24 @@
|
||||
---
|
||||
layout: forum
|
||||
title: 'Re: Proof-of-work difficulty increasing'
|
||||
grand_parent: Forum Posts
|
||||
parent: Bitcoin Forum
|
||||
nav_order: 56
|
||||
date: 2010-02-16 17:36:40 UTC
|
||||
original: https://bitcointalk.org/index.php?topic=43.msg376#msg376
|
||||
---
|
||||
|
||||
# Re: Proof-of-work difficulty increasing
|
||||
---
|
||||
|
||||
<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight">
|
||||
<code>Re: Proof-of-work difficulty increasing
|
||||
February 16, 2010, 05:36:40 PM
|
||||
|
||||
<a href="https://bitcointalk.org/index.php?topic=43.msg361#msg361">Quote from: Suggester on February 16, 2010, 02:15:49 AM</a>
|
||||
-------------
|
||||
Satoshi, I figured it will take my modern core 2 duo about 20 hours of nonstop work to create ฿50.00! With older PCs it will take forever. People like to feel that they "own" something as soon as possible, is there a way to make the generation more divisible? So say, instead of making ฿50 every 20 hours, make ฿5 every 2 hours?
|
||||
-------------
|
||||
I thought about that but there wasn't a practical way to do smaller increments. The frequency of block generation is balanced between confirming transactions as fast as possible and the latency of the network.
|
||||
|
||||
The algorithm aims for an average of 6 blocks per hour. If it was 5 bc and 60 per hour, there would be 10 times as many blocks and the initial block download would take 10 times as long. It wouldn't work anyway because that would be only 1 minute average between blocks, too close to the broadcast latency when the network gets larger.</code></pre></div></div>
|
||||
Reference in New Issue
Block a user