From: Peter R <peter_r@gmx.com>
To: Allen Piscitello <allen.piscitello@gmail.com>
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Your Gmaxwell exchange
Date: Mon, 31 Aug 2015 16:32:55 -0700 [thread overview]
Message-ID: <5A3D7824-F1E3-421B-A32A-0EF21DD215BD@gmx.com> (raw)
In-Reply-To: <CAJfRnm4kwHkBLUUOmfzViUwsdAf3LYSTruvHw9+-RbgxSMHLRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On 2015-08-31, at 2:24 PM, Allen Piscitello via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
> Even so, decentralization is a means to an end - not an end-goal. It is essential for Bitcoin to be a useful alternative, of course.
I agree. What about decentralization in development? Gavin recently said that he wants to "get to the point where there will be multiple robust implementations of the core protocol."
When I look at this image (https://i.imgur.com/zivHJvY.gif) illustrating centralization in nodes, mining and development, the biggest source of concern for me is the 85% node share around Bitcoin Core. With this level of centralization, it may be possible in the future for a group of coders to prevent important changes from being made in a timely fashion (e.g., should their interests no longer align with those of the larger Bitcoin community).
It is my opinion, then, that we should support multiple implementations of the Bitcoin protocol, working to reduce the network's dependency on Core.
Best regards,
Peter R
[-- Attachment #2: Type: text/html, Size: 1682 bytes --]
next prev parent reply other threads:[~2015-08-31 23:33 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 20:06 [bitcoin-dev] Your Gmaxwell exchange Monarch
2015-08-31 20:27 ` Justus Ranvier
2015-08-31 20:48 ` Monarch
2015-08-31 21:24 ` Allen Piscitello
2015-08-31 21:42 ` Monarch
2015-08-31 21:54 ` Justus Ranvier
2015-08-31 22:53 ` Monarch
2015-08-31 23:24 ` Justus Ranvier
2015-09-01 0:02 ` Milly Bitcoin
2015-09-01 9:25 ` Jorge Timón
2015-08-31 23:32 ` Peter R [this message]
2015-08-31 23:47 ` s7r
2015-09-01 2:16 ` [bitcoin-dev] Let's kill Bitcoin Core and allow the green shoots of a garden of new implementations to grow from its fertile ashes Peter R
2015-09-01 2:25 ` Gregory Maxwell
2015-09-01 8:42 ` Adam Back
2015-09-01 10:16 ` Chris D'Costa
2015-09-01 11:20 ` Monarch
2015-09-01 12:24 ` Wladimir
2015-09-01 22:06 ` s7r
2015-09-01 11:44 ` [bitcoin-dev] Your Gmaxwell exchange Monarch
2015-09-01 11:11 ` Monarch
2015-09-01 15:59 ` Dave Collins
2015-09-01 16:51 ` Monarch
2015-09-01 18:37 ` Eric Voskuil
2015-09-01 20:08 ` Monarch
[not found] <CAEgR2PFB3h_8fr=d8HegRSD0XdooimhFKtLR4vKr2QXv+EwBfQ@mail.gmail.com>
[not found] ` <AD284610-4F40-445C-A074-CC94EDFFCBA8@gmx.com>
2015-08-30 3:25 ` Gregory Maxwell
2015-08-30 4:13 ` Peter R
2015-08-30 4:57 ` Gregory Maxwell
2015-08-30 6:38 ` Adam Ritter
2015-08-31 18:55 ` Justus Ranvier
2015-08-31 19:11 ` Mike Hearn
2015-09-01 20:29 ` Wladimir J. van der Laan
2015-09-02 18:51 ` Justus Ranvier
2015-09-01 2:30 ` Oliver Petruzel
2015-08-30 7:41 ` Peter R
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=5A3D7824-F1E3-421B-A32A-0EF21DD215BD@gmx.com \
--to=peter_r@gmx.com \
--cc=allen.piscitello@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.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