From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org, Tomas <tomas@tomasvdw.nl>
Subject: Re: [bitcoin-dev] [BIP Draft] Decentralized Improvement Proposals
Date: Wed, 30 Dec 2015 17:10:25 +0000 [thread overview]
Message-ID: <201512301710.27154.luke@dashjr.org> (raw)
In-Reply-To: <1451493317.3215816.479282618.4F666D71@webmail.messagingengine.com>
On Wednesday, December 30, 2015 4:35:17 PM Tomas via bitcoin-dev wrote:
> In an attempt to reduce developer centralization, and to reduce the risk
> of forks introduced by implementation other than bitcoin-core, I have
> drafted a BIP to support changes to the protocol from different
> implementations.
The premises in Motivation are false. BIPs are required to have a reference
implementation, but that implementation need not necessarily be for Bitcoin
Core specifically.
The specification itself looks like an inefficient and bloaty reinvention of
version bits.
Luke
next prev parent reply other threads:[~2015-12-30 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 16:35 [bitcoin-dev] [BIP Draft] Decentralized Improvement Proposals Tomas
2015-12-30 17:10 ` Luke Dashjr [this message]
2015-12-30 18:22 ` Tomas
2015-12-30 23:47 ` Luke Dashjr
2016-01-03 23:31 ` Rusty Russell
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=201512301710.27154.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=tomas@tomasvdw.nl \
/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