From 4c9e8553e5a4434f88f1ebf8747fd9d215f854c2 Mon Sep 17 00:00:00 2001 From: "Andreas M. Antonopoulos" Date: Tue, 18 Jul 2017 11:39:24 +0800 Subject: [PATCH] typo --- appdx-segwit.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/appdx-segwit.asciidoc b/appdx-segwit.asciidoc index 99f0e116..37086cf9 100644 --- a/appdx-segwit.asciidoc +++ b/appdx-segwit.asciidoc @@ -10,7 +10,7 @@ In the context of bitcoin, a digital signature is _one type of witness_, but a w Before segwit’s introduction, every input in a transaction was followed by the witness data that unlocked it. The witness data was embedded in the transaction as part of each input. The term _segregated witness_, or _segwit_ for short, simply means separating the signature or unlocking script of a specific output. Think "separate scriptSig," or “separate signature” in the simplest form. -Segregated Witness therefore is an architectural change to bitcoin that aims to move the witness data from the +scriptSig+ (unlocking script) field of a transaction into a separate a _witness_ data structure that accompanies a transaction. Clients may request transaction data with or without the accompanying witness data. +Segregated Witness therefore is an architectural change to bitcoin that aims to move the witness data from the +scriptSig+ (unlocking script) field of a transaction into a separate _witness_ data structure that accompanies a transaction. Clients may request transaction data with or without the accompanying witness data. In this section we will look at some of the benefits of Segregated Witness, describe the mechanism used to deploy and implement this architecture change, and demonstrate the use of Segregated Witness in transactions and addresses.