MIME-Version: 1.0
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
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Services bit for xthin blocks
Precedence: list

--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">&lt;<a href=3D"mailto:luke@dashjr.org" tar=
get=3D"_blank">luke@dashjr.org</a>&gt;</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>
&gt; Not an unreasonable request, however while I personally respect the ma=
ny<br>
&gt; great accomplishments of individual engineers loosely affiliated with<=
br>
&gt; &quot;Core&quot;, Bitcoin Unlimited has our own process for documentat=
ion and<br>
&gt; discussion on an uncensored forum located here:<br>
&gt; <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>
&gt; would love to have any interested engineer join us there with ideas an=
d<br>
&gt; 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&#39;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&#39;t find BUIP 1 at a=
ll, for<br>
example.<br>
<br>
Thanks,<br>
<br>
Luke<br>
<br>
</blockquote></div><br></div>

--001a1135a2e8d07329052da1a021--