From: Monarch <monarch@cock.li>
To: Eric Voskuil <eric@voskuil.org>
Cc: bitcoin-dev@lists.linuxfoundation.org, libbitcoin@lists.dyne.org
Subject: Re: [bitcoin-dev] Your Gmaxwell exchange
Date: Tue, 01 Sep 2015 20:08:37 +0000 [thread overview]
Message-ID: <ec50844ebf2109364e87af0ab1a623af@cock.li> (raw)
In-Reply-To: <55E5F05E.9060409@voskuil.org>
On 2015-09-01 18:37, Eric Voskuil wrote:
> Whether intended or otherwise this is an attack on the idea of
> decentralized bitcoin development. The option to fork or roll your own
> is open source, not decentralization. Decentralization requires
> *actually doing so*. One step down that path, even for a fork, is a
> major commitment.
>
> Common consensus check code is now available in several bitcoin
> implementations. The claim that this is outrageously difficult is
> misleading. It's just engineering work that needs to get done if
> Bitcoin
> is to survive.
>
There's no requirement for there to be multiple interpretations of the
consensus code, this is why libbitcoinconsensus exists. Why do you
think Bitcoins survival is predicated on reimplementation?
> These are issues that affect the satoshi client as much as other
> implementations, and therefore don't support your premise.
>
I'm aware that these problems apply to Bitcoin Core.
next prev parent reply other threads:[~2015-09-01 20:08 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
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 [this message]
[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=ec50844ebf2109364e87af0ab1a623af@cock.li \
--to=monarch@cock.li \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=eric@voskuil.org \
--cc=libbitcoin@lists.dyne.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