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
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
|
Return-Path: <morcos@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 32709B57
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 17 Nov 2016 01:24:51 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-it0-f49.google.com (mail-it0-f49.google.com
[209.85.214.49])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A2900148
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 17 Nov 2016 01:24:50 +0000 (UTC)
Received: by mail-it0-f49.google.com with SMTP id c20so39862037itb.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 16 Nov 2016 17:24:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=b/P/e+dsjtVutMphLDdJdi/Z2W4qVHHU4dCC+fpVjSw=;
b=j+VNarBYTcS0x/V0//Y3yrdARrUxRL7CElMJDvvqONboKodAK+cnvBvCZHjQ9IO8Zn
JOSa4O25OjAqIRpHVY5KKy937ly/b84MpyWv2OCjqUE6d+Ef+dQjPIfxgJsp5ZYwyVvT
5d0LwoNI9CoT6I3tbvr7pu8IBH2VZPLB4Pwyv5BJ5jb4Xregpk5dW39ceaY9R9MgwugP
DNcwZx8kAtZArzHGloo4h/BpbNGlUC9o8ZOpcAual5MZ2UQXMBW0fDMUHZ2UaaiTkKge
a3ogUxfriFh9gPzLgoR9CePuE7Yr+lwcE4Hlxvw/uvY0D0M0lahYau9C+4Fv4ZHDHZtT
RNuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=b/P/e+dsjtVutMphLDdJdi/Z2W4qVHHU4dCC+fpVjSw=;
b=Xnj42tTbXZdt3eJ95ycWG8vARY168AYrrRqpdydFUrxzrjCrhfimRp99ZMd7yuKETv
ui03k02EGQs44NUiqMd6JHRqdkTRUDWOt84PyvARos0tUsEAG83nAqYe1B+UEjk9gnTZ
7XqLzvyarVD7+9LhG3AkCK0axXGjuOfPNzqDA6aNd/j8mpwtNpTMj2UNBlJl1bRnJoBg
3qRf1ygK0uZloAHcyZ9/cPqHNZGhMZJY7w0AAt+dkN+iwiM/ctdgt8ZvbqNnm6oW9p13
81nb6OEDYXUYPpw6/xcG+75oJP2GmT5/GxVs0yqSXk0xN6ifyqfik+p+UPDs6MJZLiCn
kzHQ==
X-Gm-Message-State: ABUngvdxMgw3kLtJIEoaJyO0v+t1zo6q21CMkBhpiBloOVrRRiv7qN1X+cIX4XnC5oCZvcE/hnVc5ARMwDArKg==
X-Received: by 10.36.31.200 with SMTP id d191mr9860044itd.70.1479345889947;
Wed, 16 Nov 2016 17:24:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.119.199 with HTTP; Wed, 16 Nov 2016 17:24:49 -0800 (PST)
In-Reply-To: <6191e5f2-4cc7-b3ff-b4e7-bb7979e24d1f@voskuil.org>
References: <CAFp6fsGmynRXLCqKAA+iBXObGOZ2h3DVW8k5L9kSfbPmL1Y-QQ@mail.gmail.com>
<CEDAD65E-512A-43CA-9BD6-56F7D9E6897C@voskuil.org>
<CADJgMzunxU2-7Z_ZPafNY4BPRu0x9oeh6v2dg0nUYqxJbXeGYA@mail.gmail.com>
<33BFC318-0BB4-48DB-B5DC-08247FAC6E5A@voskuil.org>
<CADL_X_dJ8YuDevKR4xA+PTy9D089dAeZ1F3ZwSYG6MrMvkLweg@mail.gmail.com>
<A98BB7F2-7AE2-4D84-9F38-7E7E9D5D3210@voskuil.org>
<e86b5b85-591d-5342-6a75-3ebd501f1789@thomaskerin.io>
<CABm2gDqy+iBdw3W2dap8rdi5TD-5_VSmFnakvEbYeAtgpdLgMg@mail.gmail.com>
<6191e5f2-4cc7-b3ff-b4e7-bb7979e24d1f@voskuil.org>
From: Alex Morcos <morcos@gmail.com>
Date: Wed, 16 Nov 2016 20:24:49 -0500
Message-ID: <CAPWm=eWcZZCzKWXkX=sD=cnjTCEGmdN3G_hf85rwy60EAUXUqQ@mail.gmail.com>
To: Eric Voskuil <eric@voskuil.org>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11446e864536bc0541750e5e
X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_LOW,
RCVD_IN_SORBS_SPAM autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Thomas Kerin <me@thomaskerin.io>
Subject: Re: [bitcoin-dev] [BIP Proposal] Buried Deployments
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: Thu, 17 Nov 2016 01:24:51 -0000
--001a11446e864536bc0541750e5e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
huh?
can you give an example of how a duplicate transaction hash (in the same
chain) can happen given BIP34?
On Wed, Nov 16, 2016 at 7:00 PM, Eric Voskuil via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On 11/16/2016 03:58 PM, Jorge Tim=C3=B3n via bitcoin-dev wrote:
> > On Wed, Nov 16, 2016 at 3:18 PM, Thomas Kerin via bitcoin-dev
> > <bitcoin-dev@lists.linuxfoundation.org> wrote:
> >> BIP30 actually was given similar treatment after a reasonable amount o=
f
> time
> >> had passed.
> >> https://github.com/bitcoin/bitcoin/blob/master/src/main.cpp#L2392
> >
> > This is not really the same. BIP30 is not validated after BIP34 is
> > active because blocks complying with BIP34 will always necessarily
> > comply with BIP30 (ie coinbases cannot be duplicated after they
> > include the block height).
>
> This is a misinterpretation of BIP30. Duplicate transaction hashes can
> and will happen and are perfectly valid in Bitcoin. BIP34 does not
> prevent this.
>
> e
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--001a11446e864536bc0541750e5e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">huh?<div>can you give an example of how a duplicate transa=
ction hash (in the same chain) can happen given BIP34? =C2=A0=C2=A0</div><d=
iv><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On Wed, Nov 16, 2016 at 7:00 PM, Eric Voskuil via bitcoin-dev <span dir=
=3D"ltr"><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" targe=
t=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>></span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><span class=3D"">On 11/16/2016 03:58 PM, Jo=
rge Tim=C3=B3n via bitcoin-dev wrote:<br>
> On Wed, Nov 16, 2016 at 3:18 PM, Thomas Kerin via bitcoin-dev<br>
> <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-d=
ev@lists.<wbr>linuxfoundation.org</a>> wrote:<br>
>> BIP30 actually was given similar treatment after a reasonable amou=
nt of time<br>
>> had passed.<br>
>> <a href=3D"https://github.com/bitcoin/bitcoin/blob/master/src/main=
.cpp#L2392" rel=3D"noreferrer" target=3D"_blank">https://github.com/bitcoin=
/<wbr>bitcoin/blob/master/src/main.<wbr>cpp#L2392</a><br>
><br>
> This is not really the same. BIP30 is not validated after BIP34 is<br>
> active because blocks complying with BIP34 will always necessarily<br>
> comply with BIP30 (ie coinbases cannot be duplicated after they<br>
> include the block height).<br>
<br>
</span>This is a misinterpretation of BIP30. Duplicate transaction hashes c=
an<br>
and will happen and are perfectly valid in Bitcoin. BIP34 does not<br>
prevent this.<br>
<br>
e<br>
<br>
<br>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
<br></blockquote></div><br></div>
--001a11446e864536bc0541750e5e--
|
