From: Patrick Strateman <patrick.strateman@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Minimum Block Size
Date: Sun, 16 Aug 2015 18:20:49 -0700 [thread overview]
Message-ID: <55D136F1.7010104@gmail.com> (raw)
In-Reply-To: <CADm_WcbEkpdKNF-LCAVDyRpip5W+4tdVq0mn3PzKpZgaZtS4Mw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1354 bytes --]
The first question to answer here is simple:
What value would there be in requiring a minimum block size?
I see no value.
On 08/16/2015 05:30 PM, Jeff Garzik via bitcoin-dev wrote:
> "minimum" an interesting topic.
>
> - Traffic levels may not produce a minimum size block
> - Miners can always collude to produce a lowered maximum block size, a
> sort of minimum maximum
>
>
>
> On Sun, Aug 16, 2015 at 12:41 PM, Levin Keller via bitcoin-dev
> <bitcoin-dev@lists•linuxfoundation.org
> <mailto:bitcoin-dev@lists•linuxfoundation.org>> wrote:
>
> Hey everyone,
>
> as with the current "max block size" debate I was wondering: Is
> anyone here in favor of a minimum block size (say 2 MB or so)? If
> so I would be interested in an exchange (maybe off-list) of ideas.
> I am in favor of a lower limit and am giving it quite a bit of
> thought at the moment.
>
> Cheers
>
> Levin
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> <mailto:bitcoin-dev@lists•linuxfoundation.org>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Type: text/html, Size: 3262 bytes --]
next prev parent reply other threads:[~2015-08-17 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 16:41 Levin Keller
2015-08-16 16:52 ` Mark Friedenbach
2015-08-17 0:30 ` Jeff Garzik
2015-08-17 1:20 ` Patrick Strateman [this message]
2015-08-17 16:18 ` Jorge Timón
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=55D136F1.7010104@gmail.com \
--to=patrick.strateman@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.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