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
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
|
Return-Path: <g.andrew.stone@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id A1B67B64
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 Mar 2016 18:11:36 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qg0-f47.google.com (mail-qg0-f47.google.com
[209.85.192.47])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 79415F0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 9 Mar 2016 18:11:35 +0000 (UTC)
Received: by mail-qg0-f47.google.com with SMTP id t4so48771169qge.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 09 Mar 2016 10:11:35 -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:to
:cc; bh=IHhR2XgZyytyplGoEq3PHRFPRIxH6IRz11BCpLpyMwI=;
b=D0s8Kk5LhFWYbeToPzu27j1p0zobAaFw/RVAsrTXlVi23W/wGinD28dXVeD7s4le0v
GIHX6qS9MSL+FRUKlub5mM36aFPGvANqt73yg8+gVGopj+ujITiuZAEsyavDJuXFX+fQ
zcPSK0znW1vjElFqdfwHwHdd8NfpoKG3ERxWodjPAW0ioRUzdutZpZTLik94+fdJ+KcW
YBnoQyR2d6eto029mScpsq3QrywwboFKfu17+gOFaACpiBXJByeloxP75Cp/Ap0JuYL0
uWX7vhYKClrdjgvGNyYELLU3aapqrdxJoeAfYrBMyy3isZFzX8ERwqWtWN8nX6tuKcqk
b3qg==
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;
bh=IHhR2XgZyytyplGoEq3PHRFPRIxH6IRz11BCpLpyMwI=;
b=RGFo20/IjFanLFlU2VECGx2D5x0o+ph4LyY+amHV2Z6XtvV8Lw9ybhK3/HRFkPGqt/
wo5Ri3PV7TSyol+7AB1GKGw9QPXxAjCf5ETVZ/wdj8JzlqV1TYBd+7Nb1N5NipeilLH0
JlLd+OCcgMhf+leKfx3LGfOr1Uo/effp7gQBe2VFXBU2JMvs+voW0W3MVo8Iz4mu/mr/
q5JRKjvOqCQpCHjJBVZUzrmLWI0od1pX2H0fPhnTzprBDeqU8Hx5Eop/JCZ/Q8qwe27b
u1M969KQ8LzDXGn2KFeROU6wPeURY4lmTlOtCUElg3V5KUxe4niTnGxqBtcEvBHSQg3R
8Alw==
X-Gm-Message-State: AD7BkJJ8iKcmyGv1Iwet7UjkNplHBwB1tblO61WmJzWtix3MPnvZCE0Zz2Sfpr9dcxwyQEJKquxnDpmDNbZVVg==
MIME-Version: 1.0
X-Received: by 10.140.238.8 with SMTP id j8mr47909593qhc.76.1457547094551;
Wed, 09 Mar 2016 10:11:34 -0800 (PST)
Received: by 10.55.9.13 with HTTP; Wed, 9 Mar 2016 10:11:34 -0800 (PST)
In-Reply-To: <201603081719.20662.luke@dashjr.org>
References: <CAHUwRvuR9qtYc+rVh1yPbQoESxm4m0r6a+Fd6VF=FuT0vom_HQ@mail.gmail.com>
<CALcNmJwY=pQuRpnb-MJ1QiME3mPUSe2KmHD7XykhX08yku9mhQ@mail.gmail.com>
<CAHUwRvv_UMoRhcwy7u2XLz19q3aKNfHXyTNbfaSUsEapFnH2kg@mail.gmail.com>
<201603081719.20662.luke@dashjr.org>
Date: Wed, 9 Mar 2016 13:11:34 -0500
Message-ID: <CAHUwRvszz2XQ1DdfKYqrkQkxvPzkPSc=2R+LNDkDuvjyZ+U8FA@mail.gmail.com>
From: "G. Andrew Stone" <g.andrew.stone@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=001a1135a2e8d07329052da1a021
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: Wed, 09 Mar 2016 18:17:20 +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: Wed, 09 Mar 2016 18:11:36 -0000
--001a1135a2e8d07329052da1a021
Content-Type: text/plain; charset=UTF-8
Thanks for your offer Luke, but we are happy with our own process and,
regardless of historical provenance, see this mailing list and the BIP
process as very Core specific for reasons that are too numerous to describe
here but should be obvious to anyone who has been aware of the last year of
Bitcoin history.
Andrew
On Tue, Mar 8, 2016 at 12:19 PM, Luke Dashjr <luke@dashjr.org> wrote:
> On Tuesday, March 08, 2016 2:35:21 AM G. Andrew Stone via bitcoin-dev
> wrote:
> > Not an unreasonable request, however while I personally respect the many
> > great accomplishments of individual engineers loosely affiliated with
> > "Core", Bitcoin Unlimited has our own process for documentation and
> > discussion on an uncensored forum located here:
> > https://bitco.in/forum/threads/buip010-passed-xtreme-thinblocks.774/. We
> > would love to have any interested engineer join us there with ideas and
> > criticisms.
>
> Bitcoin-dev and the BIP process are not affiliated with Core at all. In
> fact,
> the BIP process was created by Amir Taaki, who was a libbitcoin developer
> (libbitcoin is not Core).
>
> I encourage Bitcoin Unlimited to use the BIP process for
> cross-implementation
> standards like this, as do other implementations, so that you can benefit
> from
> peer review from the wider Bitcoin development community, as well as have a
> common repository for these standards.
>
> Many BIPs are discussed on reddit in addition to this mailing list, and you
> would certainly remain free to discuss your own proposals on any forum you
> like - it isn't restricted to only this mailing list.
>
> If this is of interest, I will be happy to try to go over and assign BIP
> numbers to the current (15?) BUIPs assuming they meet the basic
> requirements
> for such assignment (see BIP 1:
> https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki). Is there
> an
> easy way to get links to each of the BUIPs? I couldn't find BUIP 1 at all,
> for
> example.
>
> Thanks,
>
> Luke
>
>
--001a1135a2e8d07329052da1a021
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Thanks for your offer Luke, but we are happy with our=
own process and, regardless of historical provenance, see this mailing lis=
t and the BIP process as very Core specific for reasons that are too numero=
us to describe here but should be obvious to anyone who has been aware of t=
he last year of Bitcoin history.<br><br></div>Andrew<br></div><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Mar 8, 2016 at 12:19 P=
M, Luke Dashjr <span dir=3D"ltr"><<a href=3D"mailto:luke@dashjr.org" tar=
get=3D"_blank">luke@dashjr.org</a>></span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><span class=3D"">On Tuesday, March 08, 2016 2:35:21 AM G. And=
rew Stone via bitcoin-dev wrote:<br>
> Not an unreasonable request, however while I personally respect the ma=
ny<br>
> great accomplishments of individual engineers loosely affiliated with<=
br>
> "Core", Bitcoin Unlimited has our own process for documentat=
ion and<br>
> discussion on an uncensored forum located here:<br>
> <a href=3D"https://bitco.in/forum/threads/buip010-passed-xtreme-thinbl=
ocks.774/" rel=3D"noreferrer" target=3D"_blank">https://bitco.in/forum/thre=
ads/buip010-passed-xtreme-thinblocks.774/</a>. We<br>
> would love to have any interested engineer join us there with ideas an=
d<br>
> criticisms.<br>
<br>
</span>Bitcoin-dev and the BIP process are not affiliated with Core at all.=
In fact,<br>
the BIP process was created by Amir Taaki, who was a libbitcoin developer<b=
r>
(libbitcoin is not Core).<br>
<br>
I encourage Bitcoin Unlimited to use the BIP process for cross-implementati=
on<br>
standards like this, as do other implementations, so that you can benefit f=
rom<br>
peer review from the wider Bitcoin development community, as well as have a=
<br>
common repository for these standards.<br>
<br>
Many BIPs are discussed on reddit in addition to this mailing list, and you=
<br>
would certainly remain free to discuss your own proposals on any forum you<=
br>
like - it isn't restricted to only this mailing list.<br>
<br>
If this is of interest, I will be happy to try to go over and assign BIP<br=
>
numbers to the current (15?) BUIPs assuming they meet the basic requirement=
s<br>
for such assignment (see BIP 1:<br>
<a href=3D"https://github.com/bitcoin/bips/blob/master/bip-0001.mediawiki" =
rel=3D"noreferrer" target=3D"_blank">https://github.com/bitcoin/bips/blob/m=
aster/bip-0001.mediawiki</a>). Is there an<br>
easy way to get links to each of the BUIPs? I couldn't find BUIP 1 at a=
ll, for<br>
example.<br>
<br>
Thanks,<br>
<br>
Luke<br>
<br>
</blockquote></div><br></div>
--001a1135a2e8d07329052da1a021--
|
