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
|
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 104FEE67
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 11 Feb 2016 23:04:43 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f173.google.com (mail-io0-f173.google.com
[209.85.223.173])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 51C5311C
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 11 Feb 2016 23:04:42 +0000 (UTC)
Received: by mail-io0-f173.google.com with SMTP id l127so73214977iof.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 11 Feb 2016 15:04:42 -0800 (PST)
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=oSHGqZCha/eZBv6/dIfvJX0WGkzPyZqXlMeefo3S+bk=;
b=oK8XWqWjuJFe8rpudsZUKZWt4bHX1rc7ElajyAeDHuiTp+gjGnUqmABuB0bVRG+Jez
3WrL8bzO9Rj5g7hH/Ts6bUzc1p59neu/i/q2fzHvj9NqwLhgHhp29bd/1Qv63Pwd1h+2
fv8m9K+uIFjfcRF4pWyLs0COpo3zD8s+xK3N9OMWyTFbq0UDyHm+M2x+fQVmAhM7mmru
lszFKpNYTopTbI4D+g/hNtpeCG68POpOkRZA4yPJ3ujLU4xRZeq10tNZ9EEZba1fcqDq
06bzdLHbe9xRjTDRLr/INZpQoQJphylwq+emrcBHfn78vUF3EvOxXgQSHvc4Wxg3mO8o
kEIg==
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:date
:message-id:subject:from:cc:content-type;
bh=oSHGqZCha/eZBv6/dIfvJX0WGkzPyZqXlMeefo3S+bk=;
b=Eop4i8z6gfN2qvs8Ut/NIphjJk3Ddxn3MB1VTzUYqIToDNeGi5P6ljFOgqEJs1AnYa
Xd+A+G3T7cYumnNjfWx5aZwmHZ70Y85yFsZH+GyMuKF7UbHdyeXB977/oImKOEOW/OYf
zwnE6jRQDa/VyYvWY4MgCw7WN84aMdZZI74+duaqo5839ynvJo/HJU8O/Bg65m2JmLKr
vc2WEjTyBE0X7J7S6vwecjUcdfYoToHMWgblJOd1j6/890lQFGvDHk7VU7JIj7ObEHDh
bL3cs5NyLgk9UeMo0G0ettrhgTzHocuHn6v6y3jb9RG2sKFL8UbkTZtnfoPC6s2CUEVF
scPg==
X-Gm-Message-State: AG10YOResXWImRGM4uLo5vkqta9qUUzskB6ZXCoyCnWw6i2nwdPwUmf4jpAqHGxiqTCPQg/QSbrQZOXGEkeRMA==
MIME-Version: 1.0
X-Received: by 10.107.28.80 with SMTP id c77mr53301333ioc.98.1455231877838;
Thu, 11 Feb 2016 15:04:37 -0800 (PST)
Received: by 10.79.77.65 with HTTP; Thu, 11 Feb 2016 15:04:37 -0800 (PST)
In-Reply-To: <CAHv+tb7CMEpR9hLp6pJE9Nt=j5zvChNr1CvDXn8Pb-d2sRZSEA@mail.gmail.com>
References: <CAE-z3OUpaMLxF9dGttzLUd6tG+nO18FMo3LZqr7taASVmrEumg@mail.gmail.com>
<CAHv+tb7CMEpR9hLp6pJE9Nt=j5zvChNr1CvDXn8Pb-d2sRZSEA@mail.gmail.com>
Date: Thu, 11 Feb 2016 23:04:37 +0000
Message-ID: <CAE-z3OU1UR1BY0Z++ZdkaLV+t9ygJm7OhaowQr2ksQHf0h_4=A@mail.gmail.com>
From: Tier Nolan <tier.nolan@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11409b18255940052b869354
X-Spam-Status: No, score=1.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_IMAGE_ONLY_20,
HTML_MESSAGE,
HTML_SHORT_LINK_IMG_3, MALFORMED_FREEMAIL, MISSING_HEADERS,
RCVD_IN_DNSWL_LOW, T_REMOTE_IMAGE autolearn=no version=3.3.1
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] BIP CPRKV: Check private key verify
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: Thu, 11 Feb 2016 23:04:43 -0000
--001a11409b18255940052b869354
Content-Type: text/plain; charset=UTF-8
On Thu, Feb 11, 2016 at 10:20 PM, Thomas Kerin <thomas.kerin@gmail.com>
wrote:
> I wonder if this is possible as a soft fork without using segwit?
Increasing the sigop count for a NOP would be a hard fork, but such a
change would be fine with a new segwit version. It might require specific
support in the altcoin, which might be troublesome..
It is a soft fork since it makes things that were previous allowed
disallowed. If it decreased the sigop count, then you could create a block
that had to many sigops due to the old rules.
With this rule, it increases the count. If the sigop count is valid under
the new rules, it is also valid under the old rules.
There is no need for specific support on the altcoin. It allows the
Bitcoin network act as trusted 3rd party so that you can do channels safely
on the altcoin, even though the altcoin still suffers from malleability and
doesn't have OP_CHECKLOCKTIMEVERIFY.
With regards to seg-witness, Ideally, the opcode would work in both old and
new scripts by re-purposing OP_NOP3.
<https://www.avast.com/sig-email> This email has been sent from a
virus-free computer protected by Avast.
www.avast.com <https://www.avast.com/sig-email>
<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--001a11409b18255940052b869354
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">On Thu, Feb 11, 2016 at 10:20 PM, Thomas Kerin <span dir=
=3D"ltr"><<a href=3D"mailto:thomas.kerin@gmail.com" target=3D"_blank">th=
omas.kerin@gmail.com</a>></span> wrote:<br><p dir=3D"ltr">> I
wonder if this is possible as a soft fork without using segwit?=20
Increasing the sigop count for a NOP would be a hard fork, but such a=20
change would be fine with a new segwit version. It might require=20
specific support in the altcoin, which might be troublesome..</p><p>It is a=
soft fork since it makes things that were previous allowed disallowed.=C2=
=A0 If it decreased the sigop count, then you could create a block that had=
to many sigops due to the old rules.</p><p>With this rule, it increases th=
e count.=C2=A0 If the sigop count is valid under the new rules, it is also =
valid under the old rules.<br></p><p>There is no need for specific support =
on the altcoin.=C2=A0 It allows the Bitcoin network act as trusted 3rd part=
y so that you can do channels safely on the altcoin, even though the altcoi=
n still suffers from malleability and doesn't have OP_CHECKLOCKTIMEVERI=
FY.</p><p>With regards to seg-witness, Ideally, the opcode would work in bo=
th old and new scripts by re-purposing OP_NOP3.<br></p></div><div id=3D"DDB=
4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><table style=3D"border-top:1px solid #aa=
abb6;margin-top:30px">
<tr>
<td style=3D"width:105px;padding-top:15px">
<a href=3D"https://www.avast.com/sig-email" target=3D"_blank"><img src=
=3D"https://ipmcdn.avast.com/images/logo-avast-v1.png" style=3D"width: 90px=
; height:33px;"></a>
</td>
<td style=3D"width:470px;padding-top:20px;color:#41424e;font-size:13px;fo=
nt-family:Arial,Helvetica,sans-serif;line-height:18px">This email has been =
sent from a virus-free computer protected by Avast. <br><a href=3D"https://=
www.avast.com/sig-email" target=3D"_blank" style=3D"color:#4453ea">www.avas=
t.com</a>
</td>
</tr>
</table><a href=3D"#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width=3D"1" heigh=
t=3D"1"></a></div>
--001a11409b18255940052b869354--
|
