public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Marcel Jamin <marcel@jamin.net>
To: bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Simplifying the blocksize limit debate
Date: Tue, 18 Aug 2015 08:38:05 +0200	[thread overview]
Message-ID: <CAAUq486afiWsDzMhGsYmX3v5AsWmaHNq9taS-azUodg5cWWRKA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

I'm going to list a few assumtions / observations / understandings around
this debate. Please point out the incorrect ones.

* Most developers here agree that 1 MB is not a magic constant and that the
limit has to increase eventually.

* Most developers want to reduce the amount of policy decisions
bitcoin-core makes as much as possible.

* The most conservative option for the 4 billion dollar system that is
bitcoin is to keep the limit.

* Technological growth in bandwidth, cpu and storage exists and relative to
that growth, the blocksize limit is effectively decreased. Keeping the
limit as it is today, or was five years ago, means we need to adjust for
technological growth.

* Doing so will not reduce current decentralization, however measured.

* Increasing the blocksize limit will always require a hard-fork.
Decreasing, or stopping the growth of the blocksize limit will always be
possible via soft-fork.

* Problems arising from underestimating the need for a larger blocksize
limit are increasingly harder to fix. Problems arising from a limit that is
getting too high are more easy to fix.

* This means we can be optimistic when estimating future technological
growth.

[-- Attachment #2: Type: text/html, Size: 1448 bytes --]

                 reply	other threads:[~2015-08-18  6:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAAUq486afiWsDzMhGsYmX3v5AsWmaHNq9taS-azUodg5cWWRKA@mail.gmail.com \
    --to=marcel@jamin.net \
    --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