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
|
Return-Path: <slashene@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 4C817CEA
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 9 Feb 2016 12:32:27 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qg0-f51.google.com (mail-qg0-f51.google.com
[209.85.192.51])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DB69C100
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 9 Feb 2016 12:32:26 +0000 (UTC)
Received: by mail-qg0-f51.google.com with SMTP id b35so138604683qge.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 09 Feb 2016 04:32:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:sender:from:date:message-id:subject:to:content-type;
bh=h0vWOyLr6erGPQyLFomgnIZPW13gQsewQVBSSKm6yB8=;
b=CTT1m/J1j4YF31w8OFfizE6do//vn9CBKzbE9kGxmzfCnd4iZbg/oJM9oJcY+jVMMV
AQOsLPT+ONPSJ/Xtr7sVL5/myE3JB4MMqXUKe8jskL5fSdsSfV/8r4mgbl4RkFpHALYX
PTXEWxrhgj7jx9BahD3AJhJy+CLiVTwFEAyDs3hmnx8w5CH3/TgCxnP8ETVqwvKWSz4U
LSUu52dFd9cY4stCVsixEfq12h1H35gEPnuj7lfSRBGgFma3t/pwa3ZBVBrXWSzWM/z+
Z8mCdTR67qoGIROWXTXGfn5RfRH6xXjjXsa5Yr4NfECR7815uO1Iqq3NGUR8rC8WuqgS
TI2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:from:date:message-id:subject
:to:content-type;
bh=h0vWOyLr6erGPQyLFomgnIZPW13gQsewQVBSSKm6yB8=;
b=g7xf0pVRK8B7gLjFLxBzmvKNXUJ1CQqEWwOAcPgYDTmdsbHblcDK0xFy74/VhDAvsL
fPz5qoOtNns4j/RhPuVzl6UiR84ooHgIs4hnpDy6kVYzv8vL051Zv3yIYPeZbXr7RXin
6QXlyK91ovXksTGGwSgwKNhRmtl0jwFAfN6DR/JhVh3Y6b+iW/J4S6p8HkvRofZSPrqc
sFqctGrEN8/nVT3vCOMaCk+5d7MCVJUQV7ACXRYGjau17Rarf5PnEvfckac7bRY34mew
b0jwwhewQb6JpwPQK8Yyz9wbsmpCtPKxzorl6++L6HKaCnxCTHTQN0/dz9Zw1NncT3zp
pf9Q==
X-Gm-Message-State: AG10YOSzApvhQFXHo3uumLNVTlY+vcJdU3lNHwifhebdgAayz0f5J41buhmC/L+vDyA+PasdKxrmbwD2fe/foA==
X-Received: by 10.140.106.97 with SMTP id d88mr41110096qgf.84.1455021146141;
Tue, 09 Feb 2016 04:32:26 -0800 (PST)
MIME-Version: 1.0
Sender: slashene@gmail.com
Received: by 10.55.86.6 with HTTP; Tue, 9 Feb 2016 04:32:06 -0800 (PST)
From: Nicolas Dorier <nicolas.dorier@gmail.com>
Date: Tue, 9 Feb 2016 21:32:06 +0900
X-Google-Sender-Auth: 7NvfV0oiZBvvkI3pzxuo_qpGFE8
Message-ID: <CA+1nnrnghvJFfcg0Az0di1EGJYrSh-9h+5Y9P1pfQbbL-AuX=w@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a1139641e8e79ef052b558296
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
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: Tue, 09 Feb 2016 14:45:47 +0000
Subject: Re: [bitcoin-dev] On Hardforks in the Context of SegWit
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: Tue, 09 Feb 2016 12:32:27 -0000
--001a1139641e8e79ef052b558296
Content-Type: text/plain; charset=UTF-8
> 2) In order to prevent significant blowups in the cost to validate
> [...] and transactions are only allowed to contain
> up to 20 non-segwit inputs. [...]
There is two kind of hard fork, the one who breaks things, and the one who
does not.
Restricting the non-segwit inputs would disrupt lots of services, and
potentially invalidating
hash time locked transactions, which is a very bad precedent.
So I'm strongly against this particular point.
> scriptPubKeys are now limited to 100 bytes in
> size and may not contain OP_CODESEPARATOR, scriptSigs must be push-only
> (ie no non-push opcodes)
Same problem for native multisig, however potentially less important than
the previous point.
--001a1139641e8e79ef052b558296
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>> 2) In order to prevent significant blowups in th=
e cost to validate</div><div>> [...] and transactions are only allowed t=
o contain</div><div>> up to 20 non-segwit inputs. [...]</div><div><br></=
div><div>There is two kind of hard fork, the one who breaks things, and the=
one who does not.</div><div>Restricting the non-segwit inputs would disrup=
t lots of services, and potentially invalidating=C2=A0</div><div>hash time =
locked transactions, which is a very bad precedent.</div><div>So I'm st=
rongly against this particular point.<br></div><div><br></div><div>>=C2=
=A0<span style=3D"font-size:12.8px">scriptPubKeys are now limited to 100 by=
tes in</span></div><span style=3D"font-size:12.8px">> size and may not c=
ontain OP_CODESEPARATOR, scriptSigs must be push-only</span><br style=3D"fo=
nt-size:12.8px"><span style=3D"font-size:12.8px">> (ie no non-push opcod=
es)</span><div><span style=3D"font-size:12.8px"><br></span></div><div><span=
style=3D"font-size:12.8px">Same problem for native multisig, however poten=
tially less important than the previous point.</span></div></div>
--001a1139641e8e79ef052b558296--
|
