public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Justus Ranvier <justus@openbitcoinprivacyproject.org>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] block-size tradeoffs & hypothetical alternatives (Re: Block size increase oppositionists: please clearly define what you need done to increase block size to a static 8MB, and help do it)
Date: Tue, 30 Jun 2015 15:08:46 -0500	[thread overview]
Message-ID: <5592F74E.80200@openbitcoinprivacyproject.org> (raw)
In-Reply-To: <CALqxMTG1=+F8DSeRAThtTSmj4F3YhgUiCbqJ1CfBy9Z-LLZvSQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 986 bytes --]

On 06/30/2015 02:54 PM, Adam Back wrote:
> Decentralisation is key to Bitcoin's security model, and it's
> differentiating properties.

Continually repeating this statement without defining terms or providing
evidence does not make it true or informative.

"Decentralization" is a popular buzzword these days, but how about
stating the problem description in a way that is more precise and accurate?

One of Bitcoin's differentiating properties is that it prevents double
spending without using a trusted third party.

Now instead of arguing about some nebulous "decentralization" that
nobody can define or measure, we can talk about more helpful questions like:

Under what circumstances will miners and/or nodes behave as a trusted
third party (collusion)?

What incentives exist which increase, and which reduce, any tendencies
that may exist for nodes to collude?

In what ways specifically does MAX_BLOCK_SIZE relate to either of the
following questions?


[-- Attachment #1.2: 0xEAD9E623.asc --]
[-- Type: application/pgp-keys, Size: 18667 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply	other threads:[~2015-06-30 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 19:54 [bitcoin-dev] block-size tradeoffs & hypothetical alternatives (Re: Block size increase oppositionists: please clearly define what you need done to increase block size to a static 8MB, and help do it) Adam Back
2015-06-30 20:08 ` Justus Ranvier [this message]
2015-06-30 20:29   ` Milly Bitcoin
2015-06-30 22:55 ` Simon Liu
2015-06-30 22:56 ` Tom Harding

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=5592F74E.80200@openbitcoinprivacyproject.org \
    --to=justus@openbitcoinprivacyproject.org \
    --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