mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-12-25 16:08:13 +00:00
Edited ch12_mining.adoc with Atlas code editor
This commit is contained in:
parent
926ea797f5
commit
74590a642b
@ -1629,7 +1629,7 @@ between all participants.
|
|||||||
[[hard_forks]]
|
[[hard_forks]]
|
||||||
==== Hard Forks
|
==== Hard Forks
|
||||||
|
|
||||||
In <<forks>> we looked at how
|
In <<forks>> we looked((("consensus rules", "hard forks", id="consensus-hard-fork")))((("forks", "hard forks", id="forks-hard")))((("hard forks", id="hard-forks"))) at how
|
||||||
the Bitcoin network may briefly diverge, with two parts of the network
|
the Bitcoin network may briefly diverge, with two parts of the network
|
||||||
following two different branches of the blockchain for a short time. We
|
following two different branches of the blockchain for a short time. We
|
||||||
saw how this process occurs naturally, as part of the normal operation
|
saw how this process occurs naturally, as part of the normal operation
|
||||||
@ -1754,7 +1754,7 @@ New miners may mine on top of the new block,
|
|||||||
while old miners will mine a separate chain based on the old rules. The
|
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
|
partitioned network will make it so that the miners operating on
|
||||||
separate consensus rules won't likely receive each other's blocks, as
|
separate consensus rules won't likely receive each other's blocks, as
|
||||||
they are connected to two separate networks.
|
they are connected to two separate ((("consensus rules", "hard forks", startref="consensus-hard-fork")))((("forks", "hard forks", startref="forks-hard")))((("hard forks", startref="hard-forks")))networks.
|
||||||
|
|
||||||
==== Diverging Miners and Difficulty
|
==== Diverging Miners and Difficulty
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user