From: Levin Keller <post@levinkeller•de>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Minimum Block Size
Date: Sun, 16 Aug 2015 16:41:05 +0000 [thread overview]
Message-ID: <CAG86ZOzEnjMw4xam5oUuuvyfoAps=47j418cZcw9BLs-yUCB2g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 313 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 417 bytes --]
next reply other threads:[~2015-08-16 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 16:41 Levin Keller [this message]
2015-08-16 16:52 ` Mark Friedenbach
2015-08-17 0:30 ` Jeff Garzik
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='CAG86ZOzEnjMw4xam5oUuuvyfoAps=47j418cZcw9BLs-yUCB2g@mail.gmail.com' \
--to=post@levinkeller$(echo .)de \
--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