Edited ch10.asciidoc with Atlas code editor

7 years ago · f9f9fc8552
parent 74ae533fa2
commit f9f9fc8552
1 changed files with 1 additions and 1 deletions
--- a/ch10.asciidoc
+++ b/ch10.asciidoc
@ -908,7 +908,7 @@ While the consensus rules are invariable in the short term and must be consisten

 [[hard_forks]]
 ==== Hard Forks
-((("forks", "changing consensus rules", id="forks10a")))((("forks", "changing consesnsus rules", "hard forks")))In <<forks>> we looked at how the bitcoin network may briefly diverge, with two parts of the network following two different branches of the blockchain for a short time. We saw how this process occurs naturally, as part of the normal operation of the network and how the network reconverges on a common blockchain after one or more blocks are mined.
+((("forks", "changing consensus rules", id="forks10a")))((("forks", "changing consensus rules", "hard forks")))In <<forks>> we looked at how the bitcoin network may briefly diverge, with two parts of the network following two different branches of the blockchain for a short time. We saw how this process occurs naturally, as part of the normal operation of the network and how the network reconverges on a common blockchain after one or more blocks are mined.

 There is another scenario in which the network may diverge into following two chains: a change in the consensus rules. This type of fork is called a _hard fork_, because after the fork the network does not reconverge onto a single chain. Instead, the two chains evolve independently. Hard forks occur when part of the network is operating under a different set of consensus rules than the rest of the network. This may occur because of a bug or because of a deliberate change in the implementation of the consensus rules.