public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Richard Moore <me@ricmoo•com>
To: Michael Naber <mickeybob@gmail•com>
Cc: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Block size increase oppositionists: please clearly define what you need done to increase block size to a static 8MB, and help do it
Date: Tue, 30 Jun 2015 12:03:02 -0400	[thread overview]
Message-ID: <8F54D4D6-A2FE-4F20-9927-712187B2B03A@ricmoo.com> (raw)
In-Reply-To: <CALgxB7uvtKCNM-nH+aqqPa4KNf5O6Gx4GmgZY7Oq8=A24wCrfA@mail.gmail.com>

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

I’m not planning to take a firm stance against or for, but one problem with your analogy is that airplanes [currently] are not elastic (until we get TARDIS technology, or semi-TARDIS-like technology); they take up space and resources proportional to their capacity.

It is not the block size that is increasing, it is the *maximum* block size… So, it’s more like saying the *maximum* airplane size is increasing, which I think may be somewhat true (although, I agree, probably not exponentially). It would be more like an airplane whose capacity was doubling every two years, but would shrink when that extra capacity was not needed and only consume the maintenance, fuel, et cetera needed for its current size.

My semi-firm-ish stance is that kicking the can down the road with a static increase is less better. We can always soft-fork the limit down if the *actual* block size is growing too fast. When (and/or if) we need to. I also think 8MB is a rather large jump, for either static or dynamic.

*shrug*

RicMoo


> On Jun 30, 2015, at 11:34 AM, Michael Naber <mickeybob@gmail•com> wrote:
> 
> As you know I'm trying to lobby for a block size increase to a static 8MB. 
> 
> I'm happy to try to get the testing done that people want done for this, but I think the real crux of this issue is that we need to get consensus that we intend to continually push the block size upward as bounded only by technology.
> 
> Imagine an engineer (Gavin) at Boeing (Bitcoin Core) said he was going to build an airplane (block) that was going to move 8x as many people (transactions) as today’s planes (blocks), all while costing about the same amount to operate. Imagine he then went on to tell you that he expects to double the plane’s (block's) capacity every two years! 
> 
> Without full planes (blocks), will the airlines (miners) go out of business, since planes (blocks) will never be full and the cost to add people (transactions) to a plane (block) will approach zero? Probably not. Airlines (miners) still have to pay for pilots, security screening staff, fuel, etc (engineers, hash rate, electricity, etc) so even if their airplanes (blocks) can hold limitless people (transactions), they would still have to charge sufficient fees to stay in business.
> 
> What tests do you need done to move to 8MB? Pitch in and help get those tests done; agree that we'll run more tests next year or the year after when technology might allow for 16 MB blocks. Do you really want to be the guy holding back bigger planes? Do you really want to artificially constrain block size below what technology allows? 
> 
> In the face of such strong market demand for increased capacity in globally aware global consensus, do you really think you can prevent supply from meeting demand when the technology exists to deliver it? Do you really want to force a fork because you and others won't agree to a simple raise to a static 8MB? 
> 
> Do what's best for Bitcoin and define what needs to get done to agree to a simple block size increase to a static 8MB.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸¸.·´¯`·.¸><(((º>

Richard Moore ~ Founder
Genetic Mistakes Software inc.
phone: (778) 882-6125
email: ricmoo@geneticmistakes•com <mailto:ricmoo@geneticmistakes•com>
www: http://GeneticMistakes.com <http://geneticmistakes.com/>

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

  reply	other threads:[~2015-06-30 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30 15:34 Michael Naber
2015-06-30 16:03 ` Richard Moore [this message]
2015-06-30 16:15 ` Venzen Khaosan
2015-06-30 16:25   ` Peter Todd
2015-06-30 16:35     ` Michael Naber
2015-06-30 19:59       ` Bryan Cheng

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=8F54D4D6-A2FE-4F20-9927-712187B2B03A@ricmoo.com \
    --to=me@ricmoo$(echo .)com \
    --cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
    --cc=mickeybob@gmail$(echo .)com \
    /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