public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Elliot Olds <elliot.olds@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Block size following technological growth
Date: Wed, 5 Aug 2015 00:29:50 -0700	[thread overview]
Message-ID: <CA+BnGuFNOjzLaiPPnUSi-rkU94UMgmP30Si8N3oBSYG0q8j-_w@mail.gmail.com> (raw)
In-Reply-To: <CABm2gDpp5+hkHmd6op6PPW658siKoEMRDfTWiEHHM7vJSLDhyA@mail.gmail.com>

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

On Tue, Aug 4, 2015 at 4:59 AM, Jorge Timón <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> Also I don't think "hitting the limit" must be necessarily harmful and
> if it is, I don't understand why hitting it at 1MB will be more
> harmful than hitting it at 2MB, 8MB or 8GB.


I don't think merely hitting the limit is bad. The level of tx fees in
equilibrium give some clue as to the level of harm being done. If fees are
at $5/tx at 1MB, it's about as bad as if fees are at $5/tx at 4MB.

There is NO criterion based on mining centralization to decide between
> 2 sizes in favor of the small one.
> It seems like the rationale it's always "the bigger the better" and
> the only limitation is what a few people concerned with mining
> centralization (while they still have time to discuss this) are
> willing to accept. If that's the case, then there won't be effectively
> any limit in the long term and Bitcoin will probably fail in its
> decentralization goals.
> I think its the proponents of a blocksize change who should propose
> such a criterion and now they have the tools to simulate different
> block sizes.
>

In the absence of harder data, it might be interesting to use these
simulations to graph centralization pressure as a function of bandwidth
cost over time (or other historical variables that affect centralization).
For instance, look at how high centralization pressure was in 2009
according to the simulations, given how cheap/available bandwidth was then,
compared to 2010, 2011, etc. Then we could figure out: given today's
bandwidth situation, what size blocks right now would give us the same
centralization pressure that we had in 2011, 2012, 2013, etc?

Of course this doesn't mean we should blindly assume that the level of
centralization pressure in 2012 was acceptable, and therefore any block
size increase that results in the same amount of pressure now should be
acceptable. But it might lead to a more productive discussion.


> I want us to simulate many blocksizes before rushing into a decision
> (specially because I disagree that taking a decision there is urgent
> in the first place).


IMO it is not urgent if the core devs are committed to reacting to a huge
spike in tx fees with a modest block size increase in a relatively short
time frame, if they judge the centralization risks of that increase to be
small. Greg Maxwell posted on reddit a while back something to the effect
of "the big block advocates are overstating the urgency of the block size
increase, because if there was actually a situation that required us to
increase block size, we could make the increase when it was actually
needed." I found that somewhat persuasive, but I am concerned that I
haven't seen any discussion of what the "let's wait for now" camp would
consider a valid reason to increase block size in the short term, and how
they'd make the tradeoff with tx fees or whatever else was necessitating
the increase.

Jorge, if a fee equilibrium developed at 1MB of $5/tx, and you somehow knew
with certainty that increasing to 4MB would result in a 20 cent/tx
equilibrium that would last for a year (otherwise fees would stay around $5
for that year), would you be in favor of an increase to 4MB?

