1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
|
Return-Path: <praveen.baratam@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 852B7BF7
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 20 Nov 2017 17:24:57 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4E7EF519
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 20 Nov 2017 17:24:55 +0000 (UTC)
Received: by mail-wm0-f53.google.com with SMTP id u83so11911397wmb.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 20 Nov 2017 09:24:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=FPz/lZ7SQus5/ge7G6tnWoaoZjmD8QnD6o1fnh9n8LE=;
b=vEmThmh2y5ZfcQ4REStPyY8IB5Qgs4YYY2CMrhZ6vWnbP8ulLumpIdpWyR1V8txdWH
SGOd59/iJao8CHY9p4z79fKOft+eeeipYbJIP6jybbmvmU9CUQHYow5Wt7ADgSbzgE03
1cZkwamELsIaw9DEqz+ZeQf56zx6WQyXF/b8OWaDTYSUp9SopbF52jCrMtJbEIo59xAq
1gINI2QlyN/o5eIcV06LYCuz8Y43GxQB+ZwVrF6i8fQklHONZ+ojx5nz4ntXsrdlzhDu
0YQbdG3vK+Qr0N9+P5Ozo9LMS15tJhIl4npfUKY2X460u1itQ1CR+csa3F71Pz9RHv3Z
8nPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=FPz/lZ7SQus5/ge7G6tnWoaoZjmD8QnD6o1fnh9n8LE=;
b=dxP43BRrq4eKT9PTHS2GiYhtAyemtuPqx8AXb98pbwRvGnxQY0iGgjoTgpvIevEUKO
r7TZ6vzo3n7nU5w63Rc9WXWUcriEEuZpQP/I4hTsQKNeeagSqAj1VysaMQVDaysPuyUo
hPjUdBif6d4TjTSZjATR9TSHbbfCVfck9pzt57ZEyGMEHiQs+rp8Xp0vWPUTDwnVzE5G
t5Ttzgo87fSv+fpVR7/TVKl1Y346VnaHCw9e87BnklOtVBqoh+zS7uWIi7Ocx/ZfUOk5
HObpIhfTX7C5RtwIDV8bM8ywkZWsLGEmovae2RKxk1/GKvcjWaC/jPeC8uxlkqa8Y3jP
u5jw==
X-Gm-Message-State: AJaThX64SDCdpVFaaad0xcvcyiWNhspGcjIR45yxdKNz08Hqxk21ni0M
GI3+cUt/0If6itHBrt1PyAzLHboJgnO/GQjpnvsj/Q==
X-Google-Smtp-Source: AGs4zMZFU1yzwv4gTCJQmxlGa078wWBHM9pizjHiENOeO9eAVGFnZNUTU4LH5G2P4wImTGxLFGymtqVQlQp/Ni3+iB0=
X-Received: by 10.28.212.69 with SMTP id l66mr10207275wmg.33.1511198693587;
Mon, 20 Nov 2017 09:24:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.225.6 with HTTP; Mon, 20 Nov 2017 09:24:33 -0800 (PST)
From: Praveen Baratam <praveen.baratam@gmail.com>
Date: Mon, 20 Nov 2017 22:54:33 +0530
Message-ID: <CAAQs3wuDPktHc6kiZXqTaatOheX4KP=TRgje0_-ED5h8iNs-MA@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary="001a11469a605101b1055e6d5dec"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Mon, 20 Nov 2017 17:29:18 +0000
Subject: [bitcoin-dev] Why SegWit Anyway?
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Nov 2017 17:24:57 -0000
--001a11469a605101b1055e6d5dec
Content-Type: text/plain; charset="UTF-8"
Bitcoin Noob here. Please forgive my ignorance.
From what I understand, in SegWit, the transaction needs to be serialized
into a data structure that is different from the current one where
signatures are separated from the rest of the transaction data.
Why change the format at all? Why cant we just compute the Transaction ID
the same way the hash for signing the transaction is computed?
--
Dr. Praveen Baratam
about.me <http://about.me/praveen.baratam>
--001a11469a605101b1055e6d5dec
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><span style=3D"font-family:Verdana,arial,sans-serif;f=
ont-size:14px">Bitcoin Noob here. Please forgive my ignorance.</span></div>=
<span style=3D"font-family:Verdana,arial,sans-serif;font-size:14px"><div><s=
pan style=3D"font-family:Verdana,arial,sans-serif;font-size:14px"><br></spa=
n></div>From what I understand, in SegWit, the transaction needs to be seri=
alized into a data structure that is different from the current one where s=
ignatures are separated from the rest of the transaction data.</span><div><=
span style=3D"font-family:Verdana,arial,sans-serif;font-size:14px"><br></sp=
an></div><div><span style=3D"font-family:Verdana,arial,sans-serif;font-size=
:14px">Why change the format at all? Why cant we just compute the Transacti=
on ID the same way the hash for signing the transaction is computed?</span>=
<br clear=3D"all"><div><br></div>-- <br><div class=3D"gmail_signature"><div=
style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;b=
ackground-color:rgb(255,255,255)">Dr. Praveen Baratam</div><div style=3D"co=
lor:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-co=
lor:rgb(255,255,255)"><br></div><div style=3D"color:rgb(34,34,34);font-fami=
ly:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><a hr=
ef=3D"http://about.me/praveen.baratam" style=3D"color:rgb(17,85,204)" targe=
t=3D"_blank">about.me</a></div></div>
</div></div>
--001a11469a605101b1055e6d5dec--
|
