From: "G. Andrew Stone" <g.andrew.stone@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Services bit for xthin blocks
Date: Wed, 9 Mar 2016 13:11:34 -0500 [thread overview]
Message-ID: <CAHUwRvszz2XQ1DdfKYqrkQkxvPzkPSc=2R+LNDkDuvjyZ+U8FA@mail.gmail.com> (raw)
In-Reply-To: <201603081719.20662.luke@dashjr.org>
[-- Attachment #1: Type: text/plain, Size: 1995 bytes --]
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
>
>
[-- Attachment #2: Type: text/html, Size: 2683 bytes --]
next prev parent reply other threads:[~2016-03-09 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 20:06 [bitcoin-dev] Services bit for xthin blocks G. Andrew Stone
2016-03-07 20:51 ` Gregory Maxwell
2016-03-07 21:10 ` dagurval
2016-03-08 2:35 ` G. Andrew Stone
2016-03-08 17:19 ` Luke Dashjr
2016-03-09 18:11 ` G. Andrew Stone [this message]
2016-03-09 21:11 ` Tier Nolan
2016-03-08 5:14 ` Dave Scotese
[not found] ` <CAAS2fgSf_qYaT7ahQTbmRoQpG57qgF26NKVuGGaEzpMZmCOFoA@mail.gmail.com>
2016-03-08 6:09 ` [bitcoin-dev] Fwd: " Gregory Maxwell
2016-03-07 21:09 ` [bitcoin-dev] " Tier Nolan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHUwRvszz2XQ1DdfKYqrkQkxvPzkPSc=2R+LNDkDuvjyZ+U8FA@mail.gmail.com' \
--to=g.andrew.stone@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=luke@dashjr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox