From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Embedded consensus system upgrade procedures
Date: Sun, 9 Feb 2014 17:25:41 +0000 [thread overview]
Message-ID: <201402091725.42306.luke@dashjr.org> (raw)
In-Reply-To: <20140209171214.GA20126@savin>
On Sunday, February 09, 2014 5:12:14 PM Peter Todd wrote:
> We have an embedded consensus system and we want to be able to upgrade
> it with new rules.
This asserts a central authority and gives developers too much power.
next prev parent reply other threads:[~2014-02-09 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 17:12 [Bitcoin-development] Embedded consensus system upgrade procedures Peter Todd
2014-02-09 17:25 ` Luke-Jr [this message]
2014-02-09 18:09 ` Peter Todd
2014-02-09 18:11 ` Troy Benjegerdes
2014-02-09 18:38 ` Peter Todd
2014-02-09 19:02 ` Troy Benjegerdes
2014-02-15 14:43 ` Jorge Timón
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=201402091725.42306.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/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