From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 2BAA1901 for ; Fri, 7 Aug 2015 19:15:55 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-io0-f180.google.com (mail-io0-f180.google.com [209.85.223.180]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0D1BF176 for ; Fri, 7 Aug 2015 19:15:54 +0000 (UTC) Received: by iodb91 with SMTP id b91so60949813iod.1 for ; Fri, 07 Aug 2015 12:15:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=WKKvGzK/OA2EuDFAUjpwAQneP+C3JyydKyFL9kP1O4U=; b=X2iAq8ItIeXjPnC9wjQIqV0BWXrs7uxkL3dlpIKlKGokngBQehPwROsJpmJV1JQwGQ dGanSl9PY5YGMUJHq5L7AJdk/2k/btKge2K3pZTeg15J5FAqbx1EwTFbG1oIA+M3kyVI esFDXicPFhuujRPtWkx92D8x/k2JUXv6abr0Wwqx3CumpjMGSBffCiVvIbrBQxe4CpqE +qDGpUM89lt5NVoaJmDf+l4B8R7jvAU+hOWCXU32GWcn68GzKr+r0qH+RFebcS3nINiv 8lQQUd//Gxge4FYB5uYDmKDGQmRCygsfjVZE+EnhcH5uXdWT8YyhpVtjkmGJ0HMqWZ2g RVyg== X-Gm-Message-State: ALoCoQmrsWPWkOWGfigZ5hgeHIGTg/j6goqz2S+SvrMOvIza3jWlgiiH0XPC8Vg1bMF3GMa+IFXf X-Received: by 10.107.130.166 with SMTP id m38mr11559095ioi.77.1438974953438; Fri, 07 Aug 2015 12:15:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.107.158.140 with HTTP; Fri, 7 Aug 2015 12:15:34 -0700 (PDT) X-Originating-IP: [172.56.16.232] In-Reply-To: References: From: Mark Friedenbach Date: Fri, 7 Aug 2015 12:15:34 -0700 Message-ID: To: Ryan Butler Content-Type: multipart/alternative; boundary=001a113eb9c8f0d199051cbd76c3 X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] Fees and the block-finding process X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Aug 2015 19:15:55 -0000 --001a113eb9c8f0d199051cbd76c3 Content-Type: text/plain; charset=UTF-8 Surely you have some sort of empirical measurement demonstrating the validity of that statement? That is to say you've established some technical criteria by which to determine how much centralization pressure is too much, and shown that Pieter's proposal undercuts expected progress in that area? On Fri, Aug 7, 2015 at 12:07 PM, Ryan Butler wrote: > Clarification... > > These are not mutually exclusive. We can design an increase to blocksize > that increases available space on chain AND follow technological > evolution. Peter's latest proposal is way too conservative on that front. > > And given Peter's assertion that demand is infinite there will still be a > an ocean of off chain transactions for the likes of blockstream to address. > On Aug 7, 2015 1:57 PM, "Ryan Butler" wrote: > >> Who said anything about scaling bitcoin to visa levels now? We're >> talking about an increase now that scales into the future at a rate that is >> consistent with technological progress. >> >> Peter himself said "So, I think the block size should follow >> technological evolution...". >> >> The blocksize increase proposals have been modeled around this very >> thing. It's reasonable to increase the blocksize to a point that a >> reasonable person, with reasonable equipment and internet access can run a >> node or even a miner with acceptable orphan rates. Most miners are spv >> mining anyways. The 8 or even 20 MB limits are within those parameters. >> >> These are not mutually exclusive. We can design an increase to blocksize >> that addresses both demand exceeding the available space AND follow >> technological evolution. Peter's latest proposal is way too conservative >> on that front. >> On Aug 7, 2015 1:25 PM, "Mark Friedenbach" wrote: >> >>> Please don't put words into Pieter's mouth. I guarantee you everyone >>> working on Bitcoin in their heart of hearts would prefer everyone in the >>> world being able to use the Bitcoin ledger for whatever purpose, if there >>> were no cost. >>> >>> But like any real world engineering issue, this is a matter of >>> tradeoffs. At the extreme it is simply impossible to scale Bitcoin to the >>> terrabyte sized blocks that would be necessary to service the entire >>> world's financial transactions. Not without sacrificing entirely the >>> protection of policy neutrality achieved through decentralization. And as >>> that is Bitcoin's only advantage over traditional consensus systems, you >>> would have to wonder what the point of such an endeavor would be. >>> >>> So *somewhere* you have to draw the line, and transactions below that >>> level are simply pushed into higher level or off-chain protocols. >>> >>> The issue, as Pieter and Jorge have been pointing out, is that technical >>> discussion over where that line should be has been missing from this debate. >>> >>> On Fri, Aug 7, 2015 at 10:47 AM, Ryan Butler via bitcoin-dev < >>> bitcoin-dev@lists.linuxfoundation.org> wrote: >>> >>>> Interesting position there Peter...you fear more people actually using >>>> bitcoin. The less on chain transactions the lower the velocity and the >>>> lower the value of the network. I would be careful what you ask for >>>> because you end up having nothing left to even root the security of these >>>> off chain transactions with and then neither will exist. >>>> >>>> Nobody ever said you wouldn't run out of capacity at any size. It's >>>> quite the fallacy to draw the conclusion from that statement that block >>>> size should remain far below a capacity it can easily maintain which would >>>> bring more users/velocity/value to the system. The outcomes of both of >>>> those scenarios are asymmetric. A higher block size can support more users >>>> and volume. >>>> >>>> Raising the blocksize isn't out of fear. It's the realization that we >>>> are at a point where we can raise it and support more users and >>>> transactions while keeping the downsides to a minimum (centralization etc). >>>> On Aug 7, 2015 11:28 AM, "Pieter Wuille via bitcoin-dev" < >>>> bitcoin-dev@lists.linuxfoundation.org> wrote: >>>> >>>>> On Fri, Aug 7, 2015 at 5:55 PM, Gavin Andresen < >>>>> gavinandresen@gmail.com> wrote: >>>>> >>>>>> On Fri, Aug 7, 2015 at 11:16 AM, Pieter Wuille < >>>>>> pieter.wuille@gmail.com> wrote: >>>>>> >>>>>>> I guess my question (and perhaps that's what Jorge is after): do you >>>>>>> feel that blocks should be increased in response to (or for fear of) such a >>>>>>> scenario. >>>>>>> >>>>>> >>>>>> I think there are multiple reasons to raise the maximum block size, >>>>>> and yes, fear of Bad Things Happening as we run up against the 1MB limit is >>>>>> one of the reasons. >>>>>> >>>>>> I take the opinion of smart engineers who actually do resource >>>>>> planning and have seen what happens when networks run out of capacity very >>>>>> seriously. >>>>>> >>>>> >>>>> This is a fundamental disagreement then. I believe that the demand is >>>>> infinite if you don't set a fee minimum (and I don't think we should), and >>>>> it just takes time for the market to find a way to fill whatever is >>>>> available - the rest goes into off-chain systems anyway. You will run out >>>>> of capacity at any size, and acting out of fear of that reality does not >>>>> improve the system. Whatever size blocks are actually produced, I believe >>>>> the result will either be something people consider too small to be >>>>> competitive ("you mean Bitcoin can only do 24 transactions per second?" >>>>> sounds almost the same as "you mean Bitcoin can only do 3 transactions per >>>>> second?"), or something that is very centralized in practice, and likely >>>>> both. >>>>> >>>>> >>>>>> And if so, if that is a reason for increase now, won't it be a reason >>>>>>> for an increase later as well? It is my impression that your answer is yes, >>>>>>> that this is why you want to increase the block size quickly and >>>>>>> significantly, but correct me if I'm wrong. >>>>>>> >>>>>> >>>>>> Sure, it might be a reason for an increase later. Here's my message >>>>>> to in-the-future Bitcoin engineers: you should consider raising the >>>>>> maximum block size if needed and you think the benefits of doing so (like >>>>>> increased adoption or lower transaction fees or increased reliability) >>>>>> outweigh the costs (like higher operating costs for full-nodes or the >>>>>> disruption caused by ANY consensus rule change). >>>>>> >>>>> >>>>> In general that sounds reasonable, but it's a dangerous precedent to >>>>> make technical decisions based on a fear of change of economics... >>>>> >>>>> -- >>>>> Pieter >>>>> >>>>> >>>>> _______________________________________________ >>>>> bitcoin-dev mailing list >>>>> bitcoin-dev@lists.linuxfoundation.org >>>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >>>>> >>>>> >>>> _______________________________________________ >>>> bitcoin-dev mailing list >>>> bitcoin-dev@lists.linuxfoundation.org >>>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >>>> >>>> >>> --001a113eb9c8f0d199051cbd76c3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Surely you have some sort of empirical measurement demonst= rating the validity of that statement? That is to say you've establishe= d some technical criteria by which to determine how much centralization pre= ssure is too much, and shown that Pieter's proposal undercuts expected = progress in that area?

On Fri, Aug 7, 2015 at 12:07 PM, Ryan Butler <rryanan= izer@gmail.com> wrote:

Clarification...

These are not mutually exclusive.=C2=A0 We can design an inc= rease to blocksize that increases available space on chain AND follow techn= ological evolution.=C2=A0 Peter's latest proposal is way too conservati= ve on that front.

And given Peter's assertion that demand is infinite ther= e will still be a an ocean of off chain transactions for the likes of block= stream to address.

On Aug 7, 2015 1:57 PM, "Ryan Butler" = <rryananizer@= gmail.com> wrote:

Who said anything about scaling bitcoin to visa levels = now?=C2=A0 We're talking about an increase now that scales into the fut= ure at a rate that is consistent with technological progress.

Peter himself said "So, I think the block size should f= ollow technological evolution...".

The blocksize increase proposals have been modeled around th= is very thing.=C2=A0 It's reasonable to increase the blocksize to a poi= nt that a reasonable person, with reasonable equipment and internet access = can run a node or even a miner with acceptable orphan rates.=C2=A0 Most min= ers are spv mining anyways.=C2=A0 The 8 or even 20 MB limits are within tho= se parameters.

These are not mutually exclusive.=C2=A0 We can design an inc= rease to blocksize that addresses both demand exceeding the available space= AND follow technological evolution.=C2=A0 Peter's latest proposal is w= ay too conservative on that front.

On Aug 7, 2015 1:25 PM, "Mark Friedenbach&q= uot; <mark@fri= edenbach.org> wrote:
Please don't put words into Pie= ter's mouth. I guarantee you everyone working on Bitcoin in their heart= of hearts would prefer everyone in the world being able to use the Bitcoin= ledger for whatever purpose, if there were no cost.

But like = any real world engineering issue, this is a matter of tradeoffs. At the ext= reme it is simply impossible to scale Bitcoin to the terrabyte sized blocks= that would be necessary to service the entire world's financial transa= ctions. Not without sacrificing entirely the protection of policy neutralit= y achieved through decentralization. And as that is Bitcoin's only adva= ntage over traditional consensus systems, you would have to wonder what the= point of such an endeavor would be.

So *somewhere* you have t= o draw the line, and transactions below that level are simply pushed into h= igher level or off-chain protocols.

The issue, as Pieter and J= orge have been pointing out, is that technical discussion over where that l= ine should be has been missing from this debate.

On Fri, Aug 7, 2015 at 10:47 AM, R= yan Butler via bitcoin-dev <bitcoin-dev@lists.linuxfou= ndation.org> wrote:

Interesting position there Peter...you fear more people actually u= sing bitcoin.=C2=A0 The less on chain transactions the lower the velocity a= nd the lower the value of the network.=C2=A0 I would be careful what you as= k for because you end up having nothing left to even root the security of t= hese off chain transactions with and then neither will exist.

Nobody ever said you wouldn't run out of capacity at any= size.=C2=A0 It's quite the fallacy to draw the conclusion from that st= atement that block size should remain far below a capacity it can easily ma= intain which would bring more users/velocity/value to the system.=C2=A0 The= outcomes of both of those scenarios are asymmetric.=C2=A0 A higher block s= ize can support more users and volume.

Raising the blocksize isn't out of fear.=C2=A0 It's = the realization that we are at a point where we can raise it and support mo= re users and transactions while keeping the downsides to a minimum (central= ization etc).

On Aug 7, 2015 11:28 AM, "Pieter = Wuille via bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org&= gt; wrote:
On Fri, Aug 7, 2015 at 5:55 PM, Gavin Andrese= n <gavinandresen@gmail.com> wrote:
On= Fri, Aug 7, 2015 at 11:16 AM, Pieter Wuille <pieter.wuille@gmail.c= om> wrote:
I guess my ques= tion (and perhaps that's what Jorge is after): do you feel that blocks = should be increased in response to (or for fear of) such a scenario.
=

I think there are= multiple reasons to raise the maximum block size, and yes, fear of Bad Thi= ngs Happening as we run up against the 1MB limit is one of the reasons.

I take the opinion of smart engineers who actually do= resource planning and have seen what happens when networks run out of capa= city very seriously.

This is a fundamental disagreement then. I believe that the demand is inf= inite if you don't set a fee minimum (and I don't think we should),= and it just takes time for the market to find a way to fill whatever is av= ailable - the rest goes into off-chain systems anyway. You will run out of = capacity at any size, and acting out of fear of that reality does not impro= ve the system. Whatever size blocks are actually produced, I believe the re= sult will either be something people consider too small to be competitive (= "you mean Bitcoin can only do 24 transactions per second?" sounds= almost the same as "you mean Bitcoin can only do 3 transactions per s= econd?"), or something that is very centralized in practice, and likel= y both.


And if so, if that is a reason for increase now, = won't it be a reason for an increase later as well? It is my impression= that your answer is yes, that this is why you want to increase the block s= ize quickly and significantly, but correct me if I'm wrong.
<= /div>

Sure, it might be = a reason for an increase later. Here's my message to in-the-future Bitc= oin engineers: =C2=A0you should consider raising the maximum block size if = needed and you think the benefits of doing so (like increased adoption or l= ower transaction fees or increased reliability) outweigh the costs (like hi= gher operating costs for full-nodes or the disruption caused by ANY consens= us rule change).

In general that sounds reasonable, but it's a dangerou= s precedent to make technical decisions based on a fear of change of econom= ics...

--
Pieter

<= /div>

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev


_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev



--001a113eb9c8f0d199051cbd76c3--