From 6f55743990cd0eadc80f3105520454e25477293c Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 01:43:44 +0000 Subject: [PATCH] Edited ch06_transactions.adoc with Atlas code editor --- ch06_transactions.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc index 79239ab7..e2ed89e7 100644 --- a/ch06_transactions.adoc +++ b/ch06_transactions.adoc @@ -931,12 +931,12 @@ a txid is called _segregated witness_ (segwit). The obvious method for implementing segwit requires a change to Bitcoin's consensus rules that would not be compatible with -older full nodes, also called +older full nodes, also ((("hard forks")))((("forks", "hard")))called a _hard fork_. Hard forks come with a lot of challenges, as we'll discuss further in <>. An alternative approach to segwit was described in late 2015. This -would use a backward-compatible change to the consensus rules, called a +would use a backward-compatible change to the consensus rules, ((("soft forks")))((("forks", "soft")))called a _soft fork_. Backward compatible means that full nodes implementing the change must not accept any blocks that full nodes without the change would consider invalid. As long as they obey that rule, newer full