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
|
Return-Path: <hampus.sjoberg@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 0DEC81BB
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 20 Jun 2017 22:53:35 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qt0-f178.google.com (mail-qt0-f178.google.com
[209.85.216.178])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DDF0A147
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 20 Jun 2017 22:53:30 +0000 (UTC)
Received: by mail-qt0-f178.google.com with SMTP id u19so145058235qta.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 20 Jun 2017 15:53:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=srPjH5ej9WxcOarZCCJN6d0xgnzDBCM1+kr5uUedOdE=;
b=S0TBk9WbJUaJad/WuZh9ChJ02K5VCrtHeNL7EI28ePnl2nxo/N/KgBbk3SiSxgEk9a
xWL6VsB1GFhl4Eu+SgjUvdduZyOLb8EPL/FkeZAyomKGTtIDwQCCrdCzEuVSWtBSWJuT
Cu3Oc9ih6kkJBPRLCu5fR2UakwR3YPpmIAJZJGgTgNKDSWaH0uDvV5cHm1OZZE25X+kv
oCAutNACopmPaTNEO/zXmYcTwu13SncxXJz1gVz8uNEOfhaII4etprDhVIHR2a5Zc3iK
bPDGY0wUlBIhYov/yjkYzpdzMJmd2Xi3AcTsWnNA2Pc0rNINLnJ5FS+2PPaJ5X8znAYN
lGag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=srPjH5ej9WxcOarZCCJN6d0xgnzDBCM1+kr5uUedOdE=;
b=sPxpLQWJTh1Y1fFS0KNIim2zkpWUK/AC2E//trxAkg7C1VNLzX1cGjwwanjK6yI62G
WKN5emmm7nklkyjtf9mKP6fEQAKzs6T2iyTHqOhJDlu+D5rxwlH68fqB85XTzukFO8X0
b+0jlukLTTP9v/SE3vaqVGy8earM7bzLUrcdAtrSIBIga3pcB3cgWGowCTU5kPiQ2BMb
/Uy3JIDuGLjHkz95gIkAPlQkplr4PF+KHMM+Q5FUKqvhhsHKgC0dVkx04FBIeF2RGROe
RYeyPdCOOrZ6gvE9GPsuDP8Qza9d5/ACA0p5iT1WqQOofiMT3YPDWpIafG3GgrITYVYk
1PMA==
X-Gm-Message-State: AKS2vOyIRo0FmvHOgh0vWhd3tEhPd4nLeY0fONTS/vUUzXHMeKDDh/jt
AcjxGrVnUOPR7r4BGO0zxg8zjjwjJw==
X-Received: by 10.237.61.91 with SMTP id h27mr7725463qtf.1.1497999210131; Tue,
20 Jun 2017 15:53:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.155.140 with HTTP; Tue, 20 Jun 2017 15:53:29 -0700 (PDT)
In-Reply-To: <CAAS2fgQKrFCTL-=qREOjNrwjDqhgdPZQUSgpXHUKyG4+NAo26g@mail.gmail.com>
References: <CAJowKgLtu-HUDuakk4DDU53nyChbQk_zY=f5OO2j1Za95PdL7w@mail.gmail.com>
<CAAS2fgSZ_X3G7j3-S6tAGPe2TOTT2umBB8a0RHpD-wAHN9aPgw@mail.gmail.com>
<CAFMkqK_73RrpaS2oJQ-0o6oC29m6a1h411_P7HmVcAyX712Sgw@mail.gmail.com>
<CAAS2fgQKrFCTL-=qREOjNrwjDqhgdPZQUSgpXHUKyG4+NAo26g@mail.gmail.com>
From: =?UTF-8?Q?Hampus_Sj=C3=B6berg?= <hampus.sjoberg@gmail.com>
Date: Wed, 21 Jun 2017 00:53:29 +0200
Message-ID: <CAFMkqK-4P1=3_SujjTJDgusyBeHX3rB82ekkv9uNGu7P+9yuyQ@mail.gmail.com>
To: Gregory Maxwell <greg@xiph.org>
Content-Type: multipart/alternative; boundary="001a1144bf98cb366c05526c1e46"
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
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Miners forced to run non-core code in order to
get segwit activated
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: Tue, 20 Jun 2017 22:53:35 -0000
--001a1144bf98cb366c05526c1e46
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
> I think it would be useful for there to exist a useful and trivial
> patch against current (0.14.2) software to engage in the BIP91-like
> orphaning, like people have provided for BIP148-- but right now I
> don't see any specification of the behavior so it's unclear to me
> _exactly_ what it would need to implement to be consistent.
I agree.
This is the latest code regarding BIP91 that got merged,
https://github.com/btc1/bitcoin/pull/21/files so that should be the spec we
need to follow (also the old BIP91 PR:
https://github.com/btc1/bitcoin/pull/17/files).
Perhaps James Hilliard could give input here though.
2017-06-21 0:34 GMT+02:00 Gregory Maxwell <greg@xiph.org>:
> On Tue, Jun 20, 2017 at 10:15 PM, Hampus Sj=C3=B6berg
> <hampus.sjoberg@gmail.com> wrote:
> > Segwit2x/BIP91/BIP148 will orphan miners that do not run a Segwit2x (or
> > BIP148) node, because they wouldn't have the new consensus rule of
> requiring
> > all blocks to signal for segwit.
>
> All versions of Bitcoin Core since 0.13.1 signal segwit, 0.14.1+ even
> when downstream mining software doesn't support it.
>
> I think it would be useful for there to exist a useful and trivial
> patch against current (0.14.2) software to engage in the BIP91-like
> orphaning, like people have provided for BIP148-- but right now I
> don't see any specification of the behavior so it's unclear to me
> _exactly_ what it would need to implement to be consistent.
>
--001a1144bf98cb366c05526c1e46
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>> I think it would be useful for there to exist a =
useful and trivial<br>> patch against current (0.14.2) software to engag=
e in the BIP91-like<br>> orphaning, like people have provided for BIP148=
-- but right now I<br>> don't see any specification of the behavior =
so it's unclear to me<br>> _exactly_ what it would need to implement=
to be consistent.<br><br></div><div>I agree.<br></div><div>This is the lat=
est code regarding BIP91 that got merged, <a href=3D"https://github.com/btc=
1/bitcoin/pull/21/files">https://github.com/btc1/bitcoin/pull/21/files</a> =
so that should be the spec we need to follow (also the old BIP91 PR: <a hre=
f=3D"https://github.com/btc1/bitcoin/pull/17/files">https://github.com/btc1=
/bitcoin/pull/17/files</a>).<br></div><div>Perhaps James Hilliard could giv=
e input here though.<br><br>
</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2017-=
06-21 0:34 GMT+02:00 Gregory Maxwell <span dir=3D"ltr"><<a href=3D"mailt=
o:greg@xiph.org" target=3D"_blank">greg@xiph.org</a>></span>:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><span class=3D"">On Tue, Jun 20, 2017 at 10:15 PM, =
Hampus Sj=C3=B6berg<br>
<<a href=3D"mailto:hampus.sjoberg@gmail.com">hampus.sjoberg@gmail.com</a=
>> wrote:<br>
> Segwit2x/BIP91/BIP148 will orphan miners that do not run a Segwit2x (o=
r<br>
> BIP148) node, because they wouldn't have the new consensus rule of=
requiring<br>
> all blocks to signal for segwit.<br>
<br>
</span>All versions of Bitcoin Core since 0.13.1 signal segwit, 0.14.1+ eve=
n<br>
when downstream mining software doesn't support it.<br>
<br>
I think it would be useful for there to exist a useful and trivial<br>
patch against current (0.14.2) software to engage in the BIP91-like<br>
orphaning, like people have provided for BIP148-- but right now I<br>
don't see any specification of the behavior so it's unclear to me<b=
r>
_exactly_ what it would need to implement to be consistent.<br>
</blockquote></div><br></div>
--001a1144bf98cb366c05526c1e46--
|
