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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jtimon@jtimon.cc>) id 1YxSN2-0008Sx-EU
for bitcoin-development@lists.sourceforge.net;
Wed, 27 May 2015 03:51:08 +0000
Received: from mail-wi0-f176.google.com ([209.85.212.176])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YxSN1-0001wn-0g
for bitcoin-development@lists.sourceforge.net;
Wed, 27 May 2015 03:51:08 +0000
Received: by wifw1 with SMTP id w1so6148992wif.0
for <bitcoin-development@lists.sourceforge.net>;
Tue, 26 May 2015 20:51:00 -0700 (PDT)
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:to:cc:content-type;
bh=MeRZas/8/l2++U5TG1YKeza379OpekX92rELk6Ur//w=;
b=kaMI/9aDi4HQ3eoSG6Gb+FkrX2krchPuAm1FQ0EohKm+kdh1cc3ofdu6yWU8pF3AkS
cTlJRr8kuozX4Jia4U8qeSJcQfPCC2pUPWj4U1/jxQUZm6ghBx209ZceH+/XXmph/q60
6D5Qf4G2Nf39Ei/yVJBvliiaW90WhE07lgS4S+mXIKF/QnL8l7AU5rq9AfgBzoCPBxsc
8LtldyNXzHryKSyIhxY5GBfCEPkcEhCUgEF5PgkOXxXnzjkig6UC1GcubR6CFP9KuzwS
DyD/apEDM5zGAhqm+LzmaeOdQRMYWEADAJl4zj9tfWIMJGyC1yKWVBxK0XH0XQcyD/m4
miew==
X-Gm-Message-State: ALoCoQlB4DYG5UcErgUfMeTIlL1o5xystYLse68jUbal8DrajzpJaPzNbg0ODALwh5FwcABUXB9g
MIME-Version: 1.0
X-Received: by 10.180.188.4 with SMTP id fw4mr46135972wic.7.1432698660766;
Tue, 26 May 2015 20:51:00 -0700 (PDT)
Received: by 10.194.127.97 with HTTP; Tue, 26 May 2015 20:51:00 -0700 (PDT)
Received: by 10.194.127.97 with HTTP; Tue, 26 May 2015 20:51:00 -0700 (PDT)
In-Reply-To: <201505270346.17014.luke@dashjr.org>
References: <CAPg+sBg5TqQ=zjyZ7dp-d1oBGp31Krnix3zyt9suP4-AGbxW=Q@mail.gmail.com>
<201505270346.17014.luke@dashjr.org>
Date: Wed, 27 May 2015 05:51:00 +0200
Message-ID: <CABm2gDoriDaQ1AjRDFxCT9zCNPQakJd9xRxfWkOJBf4v22hndQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=001a11c38216bedbcf0517082697
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1YxSN1-0001wn-0g
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Version bits proposal
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 27 May 2015 03:51:08 -0000
--001a11c38216bedbcf0517082697
Content-Type: text/plain; charset=UTF-8
It would also help to see the actual code changes required, which I'm sure
will be much shorter than the explanation itself.
On May 27, 2015 5:47 AM, "Luke Dashjr" <luke@dashjr.org> wrote:
> On Wednesday, May 27, 2015 1:48:05 AM Pieter Wuille wrote:
> > Feel free to comment. As the gist does not support notifying participants
> > of new comments, I would suggest using the mailing list instead.
>
> I suggest adding a section describing how this interacts with and changes
> GBT.
>
> Currently, the client tells the server what the highest block version it
> supports is, and the server indicates a block version to use in its
> template,
> as well as optional instructions for the client to forcefully use this
> version
> despite its own maximum version number. Making the version a bitfield
> contradicts the increment-only assumption of this design, and since GBT
> clients are not aware of overall network consensus state, reused bits can
> easily become confused. I suggest, therefore, that GBT clients should
> indicate
> (instead of a maximum supported version number) a list of softforks by
> identifier keyword, and the GBT server respond with a template indicating:
> - An object of softfork keywords to bit values, that the server will
> accept.
> - The version number, as presently conveyed, indicating the preferred
> softfork
> flags.
>
> Does this sound reasonable, and/or am I missing anything else?
>
> Luke
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a11c38216bedbcf0517082697
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">It would also help to see the actual code changes required, =
which I'm sure will be much shorter than the explanation itself.</p>
<div class=3D"gmail_quote">On May 27, 2015 5:47 AM, "Luke Dashjr"=
<<a href=3D"mailto:luke@dashjr.org">luke@dashjr.org</a>> wrote:<br t=
ype=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Wednesday, May 27, 20=
15 1:48:05 AM Pieter Wuille wrote:<br>
> Feel free to comment. As the gist does not support notifying participa=
nts<br>
> of new comments, I would suggest using the mailing list instead.<br>
<br>
I suggest adding a section describing how this interacts with and changes G=
BT.<br>
<br>
Currently, the client tells the server what the highest block version it<br=
>
supports is, and the server indicates a block version to use in its templat=
e,<br>
as well as optional instructions for the client to forcefully use this vers=
ion<br>
despite its own maximum version number. Making the version a bitfield<br>
contradicts the increment-only assumption of this design, and since GBT<br>
clients are not aware of overall network consensus state, reused bits can<b=
r>
easily become confused. I suggest, therefore, that GBT clients should indic=
ate<br>
(instead of a maximum supported version number) a list of softforks by<br>
identifier keyword, and the GBT server respond with a template indicating:<=
br>
- An object of softfork keywords to bit values, that the server will accept=
.<br>
- The version number, as presently conveyed, indicating the preferred softf=
ork<br>
flags.<br>
<br>
Does this sound reasonable, and/or am I missing anything else?<br>
<br>
Luke<br>
<br>
---------------------------------------------------------------------------=
---<br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div>
--001a11c38216bedbcf0517082697--
|
