From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org,
"G. Andrew Stone" <g.andrew.stone@gmail•com>
Subject: Re: [bitcoin-dev] Services bit for xthin blocks
Date: Tue, 8 Mar 2016 17:19:19 +0000 [thread overview]
Message-ID: <201603081719.20662.luke@dashjr.org> (raw)
In-Reply-To: <CAHUwRvv_UMoRhcwy7u2XLz19q3aKNfHXyTNbfaSUsEapFnH2kg@mail.gmail.com>
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
next prev parent reply other threads:[~2016-03-08 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 20:06 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 [this message]
2016-03-09 18:11 ` G. Andrew Stone
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=201603081719.20662.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=g.andrew.stone@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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