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
110
111
112
|
Return-Path: <tier.nolan@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 2E22D25A
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 19 Oct 2015 15:23:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qg0-f48.google.com (mail-qg0-f48.google.com
[209.85.192.48])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C382F16F
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 19 Oct 2015 15:23:54 +0000 (UTC)
Received: by qgeo38 with SMTP id o38so116199133qge.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 19 Oct 2015 08:23:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:cc
:content-type; bh=pZVVSY9a1eVNUJcUBAxx2cT9QfN3wvK90UIYsQ6Eyq8=;
b=XYP/TL89auy4i83HW0KJbKU3or7BKAPA3Otw9dVO3gX8iljS+J4r5SRJK0RhFq681F
J+0aR9+3mGh9V+hnwJL1ZECsI7l9urzs5q45RbmrGcsX+mTjrByJ2Oq/czhZVaOwqCfV
wKPQmWOgY2NTIPJ5r0k+pTjEtsYC5FXAh+69hNF+V/tWmwyOooAKxqjH9bFTO2MXVVuC
LqT5Wul+SWK69eIA1C8Wmso1KKNFZmoXjEL65Pj/8/LFZMSuNINp/SUSgXMEoT/Jdi6N
GhUJflrjyul64TTtT+6yMFgta/S3MK/SNWnw3FDVLo5El/+nk2JKm2+nEuIJsS09xeJ8
/1dw==
MIME-Version: 1.0
X-Received: by 10.140.151.73 with SMTP id 70mr39827372qhx.36.1445268233991;
Mon, 19 Oct 2015 08:23:53 -0700 (PDT)
Received: by 10.140.30.201 with HTTP; Mon, 19 Oct 2015 08:23:53 -0700 (PDT)
In-Reply-To: <CALxbBHU+kdEAh_4+B663vknAAr8OKZpUzVTACORPZi47E=Ehkw@mail.gmail.com>
References: <CALxbBHU+kdEAh_4+B663vknAAr8OKZpUzVTACORPZi47E=Ehkw@mail.gmail.com>
Date: Mon, 19 Oct 2015 16:23:53 +0100
Message-ID: <CAE-z3OUrM=0XsdfdU2d9h6uhCh9vP83X-OZR8NyAYsvYuE1vtg@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11353a48b141e8052276bba6
X-Spam-Status: No, score=0.5 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
MALFORMED_FREEMAIL,
MISSING_HEADERS,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] [BIP] Normalized transaction IDs
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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, 19 Oct 2015 15:23:55 -0000
--001a11353a48b141e8052276bba6
Content-Type: text/plain; charset=UTF-8
On Mon, Oct 19, 2015 at 3:01 PM, Christian Decker via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> As with the previous version, which was using a hard-fork, the normalized
> transaction ID is computed only considering the non-malleable parts of a
> transaction, i.e., stripping the signatures before computing the hash of
> the transaction.
> <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>
Is this proposal recursive?
*Coinbase transaction *
* n-txid = txid
*Non-coinbase transactions*
* replace sigScripts with empty strings
* replace txids in TxIns with n-txid for parents
The 2nd step is recursive starting from the coinbases.
In effect, the rule is that txids are what they would have been if n-txids
had been used right from the start.
--001a11353a48b141e8052276bba6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Oct 19, 2015 at 3:01 PM, Christian Decker via bitcoin-dev <span dir=3D"=
ltr"><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D=
"_blank">bitcoin-dev@lists.linuxfoundation.org</a>></span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>As with the previous vers=
ion, which was using a hard-fork, the normalized transaction ID is computed=
only considering the non-malleable parts of a transaction, i.e., stripping=
the signatures before computing the hash of the transaction. <br></div></d=
iv><a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-de=
v" rel=3D"noreferrer" target=3D"_blank"></a></blockquote><div><br></div><di=
v>Is this proposal recursive?=C2=A0 <br><br></div><div><b>Coinbase transact=
ion <br></b></div><div><br>* n-txid =3D txid<br></div></div><br></div><div =
class=3D"gmail_extra"><b>Non-coinbase transactions<br></b><br></div><div cl=
ass=3D"gmail_extra">* replace sigScripts with empty strings<br></div><div c=
lass=3D"gmail_extra">* replace txids in TxIns with n-txid for parents<br><b=
r></div><div class=3D"gmail_extra">The 2nd step is recursive starting from =
the coinbases.<br></div><div class=3D"gmail_extra"><br></div><div class=3D"=
gmail_extra">In effect, the rule is that txids are what they would have bee=
n if n-txids had been used right from the start.<br></div></div>
--001a11353a48b141e8052276bba6--
|
