public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Dashjr <luke@dashjr.org>
To: bitcoin-dev@lists.linuxfoundation.org, Erik <erik.fors@startmail.com>
Subject: Re: [bitcoin-dev] BIP proposal - Max block size
Date: Fri, 13 Nov 2015 19:37:02 +0000	[thread overview]
Message-ID: <201511131937.03430.luke@dashjr.org> (raw)
In-Reply-To: <5645E095.4050704@startmail.com>

On Friday, November 13, 2015 1:07:33 PM Erik via bitcoin-dev wrote:
> Hi devs. I was discussing the BIP proposals concerning max block size
> yesterday in the #bitcoin channel. I believe that BIP101 fully utilized
> will outperform consumer hardware soon or later and thereby centralize
> Bitcoin. I would therefore like to do a different proposal:

It doesn't look like you've considered BIP103 or newer BIPs? Especially, I'd 
suggest you look at and work with John Sacco who just the other day posted a 
BIP draft very similar-looking to yours. My overall impression of your summary 
is that it is unnecessarily over-complicated and underspecified. How does the 
2^(1/2) block size limit actually work? This is not a very precise number, so 
it seems liable to produce rounding errors in different implementations. 
Additionally, the miner voting thing seems pointless since miners can already 
softfork lower limits. It would be beneficial to express the current 
possibility so full nodes can enforce it, but this would be expressed as an 
unlimited simple-majority vote to reduce the limit. Probably it would be ideal 
to separate this off from the hardfork BIP, since it's fairly tangent to it.

Luke


  reply	other threads:[~2015-11-13 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 13:07 [bitcoin-dev] BIP proposal - Max block size Erik
2015-11-13 19:37 ` Luke Dashjr [this message]
2015-11-14 15:25   ` Erik

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=201511131937.03430.luke@dashjr.org \
    --to=luke@dashjr.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=erik.fors@startmail.com \
    /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