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
|
Return-Path: <jaejoon@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 37B7F958
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Apr 2017 14:40:31 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f182.google.com (mail-wr0-f182.google.com
[209.85.128.182])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9F787F1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Apr 2017 14:40:30 +0000 (UTC)
Received: by mail-wr0-f182.google.com with SMTP id z109so30393644wrb.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 11 Apr 2017 07:40: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=5CaozEEbUN7F2ys8NkXyi4lZtb6mKcUntSZHDC7CZrc=;
b=dXngpdME2Wy7/2OsPf44TaVoLF866QDZeJegiZBUmbqPxWYn3qjHj7BOKorAU7OiNn
Wun+VdYGIhoMu9N7Gg/aGh/M+ny1BoIwZJIIMBIWVME8bGtjJSIEzaBiMsdk8CBhDs3Z
0xCgS7rGGU9RZNnHM+ZM939Z25/7vI7D5i1Nc1Fi3d624B/MLtvQKY9F4H3W1EN7Lor1
dd3y52R1N+PZI41W0thR+BYC2Xb4B5xQh/k+R77I1/zCoJloxQYavcBWcE2fi9VR9jNH
tQll2g/nmC4NGoAisP1awXdSQM43ySDpNq9QlRAo8g7VKEcUUPf8GM2Z4NymJXimtzus
UFBA==
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=5CaozEEbUN7F2ys8NkXyi4lZtb6mKcUntSZHDC7CZrc=;
b=TwHDpZ84NWGQI/wELtu5gUB4CN2P+QDkE+qpbfCoz+qttKpRu71JUt4Ct8Kjac1W3h
nwW+hrcD8TiYv/wQ6IKSbq8sZtAOtUCzT/Trdem7/x/y4VJTFYOIZAMHgM+NApPgbe1T
R4M4QknjHtciVG+w5jJi4P58eL20RdO+pMoUF/PMSx8oHst0RBDfVt8TiD3nMA+F8r+I
XzXqomnqcFq3jjNN+EWwLhH6V+d4W3a/OcXT/fauzY3FAIxh2oxWu0nnE7t+MduK6FZy
57fJOqgTdXxECx1Zkf/jPsDlnoZvaqIDP2TwprfQwYHayJ5waZZHHbo3JL5jQoSgw2VK
OEfA==
X-Gm-Message-State: AFeK/H0+pr/5G+OCbO3PmHTKMCVkuPMlvLZ+ci2wMowEOGKmI73EDyghqFB3hF7SecPmaZNxIXV2x9rVnuDQDw==
X-Received: by 10.223.176.242 with SMTP id j47mr33649545wra.81.1491921629160;
Tue, 11 Apr 2017 07:40:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.131.225 with HTTP; Tue, 11 Apr 2017 07:40:28 -0700 (PDT)
In-Reply-To: <04bbsNGwBdLiye5VgB_cNxkCNiOSNJBWFpI2QbN_o_ZQWRLEU7FjgkfOi5DZXrrBeQIuacMn_JHGzzX4dCmoyjmpT6PI9GZDu3JDgpgT4Pw=@protonmail.com>
References: <CAJR7vkpRhNsQsem-nFkeubX04xx1y7aHwCENfg0d1266oOsXMw@mail.gmail.com>
<2151650.Y6dYBXdtR5@strawberry>
<04bbsNGwBdLiye5VgB_cNxkCNiOSNJBWFpI2QbN_o_ZQWRLEU7FjgkfOi5DZXrrBeQIuacMn_JHGzzX4dCmoyjmpT6PI9GZDu3JDgpgT4Pw=@protonmail.com>
From: Jimmy Song <jaejoon@gmail.com>
Date: Tue, 11 Apr 2017 09:40:28 -0500
Message-ID: <CAJR7vkruAKxyB4GpU7=Tb7U8+zHzrb4PbL5zssC70BEtFVY=WA@mail.gmail.com>
To: Sancho Panza <sanch0panza@protonmail.com>
Content-Type: multipart/alternative; boundary=001a11419d66bd2c75054ce51241
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE 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, 11 Apr 2017 18:53:17 +0000
Cc: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A Small Modification to Segwit
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, 11 Apr 2017 14:40:31 -0000
--001a11419d66bd2c75054ce51241
Content-Type: text/plain; charset=UTF-8
I've changed the proposal so only 8 bits are given to grinding so something
like 20 bits are available for signaling.
I have to say I'm at a loss here as to what's next? Should I make a new BIP
or try to convince the authors of BIP141 to modify their BIP? Could someone
inform me on the next part of the process?
On Tue, Apr 11, 2017 at 8:25 AM, Sancho Panza via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Tom Zander wrote:
>
> > The version field is still needed to actually allow future block version
> upgrades. We would cut off our road forward if that were to be blocked.
>
> I tend to agree, if all 32 bits were given up to grinding.
>
> But it's worth pointing out that BIP9 is purely informational, and the top
> 3 bits are still reserved for other purposes. One of them could perhaps be
> used to signal for an extended version field somewhere else, leaving the
> bottom 29 as entropy?
>
> Not a direction I prefer, but just a technical possibility perhaps.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--001a11419d66bd2c75054ce51241
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I've changed the proposal so only 8 bits are given to =
grinding so something like 20 bits are available for signaling.<div><br></d=
iv><div>I have to say I'm at a loss here as to what's next? Should =
I make a new BIP or try to convince the authors of BIP141 to modify their B=
IP? Could someone inform me on the next part of the process?</div></div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Apr 11, 2017=
at 8:25 AM, Sancho Panza 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><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><span class=3D""><div>Tom Zander wrote:<br></div><div><br></div><di=
v>> The version field is still needed to actually allow future block ver=
sion upgrades. We would cut off our road forward if that were to be blocked=
.<br></div><div><br></div></span><div>I tend to agree, if all 32 bits were =
given up to grinding.<br></div><div><br></div><div>But it's worth point=
ing out that BIP9 is purely informational, and the top 3 bits are still res=
erved for other purposes. One of them could perhaps be used to signal for a=
n extended version field somewhere else, leaving the bottom 29 as entropy?<=
br></div><div><br></div><div>Not a direction I prefer, but just a technical=
possibility perhaps.<br></div><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>
--001a11419d66bd2c75054ce51241--
|
