public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@gmail.com>
To: Levin Keller <post@levinkeller.de>
Cc: "bitcoin-dev@lists.linuxfoundation.org"
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Minimum Block Size
Date: Sun, 16 Aug 2015 20:30:05 -0400	[thread overview]
Message-ID: <CADm_WcbEkpdKNF-LCAVDyRpip5W+4tdVq0mn3PzKpZgaZtS4Mw@mail.gmail.com> (raw)
In-Reply-To: <CAG86ZOzEnjMw4xam5oUuuvyfoAps=47j418cZcw9BLs-yUCB2g@mail.gmail.com>

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

"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> 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
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

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

  parent reply	other threads:[~2015-08-17  0:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16 16:41 [bitcoin-dev] Minimum Block Size Levin Keller
2015-08-16 16:52 ` Mark Friedenbach
2015-08-17  0:30 ` Jeff Garzik [this message]
2015-08-17  1:20   ` Patrick Strateman
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=CADm_WcbEkpdKNF-LCAVDyRpip5W+4tdVq0mn3PzKpZgaZtS4Mw@mail.gmail.com \
    --to=jgarzik@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=post@levinkeller.de \
    /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