diff options
| author | Tom Zander <tomz@freedommail.ch> | 2017-01-02 20:01:11 +0100 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2017-01-02 19:00:20 +0000 |
| commit | 4ca611f1a1e4bf3ffd565226083e835091d00ba8 (patch) | |
| tree | 55bdbffd24d7974e8db553cb00e866e5fd14612f | |
| parent | 89e3150d7fe0d8585575a58202095f13cfb88ab2 (diff) | |
| download | pi-bitcoindev-4ca611f1a1e4bf3ffd565226083e835091d00ba8.tar.gz pi-bitcoindev-4ca611f1a1e4bf3ffd565226083e835091d00ba8.zip | |
Re: [bitcoin-dev] BIP - 'Block75' - New algorithm
| -rw-r--r-- | d3/8ed8d3fac19dd3fe08df07e27074247fcd10e5 | 67 |
1 files changed, 67 insertions, 0 deletions
diff --git a/d3/8ed8d3fac19dd3fe08df07e27074247fcd10e5 b/d3/8ed8d3fac19dd3fe08df07e27074247fcd10e5 new file mode 100644 index 000000000..7da2fa9f1 --- /dev/null +++ b/d3/8ed8d3fac19dd3fe08df07e27074247fcd10e5 @@ -0,0 +1,67 @@ +Return-Path: <tomz@freedommail.ch> +Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org + [172.17.192.35]) + by mail.linuxfoundation.org (Postfix) with ESMTPS id 828DF279 + for <bitcoin-dev@lists.linuxfoundation.org>; + Mon, 2 Jan 2017 19:00:20 +0000 (UTC) +X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 +Received: from mx-out01.mykolab.com (mx.kolabnow.com [95.128.36.1]) + by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6CCF2130 + for <bitcoin-dev@lists.linuxfoundation.org>; + Mon, 2 Jan 2017 19:00:19 +0000 (UTC) +X-Virus-Scanned: amavisd-new at kolabnow.com +X-Spam-Score: -2.9 +X-Spam-Level: +X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW + autolearn=ham version=3.3.1 +Received: from mx03.mykolab.com (mx03.mykolab.com [10.20.7.101]) + by mx-out01.mykolab.com (Postfix) with ESMTPS id 2F2C26031C; + Mon, 2 Jan 2017 20:00:16 +0100 (CET) +From: Tom Zander <tomz@freedommail.ch> +To: "t. khan" <teekhan42@gmail.com>, + Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> +Date: Mon, 02 Jan 2017 20:01:11 +0100 +Message-ID: <2273244.fZU5ULDz4l@cherry> +In-Reply-To: <CAGCNRJoN7u3yvzitH2KSmVty-p0tX9jxWLHPb8uO5CPZmxmoRg@mail.gmail.com> +References: <CAGCNRJoN7u3yvzitH2KSmVty-p0tX9jxWLHPb8uO5CPZmxmoRg@mail.gmail.com> +MIME-Version: 1.0 +Content-Transfer-Encoding: 7Bit +Content-Type: text/plain; charset="us-ascii" +X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on + smtp1.linux-foundation.org +X-Mailman-Approved-At: Mon, 02 Jan 2017 19:12:26 +0000 +Subject: Re: [bitcoin-dev] BIP - 'Block75' - New algorithm +X-BeenThere: bitcoin-dev@lists.linuxfoundation.org +X-Mailman-Version: 2.1.12 +Precedence: list +List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org> +List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> +List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> +List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> +List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> +List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> +X-List-Received-Date: Mon, 02 Jan 2017 19:00:20 -0000 + +On Monday, 2 January 2017 13:04:37 CET t. khan via bitcoin-dev wrote: +> Thoughts? + +This proposal doesn't change the block size, it only changes the maximum +block size. Which is expected, nothing bad there. + +The direct consequence of this, though is that the miners set the maximum +block size. Because they decide on the actual created block size. + +This leads me to the simple question why we can't just give the miners full +control of the maximum block size directly? + +The fact of the matter is that miners have for the full history of Bitcoin +been able to set the block size, until they hit the 1MB limit. +And your proposal keeps that property, but why have a maximum in the +protocol? +-- +Tom Zander +Blog: https://zander.github.io +Vlog: https://vimeo.com/channels/tomscryptochannel + |