mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2025-01-12 00:31:06 +00:00
Edited ch12_mining.adoc with Atlas code editor
This commit is contained in:
parent
499f68b2fb
commit
5db6fa31ff
@ -1697,7 +1697,7 @@ appears to be an invalid block, as its parent "7b" is not recognized as a
|
||||
|
||||
==== Hard Forks: Software, Network, Mining, and Chain
|
||||
|
||||
For ((("software forks", id="software-fork")))((("network forks", id="network-fork")))((("mining forks", id="mining-fork")))((("chain forks", id="chain-fork")))((("consensus rules", "hard forks", "types of", id="consensus-hard-fork")))((("forks", "hard forks", "types of", id="forks-hard")))((("hard forks", "types of", id="hard-forks")))software
|
||||
For ((("software forks", id="software-fork")))((("network forks", id="network-fork")))((("mining forks", id="mining-fork")))((("chain forks", id="chain-fork")))((("consensus rules", "hard forks", "types of", id="consensus-hard-fork-type")))((("forks", "hard forks", "types of", id="forks-hard-type")))((("hard forks", "types of", id="hard-forks-type")))software
|
||||
developers, the term "fork" has another meaning, adding confusion to the
|
||||
term "hard fork." In open source software, a fork occurs when a group of
|
||||
developers choose to follow a different software roadmap and start a
|
||||
@ -1754,11 +1754,11 @@ New miners may mine on top of the new block,
|
||||
while old miners will mine a separate chain based on the old rules. The
|
||||
partitioned network will make it so that the miners operating on
|
||||
separate consensus rules won't likely receive each other's blocks, as
|
||||
they are connected to two separate ((("software forks", startref="software-fork")))((("network forks", startref="network-fork")))((("mining forks", startref="mining-fork")))((("chain forks", startref="chain-fork")))((("consensus rules", "hard forks", "types of", startref="consensus-hard-fork")))((("forks", "hard forks", "types of", startref="forks-hard")))((("hard forks", "types of", startref="hard-forks")))networks.
|
||||
they are connected to two separate ((("software forks", startref="software-fork")))((("network forks", startref="network-fork")))((("mining forks", startref="mining-fork")))((("chain forks", startref="chain-fork")))((("consensus rules", "hard forks", "types of", startref="consensus-hard-fork-type")))((("forks", "hard forks", "types of", startref="forks-hard-type")))((("hard forks", "types of", startref="hard-forks-type")))networks.
|
||||
|
||||
==== Diverging Miners and Difficulty
|
||||
|
||||
As miners diverge into mining two different chains, the
|
||||
As miners ((("consensus rules", "hard forks", "difficulty and", id="consensus-hard-fork-difficult")))((("forks", "hard forks", "difficulty and", id="forks-hard-difficult")))((("hard forks", "difficulty and", id="hard-forks")))((("difficulty", "hard forks and", id="difficulty-hardfork")))diverge into mining two different chains, the
|
||||
hashing power is split between the chains. The mining power can be split
|
||||
in any proportion between the two chains. The new rules may only be
|
||||
followed by a minority, or by the vast majority of the mining power.
|
||||
@ -1786,7 +1786,7 @@ blocks will now be mined every 50 minutes on average. The difficulty
|
||||
will not be adjusted for 2,016 blocks, which will take 100,800 minutes,
|
||||
or approximately 10 weeks to mine. Assuming a fixed capacity per block,
|
||||
this will also result in a reduction of transaction capacity by a factor
|
||||
of 5, as there are fewer blocks per hour available to record
|
||||
of 5, as there are fewer blocks per hour available to record((("consensus rules", "hard forks", "difficulty and", startref="consensus-hard-fork-difficult")))((("forks", "hard forks", "difficulty and", startref="forks-hard-difficult")))((("hard forks", "difficulty and", startref="hard-forks")))((("difficulty", "hard forks and", startref="difficulty-hardfork")))
|
||||
transactions.
|
||||
|
||||
==== Contentious Hard Forks
|
||||
|
Loading…
Reference in New Issue
Block a user