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
|
Return-Path: <dagurvj@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 0D4B4C68
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 7 Mar 2016 21:10:55 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com
[209.85.217.176])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5FBBE13F
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 7 Mar 2016 21:10:54 +0000 (UTC)
Received: by mail-lb0-f176.google.com with SMTP id k15so146134730lbg.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 07 Mar 2016 13:10:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:from:date:message-id
:subject:to:cc;
bh=nEZacUnmt6A+u3TF00l18CyidMc44Co0vhhuvFw32OY=;
b=mTY7M2XVFmWdLxeGv4JvTmfu0ZKKB6lVnYZlqblojNHAb2PSJ/9jglljNplaQjXZ1l
fhcL3+0Dc4luUA26vnjdHkYpiCTpSbKEcY5EsaE2eP6+z4ULQvvd/P//mqHOczbopsIe
uJLtpQwRAE/kjnVLCanODZchbBMTJD52cX8N0dnm8WzhR8tvDTZIrXFVH4v6wc0yQWyq
H8cC4g53iV0LoXkWHowAqCmgOm+PVxIYprvJBYMJh3rdMb7rG30a5LtnaIcu7+scbhMy
gpNVN3qIeu3RnJr0zyxnQssDgX36C9hfttufIOzaYB1ep0gGDQQCcUhoq46Q2jO5vIjc
0GbA==
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:in-reply-to:references:from
:date:message-id:subject:to:cc;
bh=nEZacUnmt6A+u3TF00l18CyidMc44Co0vhhuvFw32OY=;
b=TKxio5eTJqHD423MYSQfLpO/RzU/63F/1LV0TF2j3nsfbyUVIn9TVNXjWrh+S1EvWN
m3RMtefXSDuTOFMIb++/P0+geOzMOvYZHYF3vyoc3u9Kpdp8OfydWbChfg7WEwVBFB3m
Xd2ABmjWkv+jHKc+v+a9cCH/j5dApbzNbKo9RF7iEkvGbjelwElMJqo0x4eHGLOmBCYc
1nkKTs7vTSpPnh8/piRkVXBCfJI/Qg6i4CC+ERLURnfw3E6FK67Ph9ZdYT+Kg/fhsRrP
0Ii3gCTST/55FJRI8d426FUK8EtYQl3VuubBc5RCcqdedcmcXFmA7SpNdOuCel75ta1r
bvqw==
X-Gm-Message-State: AD7BkJJ3ODmycBGf/DMucndTgfmQDp8zrM7UAWAdAIhI+YBGXdDEHZ+yMMqqRZoLUvY12A0kYp2N5ZEZqL1oHw==
X-Received: by 10.25.90.21 with SMTP id o21mr6358243lfb.166.1457385052765;
Mon, 07 Mar 2016 13:10:52 -0800 (PST)
MIME-Version: 1.0
Sender: dagurvj@gmail.com
Received: by 10.25.207.202 with HTTP; Mon, 7 Mar 2016 13:10:33 -0800 (PST)
In-Reply-To: <CAAS2fgQi1X4v9WxT1pnd_XSyE2b8hUZUv0z5A8cOEvw5RztOKw@mail.gmail.com>
References: <CAHUwRvuR9qtYc+rVh1yPbQoESxm4m0r6a+Fd6VF=FuT0vom_HQ@mail.gmail.com>
<CAAS2fgQi1X4v9WxT1pnd_XSyE2b8hUZUv0z5A8cOEvw5RztOKw@mail.gmail.com>
From: dagurval <dagurvj+btclist@gmail.com>
Date: Mon, 7 Mar 2016 22:10:33 +0100
X-Google-Sender-Auth: GIpbaa0cq8CuflYDmCBJIPD7SOo
Message-ID: <CALcNmJwY=pQuRpnb-MJ1QiME3mPUSe2KmHD7XykhX08yku9mhQ@mail.gmail.com>
To: Gregory Maxwell <greg@xiph.org>
Content-Type: multipart/alternative; boundary=001a114111065f0348052d7be660
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, 08 Mar 2016 06:59:28 +0000
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Services bit for xthin blocks
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: Mon, 07 Mar 2016 21:10:55 -0000
X-List-Received-Date: Mon, 07 Mar 2016 21:10:55 -0000
--001a114111065f0348052d7be660
Content-Type: text/plain; charset=UTF-8
Hi,
> Does this functionality change peer selection?
This bit will be used for selecting outgoing peers in Bitcoin XT.
On Mon, Mar 7, 2016 at 9:51 PM, Gregory Maxwell via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Mon, Mar 7, 2016 at 8:06 PM, G. Andrew Stone via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > The Bitcoin Unlimited client needs a services bit to indicate that the
> node
> > is capable of communicating thin blocks. We propose to use bit 4 as
> AFAIK
> > bit 3 is already earmarked for Segregated Witness.
>
> Does this functionality change peer selection? If not, the preferred
> signaling mechanism is probably the one in BIP 130.
>
> Otherwise, I think the standard method for getting numbers has been to
> write a BIP documenting the usage. I don't know if that is intentional
> or just how things have previously happened; and I don't have much of
> an opinion on it.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a114111065f0348052d7be660
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div style=3D"font-size:12.8px">Hi,<br></div><span class=
=3D"im" style=3D"font-size:12.8px"><div><br></div><div>>=C2=A0<span styl=
e=3D"font-size:12.8px">Does this functionality change peer selection?=C2=A0=
</span></div><div><br></div></span><div style=3D"font-size:12.8px">This bit=
will be used for selecting outgoing peers in Bitcoin XT.</div></div><div c=
lass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Mar 7, 2016 at =
9:51 PM, Gregory Maxwell via bitcoin-dev <span dir=3D"ltr"><<a href=3D"m=
ailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@=
lists.linuxfoundation.org</a>></span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><span class=3D"">On Mon, Mar 7, 2016 at 8:06 PM, G. Andrew Stone via=
bitcoin-dev<br>
<<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@li=
sts.linuxfoundation.org</a>> wrote:<br>
> The Bitcoin Unlimited client needs a services bit to indicate that the=
node<br>
> is capable of communicating thin blocks.=C2=A0 We propose to use bit 4=
as AFAIK<br>
> bit 3 is already earmarked for Segregated Witness.<br>
<br>
</span>Does this functionality change peer selection?=C2=A0 If not, the pre=
ferred<br>
signaling mechanism is probably the one in BIP 130.<br>
<br>
Otherwise, I think the standard method for getting numbers has been to<br>
write a BIP documenting the usage. I don't know if that is intentional<=
br>
or just how things have previously happened; and I don't have much of<b=
r>
an opinion on it.<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div><br></div>
--001a114111065f0348052d7be660--
|
