From: Justus Ranvier <justus@openbitcoinprivacyproject•org>
To: Monarch <monarch@cock•li>, 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:54:30 -0500 [thread overview]
Message-ID: <55E4CD16.3010508@openbitcoinprivacyproject.org> (raw)
In-Reply-To: <91e79f981126ebe62e30df26e0c7ec50@cock.li>
[-- Attachment #1.1: Type: text/plain, Size: 1849 bytes --]
On 08/31/2015 04:42 PM, Monarch wrote:
> The justification for the existence of Bitcoins hinges on it. What is
> described in the whitepaper is a system without the trust of third
> parties to process electronic payments, this can not exist without
> decentralization. Absent any unforseen revelations this is a
> requirement rather than a suggestion or fleeting fancy. Below a
> decentralized Bitcoin you are free to make systems as centralized as
> you please without affecting the parent, below a centralized Bitcoin
> there is no room to make it less. We really only have one shot at a
> properly bootstrapped, decentralized currency, and it would be a great
> shame to mess up the one we have with hasty decision making for
> unclear goals.
You keep using the word "decentralized" without explaining (and most
likely, understanding) what it means.
You say:
> a system without the trust of third parties to process electronic payments
What does it mean to use a decentralized network instead of a trusted
third party to process electronic payments? What undesirable actions can
a trusted third party perform that a decentralized network can not perform?
The answer to those questions are the *actual* goals, for which
decentralization is just one portion of a solution.
It might be helpful to organize Bitcoin's various existing, potential,
rejected, and proposed features using the Kano model:
https://en.wikipedia.org/wiki/Kano_model
Example: The ability of one entity to spend another entity's Bitcoins
without their consent is a reverse quality.
It would at least give us something objective to talk about.
--
Justus Ranvier
Open Bitcoin Privacy Project
http://www.openbitcoinprivacyproject.org/
justus@openbitcoinprivacyproject•org
E7AD 8215 8497 3673 6D9E 61C4 2A5F DA70 EAD9 E623
[-- Attachment #1.2: 0xEAD9E623.asc --]
[-- Type: application/pgp-keys, Size: 18667 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2015-08-31 22:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 20:06 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 [this message]
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
[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=55E4CD16.3010508@openbitcoinprivacyproject.org \
--to=justus@openbitcoinprivacyproject$(echo .)org \
--cc=allen.piscitello@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=monarch@cock$(echo .)li \
/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