From: Troy Benjegerdes <hozer@hozed•org>
To: Luke-Jr <luke@dashjr•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Embedded consensus system upgrade procedures
Date: Sun, 9 Feb 2014 12:11:32 -0600 [thread overview]
Message-ID: <20140209181132.GF3180@nl.grid.coop> (raw)
In-Reply-To: <201402091725.42306.luke@dashjr.org>
On Sun, Feb 09, 2014 at 05:25:41PM +0000, Luke-Jr wrote:
> 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.
I don't quite see how, There is nothing that 'forces' me to upgrade,
unless I have chosen to run an operating system (MacOS, Windows, Android)
that have automatic don't-ask-the-user update mechanisms.
The bigger problem with 'asset transfer' of assets which do not exist
soley in the blockchain is including the consensus of relevant local and
distributed legal jurisdictions.
For example, just because the 'colored coin' and blockchain consensus is
that I 'electronically' signed a mortgage document giving some random
internet company the rights to foreclose on my home does not mean that
my local county Judge or Sheriff are going to do anything if the internet
company cannot produce the original paper document with ink signature.
The only 'assertion' of central authority here is people who download and
run the code and submit to whatever the code asserts they are supposed to do.
At least with the 'central authority' of the big-business bitcoin developer
cabal I can read the code before I submit to it's central authority, and
this is a significant improvement over amgibuous legislation or proprietary
high-frequency trading algorithms.
next prev parent reply other threads:[~2014-02-09 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 17:12 Peter Todd
2014-02-09 17:25 ` Luke-Jr
2014-02-09 18:09 ` Peter Todd
2014-02-09 18:11 ` Troy Benjegerdes [this message]
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=20140209181132.GF3180@nl.grid.coop \
--to=hozer@hozed$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/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