public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Hampus Sjöberg" <hampus.sjoberg@gmail•com>
To: Luke Dashjr <luke@dashjr•org>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP - 'Block75' - New algorithm
Date: Mon, 13 Feb 2017 12:21:44 +0100	[thread overview]
Message-ID: <CAFMkqK_hKFZc0bnO17ONpM1v5D2nDgu5-u5MTByJF0xEYZ3tAQ@mail.gmail.com> (raw)
In-Reply-To: <201701022119.11115.luke@dashjr.org>

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

> It gives miners complete control over the limit. They can make blocks of
any size (within the current limit), thus triggering the conditions by
which your proposal would raise the limit further.

There might be a long term incentive to keep increasing the blocksize, to
further centralize the network (and kick smaller miners out), but it comes
with the cost of losing out on transaction fees.
Miners have always needed to plan for the short term, I see no rational
scenario where miners would spam their blocks with their own transactions
(or low fee transactions) to keep increasing the blocksize limit.

Hampus

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

  parent reply	other threads:[~2017-02-13 11:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 18:04 t. khan
2017-01-02 19:01 ` Tom Zander
2017-01-02 19:32   ` t. khan
2017-01-02 20:35     ` Tom Zander
2017-01-02 21:05       ` t. khan
2017-01-02 22:33         ` Tom Zander
2017-01-02 21:19       ` Luke Dashjr
2017-01-02 22:01         ` Tom Zander
2017-01-03 14:28         ` t. khan
2017-02-13 11:21         ` Hampus Sjöberg [this message]
2017-01-02 20:04 ` Luke Dashjr
2017-01-02 20:41   ` t. khan

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=CAFMkqK_hKFZc0bnO17ONpM1v5D2nDgu5-u5MTByJF0xEYZ3tAQ@mail.gmail.com \
    --to=hampus.sjoberg@gmail$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --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