|
|
|
@ -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 ((("hard forks")))((("forks", "hard")))called
|
|
|
|
|
older full nodes, also ((("hard forks")))((("forks", "hard forks")))called
|
|
|
|
|
a _hard fork_. Hard forks come with a lot of challenges, as we'll
|
|
|
|
|
discuss further in <<hard_forks>>.
|
|
|
|
|
|
|
|
|
|
An alternative approach to segwit was described in late 2015. This
|
|
|
|
|
would use a backward-compatible change to the consensus rules, ((("soft forks")))((("forks", "soft")))called a
|
|
|
|
|
would use a backward-compatible change to the consensus rules, ((("soft forks")))((("forks", "soft forks")))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
|
|
|
|
|