For those familiar with the distinction between near/far mode thinking
popularized by Robin Hanson: focusing on concrete examples like this
encourages problem solving and consensus, and focusing on abstract
principles (like decentralization vs. usability in general) leads to people
toward using argument to signal their alliances and reduce the status of
their opponents. I think it'd be very helpful if more 1MB advocates
described what exactly would make them say "OK, in this situation a block
size increase is needed, we should do one quickly!", and also if
Gavin/Mike/Jeff described what hypothetical scenarios and/or test results
would make them want to stick with 1MB blocks for now.

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

  parent reply	other threads:[~2015-08-05  7:29 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 14:25 [bitcoin-dev] Block size following technological growth Pieter Wuille
2015-07-30 15:04 ` Greg Sanders
2015-07-30 15:12 ` Jorge Timón
2015-07-30 16:23   ` Jameson Lopp
2015-07-30 16:36     ` Bryan Bishop
2015-07-30 16:43       ` Jameson Lopp
2015-07-30 16:36   ` Venzen Khaosan
2015-07-30 17:51     ` Jorge Timón
2015-07-30 18:00       ` Jorge Timón
2015-07-30 16:56   ` Gary Mulder
2015-07-30 17:13     ` Mark Friedenbach
2015-07-30 16:20 ` Gavin Andresen
2015-07-30 16:41   ` Suhas Daftuar
2015-07-30 16:48   ` Adam Back
2015-07-30 16:49   ` Pieter Wuille
2015-07-31 10:16     ` Mike Hearn
2015-07-31 11:43       ` Venzen Khaosan
2015-07-31 11:51       ` Jorge Timón
2015-07-31 12:15         ` Mike Hearn
2015-07-31 13:07           ` Marcel Jamin
2015-07-31 14:33           ` Jorge Timón
2015-07-31 14:58             ` Mike Hearn
2015-07-31 15:28               ` Venzen Khaosan
2015-07-31 20:09               ` Elliot Olds
2015-08-04 10:35               ` Jorge Timón
2015-08-04 11:04                 ` Hector Chu
2015-08-04 11:27                   ` Pieter Wuille
2015-08-04 11:34                     ` Hector Chu
2015-08-04 12:10                       ` Venzen Khaosan
2015-08-04 13:13                       ` Jorge Timón
2015-08-04 13:28                         ` Hector Chu
2015-08-04 13:42                           ` Venzen Khaosan
2015-08-04 17:59                           ` Jorge Timón
2015-08-04 13:12                     ` Gavin Andresen
2015-08-04 13:54                       ` Pieter Wuille
2015-08-04 14:30                       ` Venzen Khaosan
2015-08-04 14:43                         ` [bitcoin-dev] Fwd: " Venzen Khaosan
2015-08-04 14:45                       ` [bitcoin-dev] " Alex Morcos
2015-08-05  8:14                       ` Gareth Williams
2015-08-04 11:59                   ` Jorge Timón
2015-08-04 12:19                     ` Hector Chu
2015-08-04 13:34                       ` Venzen Khaosan
2015-08-04 13:37                       ` Jorge Timón
2015-08-05  7:29                     ` Elliot Olds [this message]
2015-08-06  1:26                       ` Jorge Timón
2015-08-06 13:40                         ` Gavin Andresen
2015-08-06 14:06                           ` Pieter Wuille
2015-08-06 14:21                             ` Gavin Andresen
2015-08-06 14:53                               ` Pieter Wuille
     [not found]                                 ` <CABsx9T0B2bZrFHxYR_QNwBmxskQx31zt=QE5BJAYjcOo7wbo3A@mail.gmail.com>
2015-08-06 15:24                                   ` [bitcoin-dev] Fwd: " Gavin Andresen
2015-08-06 15:26                                     ` Pieter Wuille
2015-08-06 18:43                                       ` Michael Naber
2015-08-06 18:52                                         ` Pieter Wuille
2015-08-07 16:06                                           ` Thomas Zander
2015-08-07 16:30                                             ` Pieter Wuille
2015-08-07 17:00                                               ` Thomas Zander
2015-08-07 17:09                                                 ` Pieter Wuille
2015-08-07 21:35                                                   ` Thomas Zander
2015-08-07 22:53                                                     ` Adam Back
2015-08-08 16:54                                                       ` Dave Scotese
2015-08-07 17:50                                               ` Gavin Andresen
2015-08-07 18:05                                                 ` Jameson Lopp
2015-08-07 18:10                                                 ` Pieter Wuille
2015-08-07 21:43                                                   ` Thomas Zander
2015-08-07 22:00                                                   ` Thomas Zander
2015-08-06 16:19                                 ` [bitcoin-dev] " Tom Harding
2015-08-06 21:56                               ` Peter Todd
2015-08-06 15:25                           ` Jorge Timón
2015-08-06 16:03                             ` Gavin Andresen
2015-08-06 16:11                               ` Mike Hearn
2015-08-06 17:15                               ` Jorge Timón
2015-08-06 19:42                                 ` Gavin Andresen
2015-08-06 20:01                                   ` Pieter Wuille
2015-08-06 21:51                                   ` Jorge Timón
2015-08-06 23:09                         ` Elliot Olds
2015-08-10 19:28                           ` Jorge Timón
2015-08-11  5:48                             ` Elliot Olds
2015-08-09 18:46                   ` [bitcoin-dev] What Lightning Is Tom Harding
2015-08-09 18:54                     ` Mark Friedenbach
2015-08-09 20:14                       ` Hector Chu
     [not found]                         ` <CAOG=w-s9KsaPwveSpgdvsVTWUDV77YY7Em7NZGyxSQMMCccYSg@mail.gmail.com>
2015-08-09 20:48                           ` Hector Chu
2015-08-10  4:48                             ` Joseph Poon
2015-08-10 17:03                         ` odinn
2015-08-10 17:14                           ` Pieter Wuille
2015-08-10 17:45                             ` odinn
2015-08-09 21:27                       ` Tom Harding
2015-08-09 21:40                         ` Chris Pacia
2015-08-09 21:45                         ` Hector Chu
2015-08-09 21:57                           ` Patrick Strateman
2015-08-09 22:03                             ` Hector Chu
2015-08-09 22:36                               ` Patrick Strateman
2015-08-10  1:52                           ` Tom Harding
2015-08-10  3:31                             ` Patrick Strateman
2015-08-09 22:06                         ` Patrick Strateman
2015-08-09 22:09                           ` Hector Chu
2015-08-09 22:27                             ` Patrick Strateman
2015-08-09 22:30                               ` Hector Chu
2015-08-09 22:44                             ` Gavin Andresen
2015-08-09 22:51                               ` Btc Drak
2015-08-10  8:27                                 ` Thomas Zander
2015-08-10  8:36                                   ` Patrick Strateman
2015-08-10  4:39                               ` Joseph Poon
2015-08-10 21:02                               ` Anthony Towns
2015-08-10 21:19                                 ` Anthony Towns
2015-08-10 21:43                                   ` Adam Back
2015-08-11  9:01                                     ` Hector Chu
2015-08-11 17:17                                       ` Simon Liu
2015-07-31 14:52           ` [bitcoin-dev] Block size following technological growth Bryan Bishop
2015-07-30 17:46   ` Jorge Timón
2015-08-02 22:35   ` Anthony Towns
2015-07-30 20:20 ` Thomas Zander

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=CA+BnGuFNOjzLaiPPnUSi-rkU94UMgmP30Si8N3oBSYG0q8j-_w@mail.gmail.com \
    --to=elliot.olds@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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